Website review, no card needed
amnesty.it website review
Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 83 checks
This review found 42 issues worth fixing on amnesty.it, 14 of them high impact, across 83 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.8 s |
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 173 ms |
| May 9, 2026 | 173 ms |
| May 16, 2026 | 176 ms |
| May 23, 2026 | 193 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 205 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 213 ms |
| Aug 8, 2026 | 201 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 201 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 184 ms |
| Oct 10, 2026 | 173 ms |
| Oct 17, 2026 | 171 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
Speed
Reduce unused JavaScript
3.4 s · 639 KiBAbout 639 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 1.6 MB34 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
1.6 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
550 ms · 1,018 KiB19 images could be 1,018 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 32). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Maps and others), adding 2.6 MB and 554 ms of main-thread time.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Google Tag Manager adds 447 ms
447 msGoogle Tag Manager costs a phone 447 ms of main-thread work and 822 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.
2,823 HTML elements
The page has 2,823 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 1.4 MB 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.
Minify CSS
80 ms · 6 KiB6 KiB could be saved by minifying CSS.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AL VIA LA MARATONA PER I DIRITTI FIRMA I 5 APPELLI”.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.186
0.186The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 173 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 169 ms
169 msReal visitors wait 169 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 108 ms
108 msScripts block the page for only 108 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.8 MB in 102 requests
3.8 MBYour homepage downloads 3.8 MB in 102 requests on a phone: images 1.8 MB (39), scripts 1.4 MB (26) and fonts 419 KiB (8). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (998 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.
7 images below the first screen load straight away
7 images further down the page (817 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 129.0 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
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (6 elements)
Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Amnesty International Italia”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 H1 headlines
There are 3 <h1> headlines (“Al via la maratona per i diritti”, “Io mi attivo!” and “Crimini contro l'umanità in Iran”). One clear main headline is easier for people and search engines.
102 internal links, 35 external
The homepage links to 102 pages on amnesty.it and 35 external pages.
6 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “La sezione italiana di Amnesty International lotta contro le ingiustizie e in difesa dei diritti umani nel mondo.”.
Canonical URL set
The canonical URL is https://www.amnesty.it/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.amnesty.it/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://www.amnesty.it/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 (984 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.amnesty.it/rapporti-annuali/rapporto-2026 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.amnesty.it/area-stampa, https://www.amnesty.it/chi-siamo/bilancio-esercizio, https://www.amnesty.it/chi-siamo/rendicontazione-5x1000 and https://www.amnesty.it/chi-siamo/contributi-parte-della-pubblica-amministrazione have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.amnesty.it/notizie/tutte-le-notizie 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 73 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
3 JavaScript errors while loading
3 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
26 of 31 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 971 words of copy
The homepage carries about 971 words of visible text.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 amnesty.it, 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
Company
- Employees
- 79
- Founded
- 1975
- Headquarters
- Rome
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on amnesty.it, including 22 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.