Seeds for the Sol
seedsforthesol.org ↗Slow to load on phones — many visitors leave before the page is usable.
What sets the score
Also measured · not scored
What this means
Seeds for the Sol’s website earns an Experience Score of 43/100 (D) — the lowest band. On a typical phone the site is slow to load and/or hard to use for people relying on assistive technology, and many visitors won’t wait. This is very fixable, and even small improvements will move the score noticeably.
Speed
On speed, Seeds for the Sol scored 32 — slow. Your main content takes around 13 seconds to appear on a mid-range phone, and the page is heavy (7 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 86 (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, Seeds for the Sol ranks #773 of 855 in Environment & Animals and #1141 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 19, 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)
- WebSite, SearchAction, EntryPoint, WebPage, BreadcrumbList, ListItem, ReadAction, Organization, ImageObject
- llms.txt
- Not detected
- robots.txt
- Detected
- XML sitemap
- Detected
- Favicon
- Not detected
- HTTPS
- Detected
What to do next
Start here: (1) compress and resize images and remove unused scripts, (2) enable caching and consider a CDN, (3) address the accessibility barriers above with your developer. Even one or two of these will lift your score — re-test anytime at pagespeed.web.dev.