Skip to content
https://cnrs.fr

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

40

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Une chercheuse prélève de l'eau dans un ruisseau section.inner > div.feature__img > picture > img
/sites/default/files/styles/mobile_banner/public/2026-04/...241.6 KiB199.3 KiB
Un scientifique relève des échantillons dans une forêt de La Réunion div.content-visual > span > picture > img
/sites/default/files/styles/homepage_news_mobile/public/i...248.8 KiB197.3 KiB
div.featured > a.article__link > picture > img div.featured > a.article__link > picture > img
/sites/default/files/styles/homepage_news_mobile/public/i...246.2 KiB194.8 KiB
Médaille de bronze du CNRS div.content-visual > span > picture > img
/sites/default/files/styles/homepage_news_mobile/public/i...66.7 KiB15.2 KiB
div.zoom__card > a > picture > img div.zoom__card > a > picture > img
/sites/default/files/styles/homepage_news_mobile/public/i...63.5 KiB12.7 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1258.625 label:Time to first byte subpart:timeToFirstByte] map[duration:207.563 label:Resource load delay subpart:resourceLoadDelay] map[duration:1265.136 label:Resource load duration subpart:resourceLoadDuration] map[duration:53.101 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Une chercheuse prélève de l'eau dans un ruisseau
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,MAIN,1,DIV,1,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,PICTURE,4,IMG
selector: section.inner > div.feature__img > picture > img
snippet: <img loading="eager" width="768" height="384" src="https://www.cnrs.fr/sites/default/files/styles/mobile_banner/public/2026-0…" alt="Une chercheuse prélève de l'eau dans un ruisseau">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Une chercheuse prélève de l'eau dans un ruisseau
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,MAIN,1,DIV,1,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,PICTURE,4,IMG
selector: section.inner > div.feature__img > picture > img
snippet: <img loading="eager" width="768" height="384" src="https://www.cnrs.fr/sites/default/files/styles/mobile_banner/public/2026-0…" alt="Une chercheuse prélève de l'eau dans un ruisseau">

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
value: no origins were preconnected
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.

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.

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: 2.3 s
URLTime Spent
cnrs.fr/1.4 s
www.cnrs.fr/970 ms
www.cnrs.fr/fr0.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

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: 250 ms 32.4 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_K2eY2aFs3JCXtciFNpgaNMiNZu6L...34.8 KiB32.4 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.

URLTotal CPU TimeScript EvaluationScript Parse
/TSPD/087dc22938ab2000cc40d18b6180f1c9470cce7869b54a97370...3.8 s3.6 s33 ms
www.cnrs.fr/libraries/MathJax/es5/tex-mml-chtml.js581 ms414 ms152 ms
Unattributable564 ms18 ms0.0 ms
www.cnrs.fr/fr562 ms16 ms2.4 ms
static.axept.io/sdk.js473 ms386 ms82 ms
/sites/default/files/js/js_b2tTzgwUeUO630pbzoKxLY_CqfcJPZ...136 ms112 ms19 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.

CategoryTime Spent
Script Evaluation4.7 s
Other659 ms
Style & Layout371 ms
Script Parsing & Compilation346 ms
Rendering101 ms
Parse HTML & CSS65 ms
Garbage Collection59 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Accueil footer.footer > div.inner > div.home__small-inner > img
www.cnrs.fr/themes/custom/cnrs/logo-footer.svg

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,984 KiB
●Avoid long main-thread tasks 10 long tasks found
●Network Requests
●Network Round Trip Times 210 ms
●Server Backend Latencies 210 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
91

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Presse div.home__small-inner > div.footer__child > li.text-black > a
Recrutement div.home__small-inner > div.footer__child > li.text-black > a
Entreprises div.home__small-inner > div.footer__child > li.text-black > a
Interne div.home__small-inner > div.footer__child > li.text-black > a

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

Names and labels

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.news__featured > div.news__featured--content > div.featured > a.article__link div.news__featured > div.news__featured--content > div.featured > a.article__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.

○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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●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.
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
TypeError: Cannot read properties of undefined (reading 'toString') at Drupal.checkPlain (https://www.cnrs.fr/sites/default/files/js/js_b2tTzgwUeUO630pbzoKxLY_CqfcJPZrB-ApaBbZfMgw.js?scope=footer&delta=0&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:13:877) at https://www.cnrs.fr/sites/default/files/js/js_b2tTzgwUeUO630pbzoKxLY_CqfcJPZrB-ApaBbZfMgw.js?scope=footer&delta=0&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:13:1167 at Array.forEach (<anonymous>) at Drupal.formatString (https://www.cnrs.fr/sites/default/files/js/js_b2tTzgwUeUO630pbzoKxLY_CqfcJPZrB-ApaBbZfMgw.js?scope=footer&delta=0&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:13:1094) at Drupal.t (https://www.cnrs.fr/sites/default/files/js/js_b2tTzgwUeUO630pbzoKxLY_CqfcJPZrB-ApaBbZfMgw.js?scope=footer&delta=0&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:13:2097) at base.addReplacement (https://www.cnrs.fr/sites/default/files/js/js_aAJjDYyF0qLfKGR7EGkrAZZEr83nHqligfw5kyojdBc.js?scope=footer&delta=3&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:10:857) at base.refresh (https://www.cnrs.fr/sites/default/files/js/js_aAJjDYyF0qLfKGR7EGkrAZZEr83nHqligfw5kyojdBc.js?scope=footer&delta=3&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:10:412) at base.init (https://www.cnrs.fr/sites/default/files/js/js_aAJjDYyF0qLfKGR7EGkrAZZEr83nHqligfw5kyojdBc.js?scope=footer&delta=3&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:10:301) at new $.cnrs.cnrs_rgpdAxeptio (https://www.cnrs.fr/sites/default/files/js/js_aAJjDYyF0qLfKGR7EGkrAZZEr83nHqligfw5kyojdBc.js?scope=footer&delta=3&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:10:1544) at HTMLIFrameElement.<anonymous> (https://www.cnrs.fr/sites/default/files/js/js_aAJjDYyF0qLfKGR7EGkrAZZEr83nHqligfw5kyojdBc.js?scope=footer&delta=3&language=fr&theme=cnrs&include=eJx1j1ESgzAIRC-UCUdyMEGljSETSM3xa7Wt_ekP85ZZYMFOxVhgRCU3khnVgXoRpThMnHapgM1k0DaubP8sM2WqmFzIh18XPPFY-6IhyLpKhh_2k4hlMdLTUecS4Usez2QuSJI6SocPXJ1IE7ZkjrolzneItRVM_i0dl9f5M8OKttywg0qrgVxZxEQ3LgQXes77hw-mTeGoHveRJ0tVcno:10:1736)

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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 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
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<html><head><title>Request Rejected</title></head><body>The requested URL was rejected. Please consult with your administrator.<br><br>Your support ID is: <14617951528874938408><br><br><a href='javascript:history.back();'>[Go Back]</body></html>Unknown directive

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

Send Feedback