Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cmp.lemonde.fr/js/lemonde.min.js	120.0 s	48.2 KiB
cdn.sitestream.co/libs/storylines/5.0.12/storylines.js	86400.0 s	57.9 KiB
cdn.sitestream.co/libs/storylines/5.0.12/seenthis-player.105.js	86400.0 s	16.5 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:69.276 source:map[type:text value:[unattributed]]] map[reflowTime:150.877 source:map[column:10665 line:0 type:source-location url:https://www.lemonde.fr/bucket/resources/front/js/home.11d1729d46f60f0e.js urlProvider:network]] map[reflowTime:46.529 source:map[column:163978 line:1 type:source-location url:https://cdn.sitestream.co/libs/storylines/5.0.12/storylines.js urlProvider:network]] map[reflowTime:1.305 source:map[column:139926 line:1 type:source-location url:https://cdn.sitestream.co/libs/storylines/5.0.12/storylines.js urlProvider:network]] map[reflowTime:0.728 source:map[column:140601 line:1 type:source-location url:https://cdn.sitestream.co/libs/storylines/5.0.12/storylines.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.lmd-link-clickarea > div.article__media-container > picture.article__media > img.initial `div.lmd-link-clickarea > div.article__media-container > picture.article__media > img.initial`	/2026/04/04/0/0/1620/1080/1600/1066/75/0/1118a04_upload-1...	70.2 KiB	65.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

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.

URL	Transfer Size	Duration
www.lemonde.fr/bucket/resources/front/css/home.d0fae6f00cc7d2be.css	103.3 KiB	957 ms
www.lemonde.fr/bucket/resources/front/css/header.ba6ded35966a9df8.css	12.0 KiB	159 ms

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 450 ms 207.0 KiB

URL	Transfer Size	Est Savings
www.lemonde.fr/bucket/resources/front/css/icons.4946a6dfb1e5a258.css	118.7 KiB	112.1 KiB
www.lemonde.fr/bucket/resources/front/css/home.d0fae6f00cc7d2be.css	103.0 KiB	94.8 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s 212.8 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604030101/pubads_impl.js?cb=31...	182.6 KiB	140.3 KiB
cdn.sitestream.co/libs/storylines/5.0.12/storylines.js	57.1 KiB	27.8 KiB
www.lemonde.fr/bucket/resources/front/js/common.3d34f58f2e440228.js	39.5 KiB	23.1 KiB
www.lemonde.fr/bucket/resources/front/js/home.11d1729d46f60f0e.js	32.3 KiB	21.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.lemonde.fr/	1.1 s	93 ms	10 ms
www.lemonde.fr/bucket/resources/front/js/home.11d1729d46f60f0e.js	843 ms	230 ms	18 ms
Unattributable	622 ms	58 ms	0.0 ms
/pagead/managed/js/gpt/m202604030101/pubads_impl.js?cb=31...	449 ms	227 ms	218 ms
cdn.sitestream.co/libs/storylines/5.0.12/storylines.js	381 ms	92 ms	31 ms
www.lemonde.fr/bucket/resources/front/js/common.3d34f58f2e440228.js	316 ms	169 ms	33 ms
/bucket/resources/front/96cb949ce39c9212.2490cffb4c967e8c...	190 ms	171 ms	14 ms
cmp.lemonde.fr/js/lemonde.min.js	168 ms	109 ms	47 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	164 ms	144 ms	19 ms
/bucket/resources/front/03ea4fa719e85114.2490cffb4c967e8c...	88 ms	74 ms	12 ms
www.lemonde.fr/bucket/resources/front/css/home.d0fae6f00cc7d2be.css	59 ms	0.0 ms	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Style & Layout	1.7 s
Script Evaluation	1.5 s
Other	722 ms
Script Parsing & Compilation	434 ms
Parse HTML & CSS	195 ms
Rendering	54 ms

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

●Layout shift culprits

●Document request latency

●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 1,264 KiB

●Avoid long main-thread tasks 18 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
CAMILLE MILLERAND/DIVERGENCE « POUR LE MONDE » `section.area > div.article > div.lmd-link-clickarea > div.article__media-credit`
CHRONIQUE `div.article > div.lmd-link-clickarea > div.article__footer > p.article__type`
ENQUÊTE `div.article > div.lmd-link-clickarea > div.article__footer > p.article__type`
Henri Seckel `div.article > a > div.article__wrapper > p.article__byline`
15 min de lecture `section.area > div.article > a > p.article__footer-info`
TRIBUNE `div.article > div.lmd-link-clickarea > div.article__footer > p.article__type`
CHRONIQUE `div.article > div.lmd-link-clickarea > div.article__footer > p.article__type`
TRIBUNE `div.article > div.lmd-link-clickarea > div.article__footer > p.article__type`
Piotr Smolar `div.article > a > div.article__wrapper > p.article__byline`
6 min de lecture `div.area > div.article > a > p.article__footer-info`
Gilles Rof et Roxana Azimi `div.article > a > div.article__wrapper > p.article__byline`
6 min de lecture `div.area > div.article > a > p.article__footer-info`
Christophe Ayad `div.article > a > div.article__wrapper > p.article__byline`
3 min de lecture `div.area > div.article > a > p.article__footer-info`
Rédacteur en chef au « Monde » `a > div.article__author > div > div.article__author-desc`
avec Le Monde `div.services__content > div.bizdev-list > div.bizdev-list__header > div.bizdev-list__header-partner`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.services > div.services__content > div.js-bizdev > a `div.services > div.services__content > div.js-bizdev > a`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sélection de la rédaction `div#habillagepub > section.zone > div.area > h4.area__title`

These are opportunities to improve keyboard navigation in your application.

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
NOUVEAU Météo du climat Consulter la carte et les données climatiques. `div#habillagepub > section.zone > section.area > a.ds-teasercard`

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

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

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

○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

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
Le Monde in English Le Monde in English `div.Connexion__links > ul > li.js-user-mea-container > a.Connexion__link`
partenaires (315) `div.c-explanation > div.c-explanation__block > p.c-explanation__answer > a`
partenaires publicitaires `div.gdpr-lmd-wall__content > div.c-explanation__block > p.c-explanation__answer > a`
autres partenaires `div.gdpr-lmd-wall__content > div.c-explanation__block > p.c-explanation__answer > a`
ici `div.c-explanation__block > p.c-explanation__answer > span.gdpr-lmd-wall__tcf > a`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`