Skip to content
Audit Complete

Results for https://europe1.fr

Visit site
FR · EUR (€) · Estimated Applicable regulations: RGPD · ePrivacy Directive · EAA Dev cost: €80/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 15, 2026 23:13 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)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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

Amazon Route 53 sites average 72
At average
Better than 73% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Google Search Console sites average 73
At average
Better than 64% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

'unsafe-eval' found in script source

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

Security › Content Security Policy
2

'unsafe-inline' found in script source

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

Security › Content Security Policy
3

HSTS header is missing

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

Security › Security Headers
4

No <main> landmark found

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

Accessibility › Landmark Structure
5

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
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%2Feurope1.fr)](https://beavercheck.com/results/160a3de1-6f98-429d-9771-720cf5dd47ad)
<a href="https://beavercheck.com/results/160a3de1-6f98-429d-9771-720cf5dd47ad"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Feurope1.fr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Feurope1.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. Your LCP of 8.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.

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

Conversion Barriers

1 critical 7 warning

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

Speed (2)

Page takes 8.4s to load

+12% bounce

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

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

High main-thread blocking time

+2% bounce

Page is non-interactive for 543ms 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

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

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

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

Return on Investment

€400 investment → €5,149/month returns + EUR 120,500,000 risk avoided

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

Investment

€400

5h · 5 findings

Monthly returns

€5,149 /mo

~€61,788 / year

  • Conversions recovered €5,149
  • Bandwidth savings €0.22

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

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

€400

5.0 developer hours at €80/hr

Based on France rates (€80/hr)

Quick wins
€120 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,003 / 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

+6 more

Bandwidth Waste

€0.22 /mo

2959.6 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~296 KB per page load
    Saves €0.22/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.

59
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.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.07 s

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

8.36 s

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

543 ms

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

0.000

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

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

8.67 s

Detailed Report

Audit breakdown by category with detailed findings.

59

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:56.4 source:map[column:220 line:4 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_galG0GPpPGW0KHW0KsIlJ_lyOMj9nD7KNe9xK6_9q90.js?scope=footer&delta=2&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:1.575 source:map[column:3794 line:4 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_galG0GPpPGW0KHW0KsIlJ_lyOMj9nD7KNe9xK6_9q90.js?scope=footer&delta=2&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:46.153 source:map[column:49615 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:3.235 source:map[column:50335 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.249 source:map[column:50393 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.169 source:map[column:50457 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:6.179 source:map[column:49637 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.415 source:map[column:51395 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
a > div.dm-blocks-item > div.dm-news-image > img a > div.dm-blocks-item > div.dm-news-image > img
/var/europe1/storage/styles/image_800_450/public/media/im...51.0 KiB17.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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: 801 ms
URLTime Spent
europe1.fr/801 ms
www.europe1.fr/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 450 ms 34.4 KiB
URLTransfer SizeEst Savings
/var/europe1/storage/css/css_LyySZmgS9-nJJ1MyESA1wydt14fe...26.4 KiB20.0 KiB
17.2 KiB14.4 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: 750 ms 223.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Other755 ms
Style & Layout549 ms
Script Parsing & Compilation175 ms
Rendering117 ms
Parse HTML & CSS66 ms
Garbage Collection60 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.6 KiB
URLTransfer SizeEst Savings
cdn.adswizz.com/adswizz/js/SynchroClient2.js9.0 KiB3.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.

Bouton Europe 1 sur l'app store div.infos-footer-autpromo > div.btns-footer-autopromo > a > img.lazyload
bouton Europe 1 sur le play store div.infos-footer-autpromo > div.btns-footer-autopromo > a > img.lazyload

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

Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 963 KiB
User Timing marks and measures 3 user timings
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 28 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 40 ms
Server Backend Latencies 240 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
INP breakdown
LCP request discovery
Avoid large layout shifts
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.

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
TOP JEU EUROPE 1 - Tentez de gagner vos places carré Or pour le concert de Céli… a > div.content-wrapper > div.content-right > h2
Vous en rêvez, Europe 1 vous l'offre ! Cette semaine, Europe 1 vous propose de … a > div.content-wrapper > div.content-right > p

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.poll-options > div.poll-option > div.form-item > input#poll-option-478 div.poll-options > div.poll-option > div.form-item > input#poll-option-478
div.poll-options > div.poll-option > div.form-item > input#poll-option-481 div.poll-options > div.poll-option > div.form-item > input#poll-option-481

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
header > div.header-wrapper > div.part-left > a.icon-search header > div.header-wrapper > div.part-left > a.icon-search

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Réglages div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-learn-more-button
Accepter et continuer div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-agree-button
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[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
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
77

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.

URLDisplayed sizeActual sizeExpected size
a > div.dm-blocks-item > div.dm-tag-image > img.lazyloaded a > div.dm-blocks-item > div.dm-tag-image > img.lazyloaded
/var/europe1/storage/styles/image_325_183/public/media/im...372 x 210325 x 183558 x 315

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
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
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
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
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.
100
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.

892 ms

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

1.21 s

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

8 ms

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

0.000

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

1.10 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.66 s

Detailed Report

Audit breakdown by category with detailed findings.

96

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.243 source:map[column:220 line:4 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_galG0GPpPGW0KHW0KsIlJ_lyOMj9nD7KNe9xK6_9q90.js?scope=footer&delta=2&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.864 source:map[column:3609 line:4 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_galG0GPpPGW0KHW0KsIlJ_lyOMj9nD7KNe9xK6_9q90.js?scope=footer&delta=2&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:27.509 source:map[column:49615 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:4.06 source:map[column:50335 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.328 source:map[column:50393 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.235 source:map[column:50457 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:6.76 source:map[column:49637 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]] map[reflowTime:0.351 source:map[column:51395 line:2 type:source-location url:https://www.europe1.fr/var/europe1/storage/js/js_I6JO81i9yl2f6WyDmdN6C0T06N76FyHiLNmdNa5xPGE.js?scope=footer&delta=0&language=fr&theme=europe1&include=eJw1ilsKgDAMwC40GZ6o1K6MabWlnchu7wP8yUcSOvgKEC7NmXqO3mgb4FiaggkO9kTfYiqSX0yiWBKfrsZzrqILyrTGb2DxpxNGh-qtZMPKYK7Vcd85bsMwLAQ urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
a > div.dm-blocks-item > div.dm-news-image > img a > div.dm-blocks-item > div.dm-news-image > img
/var/europe1/storage/styles/image_1000_562/public/media/i...74.4 KiB34.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

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 35.9 KiB
URLTransfer SizeEst Savings
/var/europe1/storage/css/css_LyySZmgS9-nJJ1MyESA1wydt14fe...26.4 KiB21.4 KiB
17.2 KiB14.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.6 KiB
URLTransfer SizeEst Savings
cdn.adswizz.com/adswizz/js/SynchroClient2.js9.0 KiB3.6 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 223.7 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.

Bouton Europe 1 sur l'app store div.infos-footer-autpromo > div.btns-footer-autopromo > a > img.lazyload
bouton Europe 1 sur le play store div.infos-footer-autpromo > div.btns-footer-autopromo > a > img.lazyload
L’application Europe 1 à portée de main div.footer-autopromo > div.wrapper-footer-autopromo > div.part-right > img.lazyload

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: 246 ms
URLTime Spent
europe1.fr/246 ms
www.europe1.fr/0.0 ms
Time to Interactive 1.7 s
Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 70 ms
Minify CSS
Avoids enormous network payloads Total size was 916 KiB
User Timing marks and measures 3 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.9 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 50 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
83

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.radio-player > div.player-right > div.volume-control > span.volume-btn div.radio-player > div.player-right > div.volume-control > span.volume-btn

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Régler le volume div#block-europe1-stickyradioplayer > div.radio-player > div.player-right > div.volume-control

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.

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
TOP JEU EUROPE 1 - Tentez de gagner vos places carré Or pour le concert de Céli… a > div.content-wrapper > div.content-right > h2
Vous en rêvez, Europe 1 vous l'offre ! Cette semaine, Europe 1 vous propose de … a > div.content-wrapper > div.content-right > p

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.poll-options > div.poll-option > div.form-item > input#poll-option-478 div.poll-options > div.poll-option > div.form-item > input#poll-option-478
div.poll-options > div.poll-option > div.form-item > input#poll-option-481 div.poll-options > div.poll-option > div.form-item > input#poll-option-481

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
header > div.header-wrapper > div.part-left > a.icon-search header > div.header-wrapper > div.part-left > a.icon-search
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image
div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image div.dernieres-actualites-content > div.categorie > div.article > a.dm-news-image

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Réglages div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-learn-more-button
Accepter et continuer div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-agree-button
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
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
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
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback