The Willow Conservancy
willowconservancy.com ↗Middling phone speed is holding the score back — the quickest win.
What sets the score
Also measured · not scored
What this means
The Willow Conservancy’s website earns an Experience Score of 66/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, The Willow Conservancy scored 59. The biggest factor is how long your main content takes to appear — about 14 seconds on a mid-range phone. That usually comes from large, uncompressed images and a heavy page (3.9 MB). Compressing images and turning on caching are the common quick wins — good items to hand your web team or host.
Accessibility
Accessibility scored 87 (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, The Willow Conservancy ranks #311 of 855 in Environment & Animals and #565 of 1222 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
- Wix
- Page title
- Detected
- Meta description
- Not detected
- Canonical URL
- Detected
- Social sharing preview
- Detected
- Mobile viewport
- Detected
- Page language
- Detected
- Structured data (schema)
- WebSite
- llms.txt
- Detected
- robots.txt
- Detected
- XML sitemap
- Detected
- Favicon
- Detected
- HTTPS
- Detected
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.