Oregon Law Foundation
oregonlawfoundation.org ↗Loads fast on phones and clears our automated accessibility checks.
What sets the score
Also measured · not scored
What this means
Oregon Law Foundation’s website earns an Experience Score of 92/100 (A) — the top band. It loads quickly on phones and clears our automated accessibility bar, so most visitors get a fast, usable experience. Re-test after any major site change to make sure you stay here.
Speed
On speed, Oregon Law Foundation scored 89. The biggest factor is how long your main content takes to appear — about 3 seconds on a mid-range phone. That usually comes from large, uncompressed images and a heavy page (490 KB). Compressing images and turning on caching are the common quick wins — good items to hand your web team or host.
Accessibility
Accessibility scored 100 (automated) — strong. Automated tools only catch part of the picture, so a quick manual check (keyboard navigation, image descriptions, color contrast) is still worthwhile, but you’re in good shape.
How you compare
Among peers, Oregon Law Foundation ranks #7 of 607 in Public & Societal Benefit and #14 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.
Site setup
Not part of the score. Read from the homepage HTML on October 15, 2026 — tags added by JavaScript may not be seen.
- Platform
- WordPress
- Page title
- Detected
- Meta description
- Detected
- Canonical URL
- Detected
- Social sharing preview
- Detected
- Mobile viewport
- Detected
- Page language
- Detected
- Structured data (schema)
- WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization
- llms.txt
- Detected
- robots.txt
- Detected
- XML sitemap
- Detected
- Favicon
- Detected
- HTTPS
- Detected
What to do next
To stay in the top band: keep new images compressed and sized for the web, avoid piling on third-party scripts, and re-test at pagespeed.web.dev after big changes.