Website review, no card needed
alternet.org website review
Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 93 checks
This review found 42 issues worth fixing on alternet.org, 17 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 95 ms |
| May 9, 2026 | 95 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 100 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 99 ms |
| Aug 1, 2026 | 99 ms |
| Aug 8, 2026 | 102 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 133 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Reduce unused JavaScript
1.2 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 74). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 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 (Ad Lightning, Cloudflare CDN and cloudfront.net and others), adding 2.2 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
300 ms · 792 KiB74 files are served with short cache lifetimes, so returning visitors download them again (792 KiB).
Ad Lightning adds 292 ms
292 msAd Lightning costs a phone 292 ms of main-thread work and 209 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.
Cloudflare CDN adds 256 ms
256 msCloudflare CDN costs a phone 256 ms of main-thread work and 298 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 264 ms. During a long task the page ignores taps.
piano adds 212 ms
212 mspiano costs a phone 212 ms of main-thread work and 402 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.
Taboola adds 162 ms
162 msTaboola costs a phone 162 ms of main-thread work and 399 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.
Google Tag Manager adds 166 ms
166 msGoogle Tag Manager costs a phone 166 ms of main-thread work and 308 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.
1,526 HTML elements
The page has 1,526 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Reduce unused CSS
31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
25 KiB1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 74 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 37.4 s
37.4 sThe page becomes fully interactive after 37.4 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Psychologist sees 'dementia' signs in 3 'peculiar' Trump en…”.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 795 ms
795 msScripts block taps and scrolling for 795 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 95 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 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.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 281 ms
281 msReal visitors wait 281 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 450 requests
4.3 MBYour homepage downloads 4.3 MB in 450 requests on a phone: scripts 3.5 MB (131), fonts 258 KiB (11) and other files 188 KiB (194). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (107 elements)
All page content should be contained by landmarks: 107 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
37 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: 37 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (12 characters)
Your title is only 12 characters: “Alternet.org”. Between 30 and 65 characters leaves room to say what you do and for whom.
251 internal links, 9 external
The homepage links to 251 pages on alternet.org and 9 external pages.
7 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Breaking news, political news, and investigative news reporting from AlterNet's team of journalists and prize-winning i…”.
One H1 headline
Your main headline reads: “Breaking news, political news, and investigative news reporting from AlterNet's team of journalists and prize-winning i…”.
Canonical URL set
The canonical URL is https://www.alternet.org/.
Structured data in place
Structured data found: Organization 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://www.alternet.org/sitemap.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
There is no https://www.alternet.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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
2 checks passed
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 (807 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.alternet.org/msn, https://www.alternet.org/commentary, https://www.alternet.org/Frontpage-feature, https://www.alternet.org/Frontpage-videos, https://www.alternet.org/Frontpage-news-and-politics and https://www.alternet.org/culture and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.alternet.org/the-right-wing, whose canonical is https://www.alternet.org/2020/12/the-right-wing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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 broken images
2 images failed to load on a phone, for example https://d2s3kjdp77ms5k.cloudfront.net/pixel.gif?timestamp=1792664621599&site_uuid=b8abd5c0-0a5e-47e8-8139-f65d9e385221&hostname=alternet.org&ad_unit=alternet.org_Mobile_300x250_1&impression_type=il&de.
36 third-party cookies
36 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.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'onclick')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
31 of 35 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 612 words of copy
The homepage carries about 612 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager 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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
84 other companies contacted
Loading the homepage contacts 84 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 alternet.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on alternet.org, including 19 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.