Netherlands · Amsterdam Completed: Apr 22, 2026 20:48 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 78 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
74 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/5921cbbb-0a16-4fbc-8d40-5c408e0ad444)<a href="https://beavercheck.com/results/5921cbbb-0a16-4fbc-8d40-5c408e0ad444"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffrance.tv" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ffrance.tvThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 1 performance issue below shapes how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.
3 barrier(s) likely increasing bounce by ~5%.
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€340 investment → €0.41/month returns + EUR 120,500,000 risk avoided
€340
4h · 5 findings
€0.41 /mo
~€4.97 / year
EUR 120,500,000
if kept compliant
€170 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
4.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,667 / month at risk
~€120,500,005 / year if left unfixed
€120,500,000
+6 more
€0.41 /mo
5594.8 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
3.64 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
0 ms
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.020
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.06 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.
0 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| utiq.france.tv/utiqLoader.js | 0.0 ms | 40.8 KiB |
| /fedf8125-d890-4ef1-a017-6700106a71f1/loader.js?target=ww... | 7200.0 s | 36.9 KiB |
| tag.aticdn.net/piano-analytics.js | 14400.0 s | 26.6 KiB |
| utiqcontent.com/website/logos/utiq-com.svg | 0.0 ms | 1.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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est 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 KiB | 113.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 KiB | 73.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 KiB | 23.9 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /P3Dy6bcxEthiLZhSG8C9cQlO0O8/400x0/filters:quality(85):fo... | 21.1 KiB | 6.8 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /64gWEKoSvwmGvklBA3sJCPv2X8I/400x0/filters:quality(85):fo... | 19.7 KiB | 5.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 KiB | 4.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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
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.
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.
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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| www.france.tv/ | 3.6 s | 154 ms | 143 ms |
| www.france.tv/_next/static/chunks/0-kkveyz.tao8.js | 1.9 s | 1.5 s | 38 ms |
| Unattributable | 1.5 s | 352 ms | 0.0 ms |
| www.france.tv/_next/static/chunks/0j15lq9f6jk8_.js | 619 ms | 617 ms | 1.7 ms |
| /sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk.... | 470 ms | 404 ms | 64 ms |
| /sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w... | 402 ms | 223 ms | 45 ms |
| utiq.france.tv/utiqLoader.js | 355 ms | 268 ms | 23 ms |
| www.france.tv/_next/static/chunks/02d395-i3s0zg.js | 151 ms | 7.0 ms | 22 ms |
| tag.aticdn.net/piano-analytics.js | 97 ms | 81 ms | 14 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.8 s |
| Other | 1.9 s |
| Style & Layout | 1.9 s |
| Rendering | 651 ms |
| Script Parsing & Compilation | 528 ms |
| Parse HTML & CSS | 452 ms |
| Garbage Collection | 173 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
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.
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.
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.
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.
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.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
790 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
0 ms
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.013
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.43 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.
0 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| utiq.france.tv/utiqLoader.js | 0.0 ms | 40.8 KiB |
| /fedf8125-d890-4ef1-a017-6700106a71f1/loader.js?target=ww... | 7200.0 s | 36.0 KiB |
| tag.aticdn.net/piano-analytics.js | 14400.0 s | 26.6 KiB |
| utiqcontent.com/website/logos/utiq-com.svg | 0.0 ms | 1.9 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP div.jTWvec > div.hWgZTB > picture.jhVjVz > img.dcuyOP | /Me_D9WvO1DeHQmZRJt1pbxT_4Pw/1350x0/filters:quality(85):f... | 291.8 KiB | 228.3 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /3F2SvBELA75SppKlfIaJOD1yOas/279x0/filters:quality(85):fo... | 36.9 KiB | 28.4 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /OMK8u0jStNrDVISrg1BcWL5h-j8/240x0/filters:quality(85):fo... | 25.0 KiB | 12.5 KiB |
Tournoi des Six Nations féminin li > a.fIgGMm > span > img | www.france.tv/logos/events/tournoi-des-six-nations-feminin.png | 10.6 KiB | 9.5 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /36YbgYjZSJ3lTxSkarTJa_03qM0/279x0/filters:quality(85):fo... | 24.1 KiB | 7.7 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /8NLg1IHRScrGqgdnZh6rJPxVbm0/240x0/filters:quality(85):fo... | 19.7 KiB | 7.2 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /qV3AXCQvDIownz-xtaG6Bx1g1eM/240x0/filters:quality(85):fo... | 19.3 KiB | 6.8 KiB |
logo france-tv div.didomi-popup-container > div.didomi-popup-view > div.didomi-popup-notice-logo-container > img.didomi-popup-notice-logo | www.france.tv/cmp/logo-france-tv-black.png | 7.6 KiB | 6.4 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /AYHjt8AHEPALxtDZBq6IZ5Y7ryg/240x0/filters:quality(85):fo... | 11.5 KiB | 6.2 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /5MQzB4EACTAn8GRzrrcrvV69a80/240x0/filters:quality(85):fo... | 17.9 KiB | 5.4 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /rakZ7rW04nHnNKRYydqAfdLDXmQ/240x0/filters:quality(85):fo... | 17.5 KiB | 5.0 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /bYz262edsgJ-XMGrU4ei0luTvG8/240x0/filters:quality(85):fo... | 17.0 KiB | 4.7 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /E52Dy-5hnTB69M8vnEa6THRkTxI/240x0/filters:quality(85):fo... | 17.2 KiB | 4.7 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /PGA_9podxlQacVdQheWpaTAHXDI/240x0/filters:quality(85):fo... | 9.4 KiB | 4.1 KiB |
span.iAGuGS > span.cHvGDh > span.krIypG > img span.iAGuGS > span.cHvGDh > span.krIypG > img | /hYCut7WcB1gt3Sq622diupVuKcY/240x0/filters:quality(85):fo... | 16.3 KiB | 4.1 KiB |
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
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.
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.
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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 991 ms |
| Other | 527 ms |
| Style & Layout | 498 ms |
| Rendering | 173 ms |
| Script Parsing & Compilation | 136 ms |
| Parse HTML & CSS | 113 ms |
| Garbage Collection | 43 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
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.
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.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
Tournoi des Six Nations féminin nav.bnyIZY > div.ddgODW > a > img | www.france.tv/logos/events/tournoi-des-six-nations-feminin.png | 180 x 20 (9.00) | 348 x 80 (4.35) |
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.
Send Feedback