C — https://www.impots.gouv.fr

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

'unsafe-eval' found in script source

Security › Content Security Policy

'unsafe-inline' found in script source

Security › Content Security Policy

1 image-only link(s) without alt text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.impots.gouv.fr)](https://beavercheck.com/results/8b0be322-0691-9e75-3529-f7026a7f5e76)

HTML

<a href="https://beavercheck.com/results/8b0be322-0691-9e75-3529-f7026a7f5e76"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.impots.gouv.fr" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.impots.gouv.fr

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

100

Best Practices

SEO

Core Web Vitals

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.27 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.95 s

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

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

3.96 s

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.

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

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

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

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

	URL	Resource Size	Est Savings
Qui mieux que vous pour réussir le concours des Finances publiques ? `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	www.impots.gouv.fr/sites/default/files/banner/concours_c.jpg	153.9 KiB	116.4 KiB
div.lecteur > div.pseudo-lecteur-video > a > img.btn-play `div.lecteur > div.pseudo-lecteur-video > a > img.btn-play`	/www2/code_cabcom/css/pseudo_lecteur_video/lecteur_video_...	31.3 KiB	30.5 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/label_...	63.1 KiB	25.6 KiB
div.contenu > div.lecteur > div.pseudo-lecteur-video > img `div.contenu > div.lecteur > div.pseudo-lecteur-video > img`	/sites/default/files/media/cabcom/images/_banniere/factur...	53.9 KiB	24.1 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/gestpa...	44.2 KiB	6.7 KiB
div.fr-card--fr-card > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--fr-card > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/2_actu/_images/simulateur_ir_2...	21.3 KiB	5.6 KiB

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

lhId: page-3-IMG

nodeLabel: div.contenu > div.lecteur > div.pseudo-lecteur-video > img

path: 1,HTML,1,BODY,1,DIV,0,DIV,2,MAIN,1,DIV,0,DIV,0,DIV,1,ARTICLE,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,3,DIV,0,IMG

selector: div.contenu > div.lecteur > div.pseudo-lecteur-video > img

snippet: <img alt="" src="/sites/default/files/media/cabcom/images/_banniere/facturation_electroniqu…" aria-hidden="true">

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.

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.

URL	Transfer Size	Duration
/sites/default/files/css/css_uJEoZcHWZvlXb4bIm22-kteWi7nd...	173.6 KiB	900 ms
/sites/default/files/js/js_UqDPpfAcYkt3Vj9otY9f5FuhDZgAay...	38.5 KiB
/sites/default/files/css/css_kR14Tq1JNJR43ip1cB2YJVRJy_fK...	6.8 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 1.3 s

URL	Time Spent
www.impots.gouv.fr/	1.3 s
www.impots.gouv.fr/accueil	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.

TTI

Diagnostics

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

Estimated savings: 150 ms 10.2 KiB

URL	Transfer Size	Est Savings
www.impots.gouv.fr/libraries/dsfr/dist/dsfr.module.js?td4kq3	45.7 KiB	10.2 KiB

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.

Estimated savings: 900 ms 156.5 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_uJEoZcHWZvlXb4bIm22-kteWi7nd...	172.9 KiB	156.5 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.

Estimated savings: 150 ms 69.1 KiB

URL	Transfer Size	Est Savings
/sites/default/files/js/js_YE3ZZj9pyOEL8oVHi4MzlDLWceT05W...	30.6 KiB	25.0 KiB
www.impots.gouv.fr/libraries/dsfr/dist/dsfr.module.js?td4kq3	45.7 KiB	22.9 KiB
/sites/default/files/js/js_EedQbQLNY6jc1Mye-z0lP8m3cFVGsW...	37.8 KiB	21.3 KiB

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

Category	Time Spent
Other	789 ms
Style & Layout	597 ms
Script Evaluation	362 ms
Rendering	276 ms
Parse HTML & CSS	110 ms
Script Parsing & Compilation	41 ms

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

	URL
div.contenu > div.lecteur > div.pseudo-lecteur-video > img `div.contenu > div.lecteur > div.pseudo-lecteur-video > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div#banniere-pro-fe-logigramme > div.contenu > div.logo > img `div#banniere-pro-fe-logigramme > div.contenu > div.logo > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div.fr-col-lg-12 > div.texte > p.fe-num-tel > img `div.fr-col-lg-12 > div.texte > p.fe-num-tel > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div.lecteur > div.pseudo-lecteur-video > a > img.btn-play `div.lecteur > div.pseudo-lecteur-video > a > img.btn-play`	/www2/code_cabcom/css/pseudo_lecteur_video/lecteur_video_...

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Avoids enormous network payloads Total size was 1,090 KiB

●JavaScript execution time 0.3 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 210 ms

●Server Backend Latencies 570 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

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.

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.

Failing Elements
Tout savoir sur la facturation électronique (vidéo) `div.contenu > div.lecteur > div.pseudo-lecteur-video > a`

○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

●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

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

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

○Identical links have the same purpose.

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

100

Best Practices

SEO

Core Web Vitals

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.

1.09 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.21 s

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

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

1.21 s

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.

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

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

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

	URL	Resource Size	Est Savings
Qui mieux que vous pour réussir le concours des Finances publiques ? `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	www.impots.gouv.fr/sites/default/files/banner/concours_c.jpg	153.9 KiB	140.5 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/label_...	63.1 KiB	49.9 KiB
div.contenu > div.lecteur > div.pseudo-lecteur-video > img `div.contenu > div.lecteur > div.pseudo-lecteur-video > img`	/sites/default/files/media/cabcom/images/_banniere/factur...	53.9 KiB	43.1 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/gestpa...	44.2 KiB	31.0 KiB
div.lecteur > div.pseudo-lecteur-video > a > img.btn-play `div.lecteur > div.pseudo-lecteur-video > a > img.btn-play`	/www2/code_cabcom/css/pseudo_lecteur_video/lecteur_video_...	31.3 KiB	30.2 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/gmbi/g...	27.5 KiB	17.8 KiB
div.fr-card--fr-card > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--fr-card > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/2_actu/_images/simulateur_ir_2...	21.3 KiB	5.6 KiB
div#banniere-pro-fe-logigramme > div.contenu > div.logo > img `div#banniere-pro-fe-logigramme > div.contenu > div.logo > img`	/sites/default/files/media/cabcom/images/_banniere/factur...	7.4 KiB	5.2 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/sp_plu...	7.7 KiB	5.0 KiB
div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img `div.fr-card--vertical > div.fr-card__header > div.fr-card__img > img.fr-responsive-img`	/sites/default/files/media/cabcom/images/_banniere/entrep...	7.2 KiB	4.6 KiB

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

lhId: page-2-IMG

nodeLabel: div.contenu > div.lecteur > div.pseudo-lecteur-video > img

path: 1,HTML,1,BODY,1,DIV,0,DIV,2,MAIN,1,DIV,0,DIV,0,DIV,1,ARTICLE,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,3,DIV,0,IMG

selector: div.contenu > div.lecteur > div.pseudo-lecteur-video > img

snippet: <img alt="" src="/sites/default/files/media/cabcom/images/_banniere/facturation_electroniqu…" aria-hidden="true">

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.

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.

URL	Transfer Size	Duration
/sites/default/files/css/css_uJEoZcHWZvlXb4bIm22-kteWi7nd...	173.6 KiB	160 ms
/sites/default/files/js/js_UqDPpfAcYkt3Vj9otY9f5FuhDZgAay...	38.5 KiB
/sites/default/files/css/css_kR14Tq1JNJR43ip1cB2YJVRJy_fK...	6.8 KiB

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

Diagnostics

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

Estimated savings: 0.0 ms 10.2 KiB

URL	Transfer Size	Est Savings
www.impots.gouv.fr/libraries/dsfr/dist/dsfr.module.js?td4kq3	45.7 KiB	10.2 KiB

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.

Estimated savings: 120 ms 155.5 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_uJEoZcHWZvlXb4bIm22-kteWi7nd...	172.9 KiB	155.5 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.

Estimated savings: 0.0 ms 69.1 KiB

URL	Transfer Size	Est Savings
/sites/default/files/js/js_YE3ZZj9pyOEL8oVHi4MzlDLWceT05W...	30.6 KiB	25.0 KiB
www.impots.gouv.fr/libraries/dsfr/dist/dsfr.module.js?td4kq3	45.7 KiB	22.8 KiB
/sites/default/files/js/js_EedQbQLNY6jc1Mye-z0lP8m3cFVGsW...	37.8 KiB	21.3 KiB

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

	URL
div.contenu > div.lecteur > div.pseudo-lecteur-video > img `div.contenu > div.lecteur > div.pseudo-lecteur-video > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div#banniere-pro-fe-logigramme > div.contenu > div.logo > img `div#banniere-pro-fe-logigramme > div.contenu > div.logo > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div.fr-col-lg-12 > div.texte > p.fe-num-tel > img `div.fr-col-lg-12 > div.texte > p.fe-num-tel > img`	/sites/default/files/media/cabcom/images/_banniere/factur...
div.lecteur > div.pseudo-lecteur-video > a > img.btn-play `div.lecteur > div.pseudo-lecteur-video > a > img.btn-play`	/www2/code_cabcom/css/pseudo_lecteur_video/lecteur_video_...

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 725 ms

URL	Time Spent
www.impots.gouv.fr/	725 ms
www.impots.gouv.fr/accueil	0.0 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.2 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Avoids enormous network payloads Total size was 1,093 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.5 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 210 ms

●Server Backend Latencies 860 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

100

Accessibility

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.

Failing Elements
Tout savoir sur la facturation électronique (vidéo) `div.contenu > div.lecteur > div.pseudo-lecteur-video > a`

○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

●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

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

●Form elements have associated labels

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Identical links have the same purpose.

○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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

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

Browse & Analyze

Learn

Results for https://www.impots.gouv.fr

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts