C — https://lemonde.fr | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 image(s) missing alt attribute

Accessibility › Alt Text Quality

1 image-in-link without alt text

Accessibility › Alt Text Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Flemonde.fr)](https://beavercheck.com/results/10d91965-4b44-4c98-8566-5369a44d5855)

HTML

<a href="https://beavercheck.com/results/10d91965-4b44-4c98-8566-5369a44d5855"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flemonde.fr" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓

SG Singapore

Full audit

736ms

DNS 290ms · TLS 151ms

ES Madrid

111ms

DNS 21ms · TLS 32ms

UN Santa Clara

603ms

DNS 199ms · TLS 137ms

NL Amsterdam

50ms

DNS 11ms · TLS 16ms

UN New York

235ms

DNS 19ms · TLS 74ms

BR Sao Paulo

795ms

DNS 206ms · TLS 199ms

CDN: Fastly (MISS) · Avg TTFB: 422ms · Cache: No cache headers

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

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.

4.78 s

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

7.00 s

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

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

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

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

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

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

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

Request	Cache TTL	Transfer Size
cmp.lemonde.fr/js/lemonde-en.min.js	120.0 s	41.2 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB

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

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.

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

items: [map[reflowTime:61.355 source:map[type:text value:[unattributed]]] map[reflowTime:77.05 source:map[column:49617 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:0.905 source:map[column:109173 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:0.217 source:map[column:38911 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:0.383 source:map[column:39361 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js 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

	URL	Resource Size	Est Savings
Ukrainian President Volodymyr Zelensky in Kyiv, March 24, 2026. `div.lmd-link-clickarea > div.article__media-container > picture.article__media > img.initial`	/2026/03/25/382/0/5722/3814/1600/1066/75/0/09c1bbb_upload...	48.5 KiB	38.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.

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.

URL	Transfer Size	Duration
www.lemonde.fr/en/bucket/resources/english/css/home.683a8dfc0bc84fb8.css	86.7 KiB	469 ms
www.lemonde.fr/en/bucket/resources/english/css/header.ea002fd163f461b5.css	12.0 KiB	156 ms

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.

Estimated savings: 2.2 s

URL	Time Spent
lemonde.fr/	1.2 s
www.lemonde.fr/	1.0 s
www.lemonde.fr/en/	0.0 ms

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

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.

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.

Estimated savings: 940 ms 195.0 KiB

URL	Transfer Size	Est Savings
www.lemonde.fr/en/bucket/resources/english/css/icons.3c02044fe15603ef.css	119.4 KiB	113.3 KiB
www.lemonde.fr/en/bucket/resources/english/css/home.683a8dfc0bc84fb8.css	86.3 KiB	81.6 KiB

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

Category	Time Spent
Style & Layout	747 ms
Script Evaluation	605 ms
Other	442 ms
Script Parsing & Compilation	148 ms
Parse HTML & CSS	101 ms
Rendering	97 ms

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

Estimated savings: 0.0 ms 22.8 KiB

URL	Transfer Size	Est Savings
www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js	37.5 KiB	22.8 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 826 KiB

●JavaScript execution time 0.7 s

●Avoid long main-thread tasks 6 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift 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.

Contrast

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

Failing Elements
SITARA CELINA RAJH FOR LE MONDE `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
Valentine Faure `div.article > a > div.article__wrapper > p.article__byline`
11 min read `section.area > div.article > a > p.article__footer-info`
Alexandre Aublanc `div.article > a > div.article__wrapper > p.article__byline`
8 min read `div.area > div.article > a > p.article__footer-info`
Olivier Faye `div.article > a > div.article__wrapper > p.article__byline`
14 min read `div.area > div.article > a > p.article__footer-info`
Léo Bourdin `div.article > a > div.article__wrapper > p.article__byline`
4 min read `div.area > div.article > a > p.article__footer-info`
Columnist `a > div.article__author > div > div.article__author-desc`
Economist `a > div.article__author > div > div.article__author-desc`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
body#js-body > iframe#multisync-allowlist-iframe `body#js-body > iframe#multisync-allowlist-iframe`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
Editor’s Picks `div#habillagepub > section.zone > div.area > h4.area__title`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Links have a discernible name

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

●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

○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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

○Elements with visible text labels have matching accessible names.

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

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

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

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

Uncrawlable Link
Le Monde in French Le Monde in French `div.Connexion__links > ul > li.js-user-mea-container > a.Connexion__link`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●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

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

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

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

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

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

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

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

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

Request	Cache TTL	Transfer Size
cmp.lemonde.fr/js/lemonde-en.min.js	120.0 s	41.3 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB

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

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

items: [map[reflowTime:66.014 source:map[type:text value:[unattributed]]] map[reflowTime:12.495 source:map[column:109173 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:0.244 source:map[column:38911 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:0.192 source:map[column:39361 line:1 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js urlProvider:network]] map[reflowTime:1.333 source:map[column:10665 line:0 type:source-location url:https://www.lemonde.fr/en/bucket/resources/english/js/home.8c9eed587f86d247.js urlProvider:network]]]

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

lhId: page-0-IMG

nodeLabel: Ukrainian President Volodymyr Zelensky in Kyiv, March 24, 2026.

path: 1,HTML,1,BODY,4,MAIN,2,DIV,0,SECTION,0,SECTION,0,DIV,0,DIV,2,DIV,0,PICTURE,0,IMG

selector: div.lmd-link-clickarea > div.article__media-container > picture.article__media > img.initial

snippet: <img loading="eager" src="https://img.lemde.fr/2026/03/25/382/0/5722/3814/1000/666/75/0/09c1bbb_uplo…" alt="Ukrainian President Volodymyr Zelensky in Kyiv, March 24, 2026." srcset=" https://img.lemde.fr/2026/03/25/382/0/5722/3814/800/533/75/0/09c1bbb_uplo…" sizes="(min-width: 1024px) 421px, 100vw" width="3" height="2" class="initial loaded" data-was-processed="true">

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.

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.

URL	Transfer Size	Duration
www.lemonde.fr/en/bucket/resources/english/css/home.683a8dfc0bc84fb8.css	86.7 KiB	80 ms
www.lemonde.fr/en/bucket/resources/english/css/header.ea002fd163f461b5.css	12.1 KiB

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

	URL	Resource Size	Est Savings
Ukrainian President Volodymyr Zelensky in Kyiv, March 24, 2026. `div.lmd-link-clickarea > div.article__media-container > picture.article__media > img.initial`	/2026/03/25/382/0/5722/3814/1000/666/75/0/09c1bbb_upload-...	28.2 KiB	23.2 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.

Estimated savings: 90 ms 193.4 KiB

URL	Transfer Size	Est Savings
www.lemonde.fr/en/bucket/resources/english/css/icons.3c02044fe15603ef.css	119.4 KiB	113.3 KiB
www.lemonde.fr/en/bucket/resources/english/css/home.683a8dfc0bc84fb8.css	86.3 KiB	80.1 KiB

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

Estimated savings: 0.0 ms 22.5 KiB

URL	Transfer Size	Est Savings
www.lemonde.fr/en/bucket/resources/english/js/common.763e7aa371b4c6d9.js	37.5 KiB	22.5 KiB

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.

Estimated savings: 1.1 s

URL	Time Spent
lemonde.fr/	636 ms
www.lemonde.fr/	440 ms
www.lemonde.fr/en/	0.0 ms

●Time to Interactive 2.3 s

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 878 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.6 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 100 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

Contrast

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

Failing Elements
SITARA CELINA RAJH FOR LE MONDE `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
HANDOUT / AFP `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
ALEX BRANDON / AP `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
CÉSAR DEZFULI FOR LE MONDE `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
AKOS STILLER/THE NEW YORK TIMES-REDUX-REA `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
MAÏA MAZAURETTE `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
Valentine Faure `div.article > a > div.article__wrapper > p.article__byline`
11 min read `section.area > div.article > a > p.article__footer-info`
Alexandre Aublanc `div.article > a > div.article__wrapper > p.article__byline`
8 min read `div.area > div.article > a > p.article__footer-info`
Olivier Faye `div.article > a > div.article__wrapper > p.article__byline`
14 min read `div.area > div.article > a > p.article__footer-info`
Léo Bourdin `div.article > a > div.article__wrapper > p.article__byline`
4 min read `div.area > div.article > a > p.article__footer-info`
Columnist `a > div.article__author > div > div.article__author-desc`
Economist `a > div.article__author > div > div.article__author-desc`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
body#js-body > iframe#multisync-allowlist-iframe `body#js-body > iframe#multisync-allowlist-iframe`

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.

Failing Elements
div.ds-header__top > div.ds-header__top__right > div.ds-header__top__right__user > a.ds-link `div.ds-header__top > div.ds-header__top__right > div.ds-header__top__right__user > a.ds-link`

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.

Navigation

Failing Elements
Editor’s Picks `div#habillagepub > section.zone > div.area > h4.area__title`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

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

Uncrawlable Link
Le Monde in French Le Monde in French `div.Connexion__links > ul > li.js-user-mea-container > a.Connexion__link`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://lemonde.fr

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Navigation

Best Practices

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Navigation

Best Practices

SEO

Crawling and Indexing

Keyboard Shortcuts