TransPonder
transponder.community ↗Middling phone speed is holding the score back — the quickest win.
What sets the score
Also measured · not scored
What this means
TransPonder’s website earns an Experience Score of 57/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, TransPonder scored 46 — slow. Your main content takes around 18 seconds to appear on a mid-range phone, and the page is heavy (3.8 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 93 (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, TransPonder ranks #588 of 795 in Other / Unclassified and #889 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
- 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, SearchAction, EntryPoint, Restaurant, PostalAddress, GeoCoordinates
- 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.