Belwin Conservancy
belwin.org ↗Middling phone speed is holding the score back — the quickest win.
What sets the score
Also measured · not scored
What this means
Belwin Conservancy’s website earns an Experience Score of 56/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, Belwin Conservancy scored 46 — slow. Your main content takes around 7 seconds to appear on a mid-range phone, and the page is heavy (4.2 MB). Oversized images, too many scripts, and no caching are the usual culprits. A developer can typically cut this dramatically by optimizing images and enabling caching and a CDN.
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, Belwin Conservancy ranks #585 of 855 in Environment & Animals and #907 of 1286 in Minnesota. 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
- Not detected
- Canonical URL
- Not detected
- Social sharing preview
- Not detected
- Mobile viewport
- Detected
- Page language
- Detected
- Structured data (schema)
- Not detected
- llms.txt
- Not 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.