C — https://huffingtonpost.fr

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

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

core-js · 1488 peers

You 74

Avg 72

At average

0 50 100

Better than 65% of core-js sites See full core-js benchmark →

Facebook · 1367 peers

You 74

Avg 72

At average

0 50 100

Better than 60% of Facebook sites See full Facebook benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

1 control(s) without accessible label

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

Accessibility › Form Accessibility

2 button(s) with no accessible text

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

Accessibility › Link & Button Quality

4 image(s) missing alt attribute

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

Accessibility › Alt Text Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fhuffingtonpost.fr)](https://beavercheck.com/results/4c48aaa5-15b1-4d2e-af58-5358c0028004)

HTML

<a href="https://beavercheck.com/results/4c48aaa5-15b1-4d2e-af58-5358c0028004"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhuffingtonpost.fr" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fhuffingtonpost.fr

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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

1 critical 7 warning

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

Speed (2)

Page loads in 3.8s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 1.3s over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

High main-thread blocking time

+2% bounce

Page is non-interactive for 348ms after first paint

Fix: Defer third-party scripts and split large bundles

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 (1)

1 form field(s) without a label

+2% 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 (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

15 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

€440 investment → €2,043/month returns + EUR 120,500,000 risk avoided

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

Investment

€440

6h · 5 findings

Monthly returns

€2,043 /mo

~€24,511 / year

Conversions recovered €2,042
Bandwidth savings €0.19

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
RGPD EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€80 — 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

€440

5.5 developer hours at €80/hr

Based on France rates (€80/hr)

Quick wins

€80 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /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,002 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveRGPDEAA

No privacy policy link detected
RGPD: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
RGPD: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
RGPD: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

€0.19 /mo

2591.1 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~259 KB per page load
Saves €0.19/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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

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

3.83 s

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

348 ms

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

0.007

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

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

9.37 s

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

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.

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.

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

value: No additional origins are good candidates for preconnecting

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
/css2?family=Montserrat:ital,wght@0,400;0,500;0,600;0,700...	1.3 KiB	813 ms
cmp.huffingtonpost.fr/js/tcfv2-stub.min.js	6.0 KiB	774 ms
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	22.4 KiB	453 ms
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	6.5 KiB
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	549 B

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
cmp.huffingtonpost.fr/js/huffpost.min.js	120.0 s	48.0 KiB
cdn.sitestream.co/libs/storylines/5.3.0/storylines.js	86400.0 s	53.0 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	15.9 KiB
cdn.sitestream.co/libs/storylines/5.2/seenthis-player.110.trackerless.js	86400.0 s	16.3 KiB
cmp.huffingtonpost.fr/js/tcfv2-stub.min.js	120.0 s	6.0 KiB
static.bettergroup.fr/scripts/betterAdManager.js?site_id=c7fecfa8f17849aa	3600.0 s	5.5 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 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: 757 ms

URL	Time Spent
huffingtonpost.fr/	757 ms
www.huffingtonpost.fr/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s

URL	Time Spent
www.huffingtonpost.fr/	1.2 s

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

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	924 ms
Other	729 ms
Style & Layout	688 ms
Script Parsing & Compilation	265 ms
Rendering	119 ms
Parse HTML & CSS	83 ms
Garbage Collection	35 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 20.0 KiB

URL	Transfer Size	Est Savings
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	22.2 KiB	20.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

Estimated savings: 0.0 ms 168.0 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js?cb=31...	187.7 KiB	144.1 KiB
cdn.sitestream.co/libs/storylines/5.3.0/storylines.js	52.1 KiB	23.9 KiB

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
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Newsletters `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Facebook `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Instagram `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Youtube `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
RSS `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
X `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.subNavLeft-categories > div.subNavLeft-block > div.subNavLeft-blockTitle > img.arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.footer-links > div.footer-block > div#groupBtn > img.footer-arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.footer-links > div.footer-links-block > div#legalBtn > img.footer-arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
arrow-down `div.footer-links > div.footer-links-block > div.footer-section > img.footer-arrow`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Threads `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
WhatsApp `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
BlueSky `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
TikTok `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Snapchat `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Dailymotion `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
Flipboard `div.footer-links-block > div.footer-socials > a > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 843 KiB

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 12 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 220 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.website > header.header > nav#navHeader > button#hamburger `div.website > header.header > nav#navHeader > button#hamburger`

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
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`
div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon `div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon`
div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon `div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon`
div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img `div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img`

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
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > a.subNavLeft-logo `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > a.subNavLeft-logo`
div.website > header.header > nav#navHeader > a.navHeader-logo `div.website > header.header > nav#navHeader > a.navHeader-logo`
div.website > footer#desktop__main_footer > div.siteContent > a.footer-logo `div.website > footer#desktop__main_footer > div.siteContent > a.footer-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.

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
FAIRE UN DON `div.website > header.header > nav#navHeader > a.navHeader-donation`
Les sites du groupe `div.siteContent > div.footer-links > div.footer-block > div#groupBtn`
Légal - Infos `div.siteContent > div.footer-links > div.footer-links-block > div#legalBtn`
Suivez-nous `div.siteContent > div.footer-links > div.footer-links-block > div.footer-section`

These are opportunities to improve the legibility of your content.

○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

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

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

●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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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 type="image">` elements have `[alt]` text

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

○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

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

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Ce que cache le gloubi-boulga de la présidentielle, un an avant l’échéance `div.pageContent-left > section.newsFeaturedArticle > a > img`	/2026/04/21/350/0/6720/3780/425/239/70/0/3e551a6_upload-1...	412 x 232	425 x 239	618 x 348
Victor, Dylan et Antoine pendant une épreuve de « Top Chef » `section.newsUne > a.newsUne-item > div.newsUne-media > img`	/2026/04/22/0/1024/3296/3296/105/105/70/0/5631f76_upload-...	105 x 105	105 x 105	158 x 158

●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

●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

●Use a strong HSTS policy

●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

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

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
VIDÉO `div.blockMobilNav > div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link`
partenaires (315) `div.gdpr-hfp-wall__content > div.gdpr-hfp-wall__paragraph > p.gdpr-hfp-wall__text > a`
partenaires publicitaires `div.gdpr-hfp-wall__paragraph > div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > a`
autres partenaires `div.gdpr-hfp-wall__paragraph > div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > a`
ici `div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > span.gdpr-hfp-wall__tcf > a`
Se connecter `div.gdpr-hfp-wall__container > div.gdpr-hfp-wall__footer > p.gdpr-hfp-wall__login > a.cookiewall__link`

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

Content Best Practices

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
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`
div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon `div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon`
div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon `div#mobileNavToggle > div.blockMobilNav-items > a.blockMobilNav-items-link > img.blockMobilNav-items-icon`
div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img `div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > 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 `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

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.

1.00 s

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

1.02 s

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

0 ms

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

0.004

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

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

1.02 s

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.

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 ▾

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.

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.

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.

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

value: No additional origins are good candidates for preconnecting

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
/css2?family=Montserrat:ital,wght@0,400;0,500;0,600;0,700...	1.3 KiB	264 ms
cmp.huffingtonpost.fr/js/tcfv2-stub.min.js	5.9 KiB	206 ms
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	22.5 KiB
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	488 B
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	6.5 KiB

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
cmp.huffingtonpost.fr/js/huffpost.min.js	120.0 s	48.0 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	15.9 KiB
cmp.huffingtonpost.fr/js/tcfv2-stub.min.js	120.0 s	5.9 KiB
static.bettergroup.fr/scripts/betterAdManager.js?site_id=c7fecfa8f17849aa	3600.0 s	5.5 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB

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
Ce que cache le gloubi-boulga de la présidentielle, un an avant l’échéance `div.pageContent-left > section.newsFeaturedArticle > a > img`	/2026/04/21/350/0/6720/3780/768/432/70/0/3e551a6_upload-1...	41.5 KiB	12.7 KiB
Shrimps are seen on a stand at the Central Municipal Market in Athens, Greece o… `section.newsUne > a.newsUne-item > div.newsUne-media > img`	/2026/04/22/236/0/4539/2553/192/108/70/0/07e6422_upload-1...	8.1 KiB	4.7 KiB

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

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

URL	Transfer Size	Est Savings
/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/c...	22.2 KiB	19.6 KiB

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
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`	/bucket/assets/7c7240409a2eefbfce1d6b747b6b21ec56048bfc/i...

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

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

URL	Time Spent
huffingtonpost.fr/	206 ms
www.huffingtonpost.fr/	0.0 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 456 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.5 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 220 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.website > header.header > nav#navHeader > button#hamburger `div.website > header.header > nav#navHeader > button#hamburger`

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
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`
div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img `div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > a.subNavLeft-logo `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > a.subNavLeft-logo`
div.website > header.header > nav#navHeader > a.navHeader-logo `div.website > header.header > nav#navHeader > a.navHeader-logo`
div.website > footer#desktop__main_footer > div.siteContent > a.footer-logo `div.website > footer#desktop__main_footer > div.siteContent > a.footer-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.

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
Faire un don au HuffPost `div.website > header.header > nav#navHeader > a.navHeader-donation`
LE 15 DU MOIS `header.header > nav#subNav > div.subNav-items > a.item`
00h22 `div.timeline-container > div.timeline-wrapper > a.timeline-wrapper--items > p.item`
23h42 `div.timeline-container > div.timeline-wrapper > a.timeline-wrapper--items > p.item`
22h41 `div.timeline-container > div.timeline-wrapper > a.timeline-wrapper--items > p.item`
21h48 `div.timeline-container > div.timeline-wrapper > a.timeline-wrapper--items > p.item`
Plus d'articles `div > div.timeline-show_more--wrapper > div.timeline-show_more--articles > a.timeline__next-arrow`
Les sites du groupe `div.siteContent > div.footer-links > div.footer-block > div#groupBtn`
Suivez-nous `div.siteContent > div.footer-links > div.footer-links-block > div.footer-section`
Légal - Infos `div.siteContent > div.footer-links > div.footer-links-block > div#legalBtn`

These are opportunities to improve the legibility of your content.

○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

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

●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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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 type="image">` elements have `[alt]` text

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

100

Best Practices

●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

●No browser errors logged to the console

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Crawling and Indexing

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
partenaires (315) `div.gdpr-hfp-wall__content > div.gdpr-hfp-wall__paragraph > p.gdpr-hfp-wall__text > a`
partenaires publicitaires `div.gdpr-hfp-wall__paragraph > div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > a`
autres partenaires `div.gdpr-hfp-wall__paragraph > div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > a`
ici `div.gdpr-hfp-wall__block > p.gdpr-hfp-wall__answer > span.gdpr-hfp-wall__tcf > a`
Se connecter `div.gdpr-hfp-wall__container > div.gdpr-hfp-wall__footer > p.gdpr-hfp-wall__login > a.cookiewall__link`

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

Content Best Practices

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
nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close `nav#subNavLeft > div.subNavLeft-body > div.subNavLeft-head > img#subNavLeft-close`
header.header > nav#navHeader > button#hamburger > img `header.header > nav#navHeader > button#hamburger > img`
div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > img `div.newsletter-block-form > div.newsletter-block-content > div.newsletter-block-input > 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 `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://huffingtonpost.fr

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best Practices

User Experience

SEO

Crawling and Indexing

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best Practices

SEO

Crawling and Indexing

Content Best Practices

Keyboard Shortcuts