NSINonprofit Speed Index

← All rankings

Jericho Road

Oregon · Human Services

jerichoroad.yolasite.com ↗
Experience Score
65 out of 100
Grade C

A few accessibility issues are keeping it out of the top band.

What sets the score

Speed 70% of score
68
Accessibility 30% of score
58

Also measured · not scored

85 Desktop
74 Best Practices
75 SEO

What this means

Jericho Road’s website earns an Experience Score of 65/100 (C) — the “needs improvement” range. Visitors on phones are likely waiting longer than they should, or hitting small accessibility snags, either of which can quietly cost you donations and sign-ups. The good news: scores here usually trace back to a handful of fixable issues.

Speed

On speed, Jericho Road scored 68. The biggest factor is how long your main content takes to appear — about 8 seconds on a mid-range phone. That usually comes from large, uncompressed images and a heavy page (1.1 MB). Compressing images and turning on caching are the common quick wins — good items to hand your web team or host.

Accessibility

Accessibility scored 58 (automated). Common issues in this range are low color contrast, missing image descriptions (alt text), and form fields without labels — all straightforward for a developer to fix, and important for visitors who use a screen reader or keyboard navigation.

How you compare

Among peers, Jericho Road ranks #700 of 1619 in Human Services and #560 of 1221 in Oregon. Explore the full rankings to see how you stack up against the top nonprofits in your field.

Technical details

Core Web Vitals

From the latest mobile scan — useful for your web team.

7.7 s Largest Contentful Paint
0.008 Cumulative Layout Shift
9 ms Total Blocking Time
3.2 s First Contentful Paint
3.9 s Speed Index
1.1 MB Page weight

What to do next

Three things that move the needle most: (1) compress and resize your images, (2) ask your host or developer about caching and lazy-loading, (3) fix the accessibility items above. Then re-test free at pagespeed.web.dev and watch the score climb.

Copy this text to send to your team or developer

See something wrong? Suggest a correction