Skip to content
https://francebleu.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.

33

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:2.695 source:map[type:text value:[unattributed]]] map[reflowTime:61.528 source:map[column:2781 line:0 type:source-location url:https://www.ici.fr/client/immutable/nodes/3.CbOPDZWF.js urlProvider:network]] map[reflowTime:70.5 source:map[column:1659 line:0 type:source-location url:https://www.ici.fr/client/immutable/chunks/XJ2bW64B.js urlProvider:network]] map[reflowTime:18.873 source:map[column:2558 line:0 type:source-location url:https://www.ici.fr/client/immutable/chunks/DVyLFctp.js urlProvider:network]] map[reflowTime:4.094 source:map[column:184 line:0 type:source-location url:https://www.ici.fr/client/immutable/chunks/Dk5TEw9t.js urlProvider:network]] map[reflowTime:63.108 source:map[column:3208 line:0 type:source-location url:https://www.ici.fr/client/immutable/chunks/gObnV7rn.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.

URLResource SizeEst Savings
div.IciVisualOverlay > div.visualWrapper > picture.IciVisual > img.svelte-1cksh76 div.IciVisualOverlay > div.visualWrapper > picture.IciVisual > img.svelte-1cksh76
www.ici.fr/pikapi/images/d8244caf-db29-4496-9acf-f9599861f3a6/1200x680195.9 KiB139.4 KiB
li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76 li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76
www.ici.fr/pikapi/images/3ed73760-7416-471d-93ea-acb6daec6eea/1200x68074.5 KiB51.4 KiB
div.main-wrapper > main.HomePage > section#hp-hot-topics-section > ::before div.main-wrapper > main.HomePage > section#hp-hot-topics-section > ::before
www.ici.fr/pikapi/images/d8244caf-db29-4496-9acf-f9599861f3a6/560x31547.2 KiB18.4 KiB
li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76 li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76
www.ici.fr/pikapi/images/a5098987-a087-430e-83c1-249fcc32e6fb/200x20012.6 KiB6.1 KiB
li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76 li.IciCard > div.media > picture.IciVisual > img.svelte-1cksh76
www.ici.fr/pikapi/images/a6fd307a-7793-42f7-97e6-6c6cecd36fa8/200x20011.6 KiB5.0 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:1295.281 label:Time to first byte subpart:timeToFirstByte] map[duration:2208.377 label:Element render delay subpart:elementRenderDelay]]
lhId: page-5-P
nodeLabel: Avec votre accord, nos partenaires et nous utilisons des cookies ou technologie…
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,P
selector: div > div.didomi-popup-notice-text-container > div.didomi-popup-notice-text > p
snippet: <p>

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.

URLTransfer SizeDuration
www.ici.fr/client/immutable/assets/10.Dv-pAOFG.css5.3 KiB151 ms
www.ici.fr/js/polyfill.js1.3 KiB
www.ici.fr/client/immutable/assets/ColorExpressionSection.Doni9XEO.css1.1 KiB
www.ici.fr/client/immutable/assets/Carousel.D6gfAHI0.css1.7 KiB
www.ici.fr/client/immutable/assets/TagClickable.B8Q5h96R.css414 B
www.ici.fr/client/immutable/assets/IciElectionsMn2026DataSources.BPdmGHpI.css406 B
www.ici.fr/client/immutable/assets/IciElectionsMn2026Infos.DpEKqiPm.css430 B
www.ici.fr/client/immutable/assets/ShareContent.ioehy9to.css732 B
www.ici.fr/client/immutable/assets/Skeleton.BTB1Ydoj.css554 B
www.ici.fr/client/immutable/assets/music.CthJWGen.css1.4 KiB
www.ici.fr/client/immutable/assets/RecommendedSection.BQSjSb3q.css618 B
www.ici.fr/client/immutable/assets/ConceptCard.CmvUdwC1.css488 B
www.ici.fr/client/immutable/assets/ArticleLayout.DICBwTxZ.css1.9 KiB
www.ici.fr/client/immutable/assets/Themes._f4SnoHO.css691 B
www.ici.fr/client/immutable/assets/Heading.DRCJyGZk.css712 B
www.ici.fr/client/immutable/assets/TopArticles.DTkuFzWg.css739 B
www.ici.fr/client/immutable/assets/FtvProgramSection.CZbx_J6R.css994 B
www.ici.fr/client/immutable/assets/SeeMoreContent.CotUxBiN.css610 B
www.ici.fr/client/immutable/assets/Number.hC8D2DG1.css342 B
www.ici.fr/client/immutable/assets/IciDataSources.DePLsz6h.css375 B
www.ici.fr/client/immutable/assets/Visual.CekMnRhv.css596 B
www.ici.fr/client/immutable/assets/PlayButton.CN_meGLO.css542 B
www.ici.fr/client/immutable/assets/IciGeolocationPanel.BbFv2896.css365 B
www.ici.fr/client/immutable/assets/LiveStatusTag.BJf-dseh.css306 B
www.ici.fr/client/immutable/assets/SimpleMenu.BrGJiibO.css803 B
www.ici.fr/client/immutable/assets/MultipleMenu.BTFHcihs.css1.0 KiB
www.ici.fr/client/immutable/assets/NewsBulletin.Da6QNV1x.css751 B
www.ici.fr/client/immutable/assets/IciRegionsPanel.Deb7TmNh.css834 B
www.ici.fr/client/immutable/assets/IciLocaleListPanel.Cze6jnYN.css1.4 KiB
www.ici.fr/client/immutable/assets/SearchBox.BJcf_puo.css1.4 KiB
www.ici.fr/client/immutable/assets/Search.DKPMMUhG.css630 B
www.ici.fr/client/immutable/assets/IciShareContentPanel.DuinO_QF.css438 B
www.ici.fr/client/immutable/assets/IciFranceBleuPanel.OMeBiYrG.css646 B
www.ici.fr/client/immutable/assets/IciLegalNoticePanel.DcVSjpLj.css368 B
www.ici.fr/client/immutable/assets/testCards.C0b9Uucd.css414 B
www.ici.fr/client/immutable/assets/Card.Cu8s-Cib.css1.4 KiB
www.ici.fr/client/immutable/assets/Tag.DuQ8Z0Ll.css621 B
www.ici.fr/client/immutable/assets/Link.DvXo4hQt.css257 B
www.ici.fr/client/immutable/assets/IciNewsBulletinsPanel.BANliQGv.css417 B
www.ici.fr/client/immutable/assets/Player.DuHeVO9p.css11.1 KiB302 ms
www.ici.fr/client/immutable/assets/3.Db7_ANNW.css5.5 KiB
www.ici.fr/client/immutable/assets/Tooltip.BjGjIxrD.css619 B
www.ici.fr/client/immutable/assets/SelectMenu.CNtfeUPH.css685 B
www.ici.fr/client/immutable/assets/Modal.-8QF5gsD.css1.3 KiB
www.ici.fr/client/immutable/assets/SadSlot.DA8AweTo.css1.4 KiB
www.ici.fr/client/immutable/assets/0.R7fqyza6.css7.7 KiB

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.4 s
URLTime Spent
francebleu.fr/1.3 s
www.francebleu.fr/1.1 s
www.ici.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

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: 150 ms 25.4 KiB
URLTransfer SizeEst Savings
17.1 KiB14.4 KiB
www.ici.fr/client/immutable/assets/Player.DuHeVO9p.css11.0 KiB11.0 KiB

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

Why this matters

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 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 Evaluation3.3 s
Style & Layout1.9 s
Other1.9 s
Rendering509 ms
Script Parsing & Compilation356 ms
Parse HTML & CSS270 ms
Garbage Collection175 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 was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.Not actionable

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
ICI div.wrapper > section#actu > div.logo > img
www.ici.fr/client/immutable/assets/logo-ici-small.DwiLDMIK.svg
ICI, Aller à la page d'accueil div.Header-Logo > a.IciLink > picture > img
www.ici.fr/client/immutable/assets/logo-ici-small.DwiLDMIK.svg

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
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,837 KiB
User Timing marks and measures 3 user timings
Avoid long main-thread tasks 19 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 350 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 510 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
Avoid non-composited animations
93

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

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
Passer la section main.HomePage > section#hp-seo-tags-section > div.title > a.LinkToNextSection

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Passer la publicité div#svelte > div.main-wrapper > div.AdsSlot > a#banniere_haute-before-sad

These items highlight common accessibility best practices.

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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
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
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
No element has a `[tabindex]` value greater than 0
`[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
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
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.
96

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation 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