Website review, no card needed

amnesty.org logo

amnesty.org website review

Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 77 checks

This review found 32 issues worth fixing on amnesty.org, 13 of them high impact, across 77 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.1 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
176 ms142 msMay 2Oct 17171 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026152 ms
May 16, 2026149 ms
May 23, 2026150 ms
May 30, 2026149 ms
Jun 6, 2026146 ms
Jun 13, 2026147 ms
Jun 20, 2026149 ms
Jun 27, 2026149 ms
Jul 4, 2026155 ms
Jul 11, 2026158 ms
Jul 18, 2026155 ms
Jul 25, 2026155 ms
Aug 1, 2026153 ms
Aug 8, 2026149 ms
Aug 15, 2026148 ms
Aug 22, 2026147 ms
Aug 29, 2026147 ms
Sep 5, 2026148 ms
Sep 12, 2026153 ms
Sep 19, 2026159 ms
Sep 26, 2026164 ms
Oct 3, 2026170 ms
Oct 10, 2026172 ms
Oct 17, 2026171 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

Full-page screenshot of amnesty.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amnesty.org at 0.4 s0.4 s
  2. amnesty.org at 0.8 s0.8 s
  3. amnesty.org at 1.1 s1.1 s
  4. amnesty.org at 1.5 s1.5 s
  5. amnesty.org at 1.9 s1.9 s
  6. amnesty.org at 2.3 s2.3 s
  7. amnesty.org at 2.6 s2.6 s
  8. amnesty.org at 3.0 s3.0 s

Speed

7 to fix49
  • Improve image delivery

    1.6 s · 1.3 MB

    12 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 450 KiB

    About 450 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.5 s · 278 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (278 KiB).

  • Render-blocking requests

    1.7 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Stripe, Google Tag Manager and PageSense and others), adding 793 KiB and 723 ms of main-thread time.

  • Google Tag Manager adds 219 ms

    219 ms

    Google Tag Manager costs a phone 219 ms of main-thread work and 312 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

    150 ms · 28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    38 KiB

    Polyfills for old browsers add 38 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 636 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “KENYAN AUTHORITIES ESCALATING AUTHORITARIAN TACTICS IN PROT…”.

  • Time to Interactive: 15.5 s

    15.5 s

    The page becomes fully interactive after 15.5 s. Good is under 3.8 s.

  • First Contentful Paint: 4.3 s

    4.3 s

    The first text or image appears after 4.3 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.3 s

    6.3 s

    Visually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.

  • Real-user CLS: 0.14

    0.14

    For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 477 ms

    477 ms

    Scripts block taps and scrolling for 477 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 148 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 156 ms

    156 ms

    Real visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 744 ms

    744 ms

    Real visitors wait 744 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 53 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 53 requests on a phone: images 2.0 MB (18), scripts 873 KiB (19) and fonts 53 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (184 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.

  • 3 images below the first screen load straight away

    3 images further down the page (206 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.84 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.2 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

3 to fixGoogle 9397
  • 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.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 9 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9287
  • Title is short (21 characters)

    Your title is only 21 characters: “Amnesty International”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://www.amnesty.org/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 90 internal links, 9 external

    The homepage links to 90 pages on amnesty.org and 9 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “We are a global movement of more than 10 million people in over 150 countries who campaign campaign for a world where h…”.

  • One H1 headline

    Your main headline reads: “Kenyan authorities escalating authoritarian tactics in protest crackdown”.

  • Canonical URL set

    The canonical URL is https://www.amnesty.org/en/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your 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.amnesty.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
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (419 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.amnesty.org/en/latest/news is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.amnesty.org/fr, https://www.amnesty.org/ar, https://www.amnesty.org/en/about-us, https://www.amnesty.org/en/careers, https://www.amnesty.org/en/countries and https://www.amnesty.org/en/get-involved/take-action and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.amnesty.org/en/latest has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.amnesty.org/ar, https://www.amnesty.org/zh-hans, https://www.amnesty.org/zh-hant and https://www.amnesty.org/ru have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

4 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.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 5 small tap targets

    5 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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.

  • About 390 words of copy

    The homepage carries about 390 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Join”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 amnesty.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
Analytics
Google Tag Manager

Company

Founded
1961
Headquarters
London

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on amnesty.org, including 15 speed issues, 3 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25