Website review, no card needed
afphq.org website review
Visit site (opens in a new tab)Reviewed 6 November 202627 issues · 79 checks
This review found 27 issues worth fixing on afphq.org, 9 of them high impact, across 79 checks. The most urgent: page weight: 6.1 MB in 157 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 4.8 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 265 ms |
| May 23, 2026 | 283 ms |
| May 30, 2026 | 294 ms |
| Jun 6, 2026 | 302 ms |
| Jun 13, 2026 | 309 ms |
| Jun 20, 2026 | 314 ms |
| Jun 27, 2026 | 313 ms |
| Jul 4, 2026 | 312 ms |
| Jul 11, 2026 | 311 ms |
| Jul 18, 2026 | 310 ms |
| Jul 25, 2026 | 310 ms |
| Aug 1, 2026 | 296 ms |
| Aug 8, 2026 | 259 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 206 ms |
| Sep 19, 2026 | 218 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 227 ms |
| Oct 10, 2026 | 231 ms |
| Oct 17, 2026 | 232 ms |
| Oct 24, 2026 | 236 ms |
| Oct 31, 2026 | 230 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.7 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, VWO and Facebook and others), adding 1.4 MB and 2.3 s of main-thread time.
Reduce unused JavaScript
360 ms · 658 KiBAbout 658 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 360 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 881 ms
881 msGoogle Tag Manager costs a phone 881 ms of main-thread work and 678 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.
Improve image delivery
919 KiB6 images could be 919 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
900 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
VWO adds 702 ms
702 msVWO costs a phone 702 ms of main-thread work and 219 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.
Reduce unused CSS
300 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
295 KiB18 files are served with short cache lifetimes, so returning visitors download them again (295 KiB).
Facebook adds 266 ms
266 msFacebook costs a phone 266 ms of main-thread work and 229 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 249 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
20 KiB20 KiB JavaScript is shipped twice across bundles.
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
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 887 ms
887 msScripts block taps and scrolling for 887 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Americans for Prosperity believes freedom and opportunity a…”. Most of its time is element render delay (2.4 s).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 170 ms
170 msReal visitors wait 170 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 597 ms
597 msReal visitors wait 597 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 265 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.3 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 157 requests
6.1 MBYour homepage downloads 6.1 MB in 157 requests on a phone: media 2.6 MB (1), scripts 1.7 MB (63) and images 1.2 MB (28). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (273 KiB) are 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.
2 images below the first screen load straight away
2 images further down the page (273 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 206.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
35 internal links, 13 external
The homepage links to 35 pages on afphq.org and 13 external pages.
8 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “We recruit and unite concerned citizens in 35 states to advance policies that will help people improve their lives.”.
One H1 headline
Your main headline reads: “Reignite the American Dream”.
Title: 31 characters
Your title is a healthy 31 characters: “Home - Americans for Prosperity”.
Canonical URL set
The canonical URL is https://americansforprosperity.org/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://americansforprosperity.org/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (579 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://americansforprosperity.org/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://americansforprosperity.org/stories and https://americansforprosperity.org/newsroom/intelligence-report have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://americansforprosperity.org/national-scorecard and https://americansforprosperity.org/government-affairs have 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 28 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
10 of 11 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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.
About 502 words of copy
The homepage carries about 502 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”, “Subscribe” and “Sign Up”.
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
33 other companies contacted
Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 afphq.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
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 134 open roles
- Teams
- Part Time or Full Time Internship (33), Part Time Internship (20), State Operations & States (16), Full Time Internship (13)
- Job board
- lever
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on afphq.org, including 17 speed issues, 1 SEO issue and 3 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.