Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
js.stripe.com/clover/stripe.js?ver=clover	120.0 s	225.3 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js?ver=6.8.5	604800.0 s	123.3 KiB
e.infogram.com/js/dist/embed-loader-min.js	86400.0 s	4.6 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:69.215 source:map[column:1818 line:0 type:source-location url:https://www.amnesty.org/en/wp-content/themes/humanity-theme/assets/scripts/bundle.js?ver=3.0.3 urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
THE STATE OF THE WORLD’S HUMAN RIGHTS Amnesty International’s Annual Report 20… `body.home > div.wp-site-blocks > section.wp-block-amnesty-core-hero`	www.amnesty.org/en/wp-content/uploads/2026/04/315356-homepage-1468x621.jpg	443.4 KiB	295.0 KiB
NEWS Haiti: New massacre highlights widespread failure to protect the populatio… `section#section-d14eb42a > div#d14eb42a > div.grid > article.grid-item`	/en/wp-content/uploads/2026/04/GettyImages-2188504445-sca...	221.6 KiB	179.9 KiB
NEWS Lebanon: Civil complaint in France a rare opportunity to hold Israel to ac… `section#section-d14eb42a > div#d14eb42a > div.grid > article.grid-item`	/en/wp-content/uploads/2026/04/4bc5f0ca-7743-44e4-9085-fb...	219.4 KiB	177.8 KiB
div.grid > article.grid-item > figure > img.petition-itemImage `div.grid > article.grid-item > figure > img.petition-itemImage`	/en/wp-content/uploads/2026/04/EU-ASSOCIATION-WEB-BANNER-...	191.1 KiB	167.6 KiB
How Vanautu’s proposed UN climate change resolution may shift climate accountab… `section#section-d14eb42a > div#d14eb42a > div.grid > article.grid-item`	www.amnesty.org/en/wp-content/uploads/2026/04/GettyImages-2187346948-640x400.jpg	190.8 KiB	149.2 KiB
NEWS Israel/OPT: States must ensure safe passage for Global Sumud Flotilla as a… `section#section-d14eb42a > div#d14eb42a > div.grid > article.grid-item`	/en/wp-content/uploads/2026/04/GettyImages-2269270742-1-1...	181.7 KiB	141.1 KiB
div.grid > article.grid-item > figure > img.petition-itemImage `div.grid > article.grid-item > figure > img.petition-itemImage`	/en/wp-content/uploads/2026/03/Ekpar_football_upscaled_ba...	137.4 KiB	114.0 KiB
NEWS Russia: Imprisoned young anti-war activists must be immediately and uncond… `section#section-d14eb42a > div#d14eb42a > div.grid > article.grid-item`	/en/wp-content/uploads/2026/04/78d08a2a-e2e8-4c75-00bc-08...	128.3 KiB	86.6 KiB
div.grid > article.grid-item > figure > img.petition-itemImage `div.grid > article.grid-item > figure > img.petition-itemImage`	www.amnesty.org/en/wp-content/uploads/2024/03/292922_display-640x400.jpg	53.2 KiB	29.8 KiB
div.grid > article.grid-item > figure > img.petition-itemImage `div.grid > article.grid-item > figure > img.petition-itemImage`	www.amnesty.org/en/wp-content/uploads/2024/11/303705-640x400.jpg	47.5 KiB	24.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-SECTION

nodeLabel: THE STATE OF THE WORLD’S HUMAN RIGHTS Amnesty International’s Annual Report 20…

path: 1,HTML,1,BODY,5,DIV,0,SECTION

selector: body.home > div.wp-site-blocks > section.wp-block-amnesty-core-hero

snippet: <section class="wp-block-amnesty-core-hero aimc-ignore is-aligned-left has-dark-background" style="background-image: url("https://www.amnesty.org/en/wp-content/uploads/2026/0…");">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.googletagmanager.com/gtm.js?id=GTM-MH9W89&ver=1.0.0	155.0 KiB	2.4 s
/en/wp-content/plugins/humanity-content-security-policy/a...	10.1 KiB	152 ms
www.amnesty.org/en/wp-includes/js/dist/hooks.min.js?ver=4d63a3d491d11ffd8ac6	3.3 KiB
/en/wp-content/plugins/block-tabbed-content-1.0.0-rc.6/di...	2.3 KiB
/en/wp-content/plugins/wp-plugin-theme-companion/assets/s...	2.1 KiB
/en/wp-content/themes/humanity-theme/assets/scripts/infog...	1.8 KiB
/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/...	4.0 KiB	152 ms
/en/wp-content/plugins/amnesty-sharepoint-runner/assets/f...	1.8 KiB
/en/wp-content/themes/humanity-theme/assets/styles/bundle...	33.2 KiB	457 ms
/en/wp-content/plugins/wp-plugin-theme-companion/assets/s...	2.7 KiB
www.amnesty.org/en/wp-includes/blocks/social-links/style.min.css?ver=6.8.5	3.2 KiB
/en/wp-content/plugins/block-tabbed-content-1.0.0-rc.6/di...	2.0 KiB
/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/...	1.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s

URL	Time Spent
amnesty.org/	801 ms
amnesty.org/	781 ms
www.amnesty.org/	150 ms
www.amnesty.org/en/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 28.1 KiB

URL	Transfer Size	Est Savings
/en/wp-content/themes/humanity-theme/assets/styles/bundle...	31.5 KiB	28.1 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.1 s 419.5 KiB

URL	Transfer Size	Est Savings
js.stripe.com/clover/stripe.js?ver=clover	224.8 KiB	163.6 KiB
www.googletagmanager.com/gtag/js?id=AW-812734679&cx=c&gtm=4e64h1	136.6 KiB	83.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-MH9W89&ver=1.0.0	154.6 KiB	80.0 KiB
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js?ver=6.8.5	122.9 KiB	57.4 KiB
cdn-eu.pagesense.io/js/amnestyinternational/a9ce5c8e3e61437682525db5403e1431.js	71.8 KiB	35.4 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js?ver=6.8.5	434 ms	351 ms	59 ms
Unattributable	387 ms	7.7 ms	0.0 ms
/en/wp-content/themes/humanity-theme/assets/scripts/bundl...	333 ms	44 ms	6.4 ms
js.stripe.com/clover/stripe.js?ver=clover	328 ms	185 ms	142 ms
www.amnesty.org/en/	324 ms	33 ms	6.6 ms
www.googletagmanager.com/gtm.js?id=GTM-MH9W89&ver=1.0.0	238 ms	189 ms	43 ms
cdn-eu.pagesense.io/js/amnestyinternational/a9ce5c8e3e61437682525db5403e1431.js	196 ms	168 ms	26 ms
www.googletagmanager.com/gtag/js?id=AW-812734679&cx=c&gtm=4e64h1	118 ms	82 ms	35 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.1 s
Other	514 ms
Style & Layout	421 ms
Script Parsing & Compilation	333 ms
Parse HTML & CSS	70 ms
Rendering	35 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.amnesty.org/en/wp-content/uploads/2026/04/315356-homepage-1468x621.jpg	445.1 KiB
js.stripe.com/clover/stripe.js?ver=clover	225.3 KiB
/en/wp-content/uploads/2026/04/GettyImages-2188504445-sca...	223.3 KiB
/en/wp-content/uploads/2026/04/4bc5f0ca-7743-44e4-9085-fb...	221.1 KiB
/en/wp-content/uploads/2026/04/EU-ASSOCIATION-WEB-BANNER-...	192.8 KiB
www.amnesty.org/en/wp-content/uploads/2026/04/GettyImages-2187346948-640x400.jpg	192.5 KiB
/en/wp-content/uploads/2026/04/GettyImages-2269270742-1-1...	183.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-MH9W89&ver=1.0.0	155.0 KiB
/en/wp-content/uploads/2026/03/Ekpar_football_upscaled_ba...	139.1 KiB
www.googletagmanager.com/gtag/js?id=AW-812734679&cx=c&gtm=4e64h1	136.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 9 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 100 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-column > div.wp-block-group > figure.aimc-ignore > a `div.wp-block-column > div.wp-block-group > figure.aimc-ignore > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEWS `article.grid-item > div.grid-content > span.grid-itemMeta > a`
NEWS `article.grid-item > div.grid-content > span.grid-itemMeta > a`
NEWS `article.grid-item > div.grid-content > span.grid-itemMeta > a`
NEWS `article.grid-item > div.grid-content > span.grid-itemMeta > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
cdn-eu.pagesense.io/js/amnestyinternational/a9ce5c8e3e61437682525db5403e1431.js line 4, col 107519	Connecting to 'https://pagesense-hb-collect.zoho.eu/psimg.gif?raw=%7B%22vrd%22%3A%5B%7B%22a%22%3A%22amnestyinternational%22%2C%22p%22%3A%22a9ce5c8e3e61437682525db5403e1431%22%2C%22n%22%3Atrue%7D%5D%2C%22urd%22%3A%7B%22f%22%3A%221776800874811zabu0.40483100114300186%22%2C%22d%22%3A%221776800874872zabv0.15244464296379878%22%7D%7D&type=24&domainname=amnestyinternational&uuid=1776800874811zabu0.40483100114300186' violates the following Content Security Policy directive: "connect-src 'self' https://apikeys.civiccomputing.com https://clapi.civiccomputing.com https://www.google.com https://my2.siteimprove.com https://googleads.g.doubleclick.net https://id.siteimprove.com https://www.google-analytics.com https://region1.google-analytics.com https://stats.g.doubleclick.net https://.hotjar.com https://.hotjar.io wss://*.hotjar.com https://contentassistant.eu.siteimprove.com https://public.flourish.studio https://oneamnesty.sharepoint.com/ https://pagesense-collect.zoho.eu https://www.recaptcha.net https://action.amnestyhk.org https://amnestyhk.org". The action has been blocked.
/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/...	`Failed to load resource: the server responded with a status of 404 ()`
/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/...	`Failed to load resource: the server responded with a status of 404 ()`
www.amnesty.org/en/ line 712, col 0	`Manifest fetch from https://www.amnesty.org/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/favicons/manifest.json failed, code 404`
www.amnesty.org/en/	`Manifest fetch from https://www.amnesty.org/en/wp-content/plugins/wp-plugin-amnesty-branding/assets/favicons/manifest.json failed, code 404`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/en/latest/news/2026/04/amnesty-international-calls-state...	READ MORE

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`