Skip to content
Audit Complete

Results for https://project-syndicate.org

Visit site
E-commerce · estimated Tracking: purchases
Spain Spain · Madrid Completed: Apr 22, 2026 20:04 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Cart Functionality · 420 peers
You 76
·
Avg 72
At average
0 50 100
Better than 83% of Cart Functionality sites See full Cart Functionality benchmark →
Amazon Route 53 · 803 peers
You 76
·
Avg 72
At average
0 50 100
Better than 85% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

2 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
5

71 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fproject-syndicate.org)](https://beavercheck.com/results/cdf26b6d-c773-46f8-8e2d-9c8823ffa617)
<a href="https://beavercheck.com/results/cdf26b6d-c773-46f8-8e2d-9c8823ffa617"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fproject-syndicate.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fproject-syndicate.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 14.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 14.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~33%.

Speed (2)

Page takes 14.4s to load

+12% bounce

Users abandon at ~3s — you're 11.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 700ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

2 form field(s) without a label

+4% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

103 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €476/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +1243%

Investment

€425

5h · 5 findings

Monthly returns

€476 /mo

~€5,707 / year

  • Conversions recovered €475
  • Bandwidth savings €0.70

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,008 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+6 more

Bandwidth Waste

€0.70 /mo

9419.7 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~942 KB per page load
    Saves €0.70/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

40
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
82
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.39 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

14.37 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

700 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.241

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.48 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

17.08 s

Detailed Report

Audit breakdown by category with detailed findings.

40

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.241276] map[node:map[boundingRect:map[bottom:695 height:567 left:10 right:402 top:128 width:392] lhId:page-12-DIALOG nodeLabel:As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … path:1,HTML,1,BODY,25,DIALOG selector:body > dialog#message-dialog snippet:<dialog class="dialog dialog--message message message--admin" id="message-dialog" role="dialog" aria-modal="true" aria-labelledby="message-dialog-title" open=""> type:node] score:0.240162 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:480 height:302 left:10 right:402 top:178 width:392] lhId:page-0-IMG nodeLabel:dialog#message-dialog > div.dialog__content > figure > img path:1,HTML,1,BODY,25,DIALOG,1,DIV,0,FIGURE,0,IMG selector:dialog#message-dialog > div.dialog__content > figure > img snippet:<img src="https://webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab1…"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:467 height:64 left:20 right:391 top:403 width:371] lhId:page-10-SPAN nodeLabel:describes a model dominated by retail investors that delivers more short-term v… path:1,HTML,1,BODY,15,MAIN,5,SECTION,0,OL,0,LI,0,ARTICLE,3,DIV,1,DIV,2,SPAN selector:article.article-card > div.article-card__header > div.article-card__excerpt > span snippet:<span> type:node] score:0.001114 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notosans/v42/o-0bIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjc5a7du3mhPy0.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notoserif/v33/ga6daw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTYf6D33WsNFH.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notoserif/v33/ga6faw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_P3_ct_NFiQg.woff2]]] type:subitems]]]

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.

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.

URLResource SizeEst Savings
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img
webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab147e.png234.7 KiB175.7 KiB
Tencent headquarters building exterior in Shenzhen, China, photographed on Marc… div.article-card__image > figure.image > picture > img
/library/7a204d35b82eb950d5ce0f1646326f21.16-9-xlarge.1.jpg143.9 KiB105.1 KiB
Woman walking past graffiti in central Athens reading “cut the debt, IMF go hom… div.article-card__image > figure.image > picture > img
/library/df7b3af0c72e9a2e3163ebc5ae5694d5.16-9-xlarge.1.jpg128.2 KiB89.4 KiB
Moroccan worker inspects a Renault Logan on the production line during the rele… div.article-card__image > figure.image > picture > img
/library/75e6ba362294f57645e6e4f3a099476a.16-9-xlarge.1.jpg115.7 KiB76.9 KiB
Humanoid robots labeled “Qinglong” sorting packages along a logistics conveyor … div.article-card__image > figure.image > picture > img
/library/bec80f6e77af9b412b478c14c6f45c2e.16-9-xlarge.1.jpg109.3 KiB70.5 KiB
Traders work on the floor of the New York Stock Exchange during a surge in majo… div.article-card__image > figure.image > picture > img
/library/746e81c081b2a506fffdc14c127e5b27.16-9-xlarge.1.jpg99.2 KiB60.4 KiB
A lone man walks near the New York Stock Exchange building, with strong shadows… div.article-card__image > figure.image > picture > img
/library/5e7d4080cf183402724539f1b21a57cd.16-9-xlarge.1.jpg94.1 KiB55.3 KiB
Employee at the Korea Exchange in Seoul smiles while looking at her mobile phon… div.article-card__image > figure.image > picture > img
/library/54948d9326c5ff7801ec2094560c7dd1.16-9-xlarge.1.jpg78.2 KiB42.3 KiB
U.S. President Donald Trump greets Israeli Prime Minister Benjamin Netanyahu at… div.article-card__image > figure.image > picture > img
/library/f5d89e319df6fcbb807d94727f98b929.16-9-xlarge.1.jpg59.9 KiB32.4 KiB
Plume of smoke rising after a reported Iranian strike on fuel tanks in Muharraq… div.article-card__image > figure.image > picture > img
/library/b598b22bbd89d5d119fdb7654d48efba.16-9-xlarge.1.jpg45.9 KiB24.8 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-IMG
nodeLabel: dialog#message-dialog > div.dialog__content > figure > img
path: 1,HTML,1,BODY,25,DIALOG,1,DIV,0,FIGURE,0,IMG
selector: dialog#message-dialog > div.dialog__content > figure > img
snippet: <img src="https://webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab1…">

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

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: 836 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … body > dialog#message-dialog
0.240
describes a model dominated by retail investors that delivers more short-term v… article.article-card > div.article-card__header > div.article-card__excerpt > span
0.001

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: 470 ms 43.0 KiB
URLTransfer SizeEst Savings
/css/styles.min.css?v=tHx_zKUaEooV4cYyQnbVvI8_6IhtqKkvz3C...50.9 KiB43.0 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

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.

CategoryTime Spent
Script Evaluation1.7 s
Other521 ms
Style & Layout484 ms
Script Parsing & Compilation253 ms
Rendering90 ms
Parse HTML & CSS51 ms
Garbage Collection19 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages that use WebXR are not currently eligible for back/forward cache.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img
webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab147e.png

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

Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 130 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
INP breakdown
89

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … body > dialog#message-dialog

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img

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.

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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Links are distinguishable without relying on color.
Links have a discernible name
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
All heading elements contain content.
`[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 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
Document has a `<title>` element
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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"]`
Document has a main landmark.
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
81

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 / WarningSource
Unload event listeners are deprecated and will be removed.
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 browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
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
82

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img

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 meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a `<title>` element
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

75
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
82
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

855 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.35 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

12 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.129

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.26 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.79 s

Detailed Report

Audit breakdown by category with detailed findings.

75

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.129247] map[node:map[boundingRect:map[bottom:817 height:695 left:355 right:995 top:123 width:640] lhId:page-21-DIALOG nodeLabel:As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … path:1,HTML,1,BODY,25,DIALOG selector:body > dialog#message-dialog snippet:<dialog class="dialog dialog--message message message--admin" id="message-dialog" role="dialog" aria-modal="true" aria-labelledby="message-dialog-title" open=""> type:node] score:0.127635 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:665 height:492 left:355 right:995 top:173 width:640] lhId:page-0-IMG nodeLabel:dialog#message-dialog > div.dialog__content > figure > img path:1,HTML,1,BODY,25,DIALOG,1,DIV,0,FIGURE,0,IMG selector:dialog#message-dialog > div.dialog__content > figure > img snippet:<img src="https://webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab1…"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:552 height:84 left:685 right:949 top:468 width:264] lhId:page-16-SPAN nodeLabel:doubts that the technology’s contribution to tax revenues will outweigh massive… path:1,HTML,1,BODY,15,MAIN,5,SECTION,0,OL,2,LI,0,ARTICLE,3,DIV,1,DIV,1,SPAN selector:article.article-card > div.article-card__header > div.article-card__excerpt > span snippet:<span> type:node] score:0.001612 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notosans/v42/o-0bIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjc5a7du3mhPy0.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notoserif/v33/ga6daw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTYf6D33WsNFH.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/notoserif/v33/ga6faw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_P3_ct_NFiQg.woff2]]] type:subitems]]]

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:56.779 source:map[type:text value:[unattributed]]]]

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.

URLResource SizeEst Savings
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img
webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab147e.png234.7 KiB183.4 KiB
Tencent headquarters building exterior in Shenzhen, China, photographed on Marc… div.article-card__image > figure.image > picture > img
/library/7a204d35b82eb950d5ce0f1646326f21.16-9-xlarge.1.jpg143.9 KiB135.0 KiB
Woman walking past graffiti in central Athens reading “cut the debt, IMF go hom… div.article-card__image > figure.image > picture > img
/library/df7b3af0c72e9a2e3163ebc5ae5694d5.16-9-xlarge.1.jpg128.2 KiB119.3 KiB
Moroccan worker inspects a Renault Logan on the production line during the rele… div.article-card__image > figure.image > picture > img
/library/75e6ba362294f57645e6e4f3a099476a.16-9-xlarge.1.jpg115.7 KiB106.7 KiB
Humanoid robots labeled “Qinglong” sorting packages along a logistics conveyor … div.article-card__image > figure.image > picture > img
/library/bec80f6e77af9b412b478c14c6f45c2e.16-9-xlarge.1.jpg109.3 KiB100.4 KiB
A lone man walks near the New York Stock Exchange building, with strong shadows… div.article-card__image > figure.image > picture > img
/library/5e7d4080cf183402724539f1b21a57cd.16-9-xlarge.1.jpg94.1 KiB85.2 KiB
Traders work on the floor of the New York Stock Exchange during a surge in majo… div.article-card__image > figure.image > picture > img
/library/746e81c081b2a506fffdc14c127e5b27.16-9-xlarge.1.jpg99.2 KiB61.1 KiB
U.S. President Donald Trump greets Israeli Prime Minister Benjamin Netanyahu at… div.article-card__image > figure.image > picture > img
/library/f5d89e319df6fcbb807d94727f98b929.16-9-xlarge.1.jpg59.9 KiB53.6 KiB
Employee at the Korea Exchange in Seoul smiles while looking at her mobile phon… div.article-card__image > figure.image > picture > img
/library/54948d9326c5ff7801ec2094560c7dd1.16-9-xlarge.1.jpg78.2 KiB42.9 KiB
Plume of smoke rising after a reported Iranian strike on fuel tanks in Muharraq… div.article-card__image > figure.image > picture > img
/library/b598b22bbd89d5d119fdb7654d48efba.16-9-xlarge.1.jpg45.9 KiB41.0 KiB
Image for Secure your copy of <em>PS Quarterly: Winners & Losers</em> – and sav… div > figure.image > picture > img
/library/ff97447608e6eeb1e7495525e2cfaebb.4-3-large.1.jpg48.0 KiB38.0 KiB
Humanoid robots labeled “Qinglong” sorting packages along a logistics conveyor … li.listing > figure.image > picture > img
/library/bec80f6e77af9b412b478c14c6f45c2e.2-1-medium.1.jpg23.1 KiB14.8 KiB
Moroccan worker inspects a Renault Logan on the production line during the rele… li.listing > figure.image > picture > img
/library/75e6ba362294f57645e6e4f3a099476a.2-1-medium.1.jpg23.1 KiB14.8 KiB
Traders work on the floor of the New York Stock Exchange during a surge in majo… li.listing > figure.image > picture > img
/library/746e81c081b2a506fffdc14c127e5b27.2-1-medium.1.jpg20.3 KiB11.9 KiB
Woman walking past graffiti in central Athens reading “cut the debt, IMF go hom… li.listing > figure.image > picture > img
/library/df7b3af0c72e9a2e3163ebc5ae5694d5.2-1-medium.1.jpg18.3 KiB10.0 KiB
A lone man walks near the New York Stock Exchange building, with strong shadows… li.listing > figure.image > picture > img
/library/5e7d4080cf183402724539f1b21a57cd.2-1-medium.1.jpg17.5 KiB9.1 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-IMG
nodeLabel: dialog#message-dialog > div.dialog__content > figure > img
path: 1,HTML,1,BODY,25,DIALOG,1,DIV,0,FIGURE,0,IMG
selector: dialog#message-dialog > div.dialog__content > figure > img
snippet: <img src="https://webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab1…">

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

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: 286 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … body > dialog#message-dialog
0.128
doubts that the technology’s contribution to tax revenues will outweigh massive… article.article-card > div.article-card__header > div.article-card__excerpt > span
0.002

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

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: 140 ms 41.2 KiB
URLTransfer SizeEst Savings
/css/styles.min.css?v=tHx_zKUaEooV4cYyQnbVvI8_6IhtqKkvz3C...50.9 KiB41.2 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages that use WebXR are not currently eligible for back/forward cache.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img
webapi.project-syndicate.org/library/a6fdec76a1a94dc5be799068b0ab147e.png

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

Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
User Timing marks and measures 10 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.8 s
Avoid long main-thread tasks 2 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 210 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 50 ms
INP breakdown
89

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
As the US and China surge ahead in AI, can Europe keep up? Don’t miss our next … body > dialog#message-dialog

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img

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.

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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Links are distinguishable without relying on color.
Links have a discernible name
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
All heading elements contain content.
`[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 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
Document has a `<title>` element
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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"]`
Document has a main landmark.
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
81

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 / WarningSource
Unload event listeners are deprecated and will be removed.
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 browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
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
82

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
dialog#message-dialog > div.dialog__content > figure > img dialog#message-dialog > div.dialog__content > figure > img

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 meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a `<title>` element
Document has a valid `rel=canonical`

Send Feedback