Tualatin Together
tualatintogether.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
Tualatin Together’s website earns an Experience Score of 31/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, Tualatin Together scored 20 — slow. Your main content takes around 36 seconds to appear on a mid-range phone, and the page is heavy (13.3 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, Tualatin Together ranks #1593 of 1617 in Human Services and #1205 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
- WordPress
- Page title
- Detected
- Meta description
- Not detected
- Canonical URL
- 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
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.