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
/uc.js?cbid=e7376c96-0a25-4b97-b830-39e089879445&implemen...	213.0 s	35.7 KiB
www.transparency.org/fonts/open-sans-v34-latin-regular.woff2	0.0 ms	16.5 KiB
www.transparency.org/fonts/open-sans-v34-latin-700.woff2	0.0 ms	16.1 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.transparency.org/assets/dist/assets/index-D5GkNzM3.js	0.0 ms	14.4 KiB
www.transparency.org/fonts/oswald-v53-latin-500.woff2	0.0 ms	12.6 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	12.9 KiB
www.transparency.org/assets/dist/assets/focus-trap.esm-CIGEOPzX.js	0.0 ms	6.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/assets/dist/assets/blocks-newsletter-BuxyWg6l.js?v=17750...	0.0 ms	1.5 KiB
www.transparency.org/assets/dist/assets/blocks-header-BltVcra-.js?v=1767876930	0.0 ms	405 B
www.transparency.org/assets/dist/assets/early-BO5cKQNi.js	0.0 ms	310 B
/assets/dist/assets/blocks-select-skip-Bc-m9LMu.js?v=1767...	0.0 ms	224 B
www.transparency.org/assets/dist/assets/global-6dEUJDVK.js	0.0 ms	128 B

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.transparency.org/fonts/oswald-v53-latin-500.woff2	25 ms
www.transparency.org/fonts/open-sans-v34-latin-700.woff2	20 ms
www.transparency.org/fonts/open-sans-v34-latin-regular.woff2	15 ms

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
main#content > section#hero > div.lazy-image > img.no-lazyload `main#content > section#hero > div.lazy-image > img.no-lazyload`	/images/CPI25_WEB_Banner_FIN_2026-02-10-054248_pucz.png?a...	420.9 KiB	346.2 KiB

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

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.5 s

URL	Time Spent
transparency.org/	764 ms
www.transparency.org/	768 ms
www.transparency.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 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: 480 ms 249.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-W42N764	159.5 KiB	67.4 KiB
www.googletagmanager.com/gtag/js?id=G-NHC85YX7P7&cx=c&gtm=4e64h1	172.2 KiB	67.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-1000198207&cx=c&gtm=4e64h1	144.1 KiB	66.4 KiB
/e7376c96-0a25-4b97-b830-39e089879445/cc.js?renew=false&r...	113.2 KiB	26.1 KiB
/uc.js?cbid=e7376c96-0a25-4b97-b830-39e089879445&implemen...	35.5 KiB	22.6 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
www.transparency.org/en/	608 ms	68 ms	6.6 ms
Unattributable	582 ms	28 ms	0.0 ms
/e7376c96-0a25-4b97-b830-39e089879445/cc.js?renew=false&r...	533 ms	212 ms	46 ms
www.googletagmanager.com/gtag/js?id=G-NHC85YX7P7&cx=c&gtm=4e64h1	387 ms	316 ms	67 ms
www.transparency.org/cdn-cgi/challenge-platform/scripts/jsd/main.js	386 ms	358 ms	3.7 ms
www.googletagmanager.com/gtm.js?id=GTM-W42N764	332 ms	262 ms	68 ms
www.googletagmanager.com/gtag/destination?id=AW-1000198207&cx=c&gtm=4e64h1	255 ms	201 ms	52 ms
/uc.js?cbid=e7376c96-0a25-4b97-b830-39e089879445&implemen...	184 ms	162 ms	15 ms
plausible.io/js/plausible.js	111 ms	99 ms	0.7 ms
unpkg.com/alpinejs@3.1.1/dist/cdn.min.js	63 ms	57 ms	4.5 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	50 ms	28 ms	3.6 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.8 s
Other	786 ms
Style & Layout	295 ms
Parse HTML & CSS	282 ms
Script Parsing & Compilation	275 ms
Rendering	49 ms
Garbage Collection	34 ms

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: 0.0 ms 11.2 KiB

URL	Transfer Size	Est Savings
	13.5 KiB	11.2 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,784 KiB

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 14 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Consent `div#CybotCookiebotDialogNav > ul#CybotCookiebotDialogNavList > li.CybotCookiebotDialogNavItem > a#CybotCookiebotDialogNavDeclaration`
Allow all `div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll`

These are opportunities to improve the legibility of your content.

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.grid > nav.col-span-2 > div.flex > a.itz-logo `div.grid > nav.col-span-2 > div.flex > a.itz-logo`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore the results `main#content > section#hero > div.flex > a.btn`

○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

●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

●`[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

●Input buttons have discernible text.

●Form elements have associated labels

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

●Select elements have associated label elements.

●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

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

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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

○`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 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

○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 type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

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

○`<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.

○Identical links have the same purpose.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.transparency.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.transparency.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.transparency.org/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
www.transparency.org/en/manifest.json	`Failed to load resource: the server responded with a status of 404 ()`
www.transparency.org/en/manifest.json	`Failed to load resource: the server responded with a status of 404 ()`
www.transparency.org/en/	`Manifest fetch from https://www.transparency.org/en/manifest.json failed, code 404`
www.transparency.org/en/	`Manifest fetch from https://www.transparency.org/en/manifest.json failed, code 404`

●Uses HTTPS

●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

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
dataprotection@transparency.org `p > span > span > a`
dataprotection@transparency.org `div > p > span > a`

To appear in search results, crawlers need access to your app.

○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 have descriptive text

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid