Skip to content
https://france.tv

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.

—

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.

RequestCache TTLTransfer Size
utiq.france.tv/utiqLoader.js0.0 ms40.8 KiB
/fedf8125-d890-4ef1-a017-6700106a71f1/loader.js?target=ww...7200.0 s36.9 KiB
tag.aticdn.net/piano-analytics.js14400.0 s26.6 KiB
utiqcontent.com/website/logos/utiq-com.svg0.0 ms1.9 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
www.france.tv/_next/static/media/FranceTVBrown-Regular.186s_hwolcixm.woff235 ms
www.france.tv/_next/static/media/FranceTVBrown-Bold.171e8j_kmufpu.woff220 ms

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.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP div.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP
/ph1tOq_02-YWpzf4XS9KHgJ9LLM/970x0/filters:quality(85):fo...152.4 KiB113.6 KiB
div.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP div.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP
/C5zllAISJYRDsvWmaZGJAZTbsTo/970x0/filters:quality(85):fo...112.1 KiB73.2 KiB
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img
/pxSMUc_FseiuROtvTTOcx8UobEY/400x0/filters:quality(85):fo...58.6 KiB23.9 KiB
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img
/P3Dy6bcxEthiLZhSG8C9cQlO0O8/400x0/filters:quality(85):fo...21.1 KiB6.8 KiB
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img
/64gWEKoSvwmGvklBA3sJCPv2X8I/400x0/filters:quality(85):fo...19.7 KiB5.0 KiB
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img
/_eDeDcjVsi-HQOpL39ZKKE6KIEQ/400x0/filters:quality(85):fo...19.1 KiB4.5 KiB

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.

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

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

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.

URLTotal CPU TimeScript EvaluationScript Parse
www.france.tv/3.6 s154 ms143 ms
www.france.tv/_next/static/chunks/0-kkveyz.tao8.js1.9 s1.5 s38 ms
Unattributable1.5 s352 ms0.0 ms
www.france.tv/_next/static/chunks/0j15lq9f6jk8_.js619 ms617 ms1.7 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....470 ms404 ms64 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...402 ms223 ms45 ms
utiq.france.tv/utiqLoader.js355 ms268 ms23 ms
www.france.tv/_next/static/chunks/02d395-i3s0zg.js151 ms7.0 ms22 ms
tag.aticdn.net/piano-analytics.js97 ms81 ms14 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 Evaluation3.8 s
Other1.9 s
Style & Layout1.9 s
Rendering651 ms
Script Parsing & Compilation528 ms
Parse HTML & CSS452 ms
Garbage Collection173 ms

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
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 1,821 KiB
●User Timing marks and measures 3 user timings
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 20 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP breakdown
○LCP request discovery
○Avoid non-composited animations
84

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chaînes div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Directs div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Catégories div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
France Info div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Jeunesse div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Services div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Contact div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
134 partenaires div.didomi-popup-notice-text > div > p > span

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Progression en cours : 94% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 78% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 82% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 99% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 97% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 42% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 86% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 80% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 65% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 28% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 28% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 84% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 80% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 63% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO

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
header.euRjEA > nav.bnyIZY > div > a.bEfsqy header.euRjEA > nav.bnyIZY > div > a.bEfsqy

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●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
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
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
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