Website review, no card needed
codeforamerica.org website review
Visit site (opens in a new tab)Reviewed 26 October 202635 issues · 80 checks
This review found 35 issues worth fixing on codeforamerica.org, 7 of them high impact, across 80 checks. The most urgent: mobile performance score: 48. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Code for America
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 95 ms |
| May 16, 2026 | 99 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 107 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 108 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and fundraiseup.com and others), adding 1.9 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
857 KiBAbout 857 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
850 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Google Tag Manager adds 721 ms
721 msGoogle Tag Manager costs a phone 721 ms of main-thread work and 971 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
417 KiB17 files are served with short cache lifetimes, so returning visitors download them again (417 KiB).
Improve image delivery
337 KiB3 images could be 337 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Vimeo adds 34 ms
34 msVimeo costs a phone 34 ms of main-thread work and 516 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 220 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 25.9 s
25.9 sThe page becomes fully interactive after 25.9 s. Good is under 3.8 s.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re helping states navigate the new rules in Medicaid wor…”.
Total Blocking Time: 627 ms
627 msScripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 937 ms
937 msReal visitors wait 937 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.161
0.161The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.6 MB in 92 requests
3.6 MBYour homepage downloads 3.6 MB in 92 requests on a phone: scripts 2.1 MB (38), fonts 944 KiB (3) and images 510 KiB (17). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (347 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “Code for America”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
63 internal links, 12 external
The homepage links to 63 pages on codeforamerica.org and 12 external pages.
5 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “Government can and should work well for everyone. We’re people-centered problem solvers showing that it’s possible.”.
Canonical URL set
The canonical URL is https://codeforamerica.org/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://codeforamerica.org/sitemap_index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://codeforamerica.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (276 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a meta description
https://codeforamerica.org/news/code-for-america-named-google-impact-challenge-recipient, https://codeforamerica.org/news/anthropic-partnership, https://codeforamerica.org/partner-with-us, https://codeforamerica.org/donate, https://codeforamerica.org/programs and https://codeforamerica.org/success-stories and 8 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://codeforamerica.org/podcast has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 247 words
The homepage has only about 247 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “sign up for our newsletter”, “Learn more about us” and “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at codeforamerica.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- React
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 8 open roles
- Teams
- Product Engineering (2), Data Science (1), Programs (1), Solutions Engineering (1)
- Job board
- greenhouse
- Careers page
- codeforamerica.org/jobs (opens in a new tab)
Company
- Founded
- 2009
- Headquarters
- San Francisco
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on codeforamerica.org, including 18 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.