Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

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:67.316 source:map[type:text value:[unattributed]]]]

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.

	URL	Resource Size	Est Savings
HEADER_M_colissimo_part_290224.jpg `div.hero > div.hero__banner > picture.hero__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/h07/hee/2700925...	200.3 KiB	168.1 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	81.6 KiB	452 ms
www.laposte.fr/ecom/_nuxt/css/35fd672.css	47.7 KiB	151 ms
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.6 KiB	452 ms
www.laposte.fr/ecom/_nuxt/css/0b3682a.css	544 B
www.laposte.fr/ecom/_nuxt/css/f3af2ce.css	2.4 KiB
www.laposte.fr/ecom/_nuxt/css/86e357d.css	2.6 KiB
www.laposte.fr/ecom/_nuxt/css/f3bbfb3.css	4.4 KiB	151 ms
www.laposte.fr/ecom/_nuxt/css/da75bd6.css	10.4 KiB

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.

Request	Cache TTL	Transfer Size
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js	30.0 s	11.2 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43.js	21600.0 s	2.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s

URL	Time Spent
www.colissimo.fr/	829 ms
laposte.fr/colissimo	850 ms
www.laposte.fr/colissimo	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

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

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: 750 ms 135.0 KiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.3 KiB	78.9 KiB
www.laposte.fr/ecom/_nuxt/css/35fd672.css	47.4 KiB	46.1 KiB
www.laposte.fr/ecom/_nuxt/css/da75bd6.css	10.1 KiB	10.1 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.

Estimated savings: 5.4 s 1.1 MiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js	553.1 KiB	447.2 KiB
www.laposte.fr/ecom/_nuxt/ace3671.modern.js	192.1 KiB	146.9 KiB
www.laposte.fr/ecom/_nuxt/9aeea0a.modern.js	127.2 KiB	127.1 KiB
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js	163.8 KiB	86.4 KiB
www.laposte.fr/ecom/_nuxt/ca3c383.modern.js	74.8 KiB	56.4 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	80.0 KiB	46.1 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js	104.6 KiB	40.3 KiB
www.laposte.fr/ecom/_nuxt/5130bf2.modern.js	89.7 KiB	37.6 KiB
www.laposte.fr/ecom/_nuxt/678a774.modern.js	47.7 KiB	36.0 KiB
www.laposte.fr/ecom/_nuxt/dc72e0b.modern.js	48.8 KiB	35.0 KiB
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	81.3 KiB	29.1 KiB
www.laposte.fr/ecom/_nuxt/ebc0c65.modern.js	46.4 KiB	27.7 KiB
www.laposte.fr/ecom/_nuxt/1163fe9.modern.js	51.4 KiB	25.7 KiB
www.laposte.fr/ecom/_nuxt/2593fae.modern.js	28.5 KiB	23.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.laposte.fr/ecom/_nuxt/f17692a.modern.js	1.7 s	1.5 s	0.2 ms
www.laposte.fr/colissimo	1.2 s	24 ms	40 ms
Unattributable	1.1 s	89 ms	0.0 ms
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js	848 ms	817 ms	2.2 ms
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	321 ms	255 ms	28 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js	209 ms	163 ms	38 ms
cdn.trustcommander.net/privacy/1491/privacy_v2_67.js	166 ms	52 ms	25 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	148 ms	106 ms	40 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_6.js	136 ms	70 ms	25 ms
try.abtasty.com/shared/analytics.6c9b51bdfcbabb565f02.js	112 ms	32 ms	3.0 ms
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js	100 ms	34 ms	4.6 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_23.js	85 ms	67 ms	18 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_27.js	79 ms	51 ms	25 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js	63 ms	59 ms	4.0 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_25.js	53 ms	31 ms	17 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.

Category	Time Spent
Script Evaluation	3.4 s
Other	1.3 s
Style & Layout	812 ms
Script Parsing & Compilation	297 ms
Parse HTML & CSS	278 ms
Rendering	169 ms
Garbage Collection	99 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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js	554.0 KiB
/ecom/occ/smartedit/medias/sys_master/cms/h07/hee/2700925...	199.6 KiB
www.laposte.fr/ecom/_nuxt/ace3671.modern.js	192.9 KiB
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js	164.6 KiB
www.laposte.fr/ecom/_nuxt/9aeea0a.modern.js	127.6 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js	105.1 KiB
www.laposte.fr/ecom/_nuxt/5130bf2.modern.js	90.0 KiB
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.6 KiB
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	81.6 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	80.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
solutions d'envoi Colissimo adaptées `div.row > div.row__left > picture > img.lazyload`
déposez votre colis `div.row > div.row__right > picture > img.lazyload`
envoyer colis dans DOM ou international `div.row > div.row__left > picture > img.lazyload`
démarche RSE dans les transports `div.row > div.row__right > picture > img.lazyload`
expérience de livraison optimisée `div.row > div.row__left > picture > img.lazyload`
Fabriqué en France `div.productCard__medias > div.productCard__icons > div.productStickers > img`	www.laposte.fr/ecom/_nuxt/img/madeInFrance.ca522eb.svg
Fabriqué en France `div.productCard__medias > div.productCard__icons > div.productStickers > img`	www.laposte.fr/ecom/_nuxt/img/madeInFrance.ca522eb.svg
Fabriqué en France `div.productCard__medias > div.productCard__icons > div.productStickers > img`	www.laposte.fr/ecom/_nuxt/img/madeInFrance.ca522eb.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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 40 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 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Enveloppebulle Lot de 5 cartons adaptables varia x-pack 3 format 305x235x105 mm… `div.productCarousel > div.carousel > div.carousel__wrapper > div.carousel__container`
Enveloppebulle Lot de 10 planches a4 avec étiquette colissimo intégrée 164 x 12… `div.productCarousel > div.carousel > div.carousel__wrapper > div.carousel__container`

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
Retour à l'accueil - La Poste `header.header > div.header__base > div.headerFull__logo > picture.logo`

When an 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 make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header > div.header__base > div.headerFull__actions > span.headerFull__button `header.header > div.header__base > div.headerFull__actions > span.headerFull__button`
header.header > div.header__base > div.headerFull__actions > span#header-cart-button `header.header > div.header__base > div.headerFull__actions > span#header-cart-button`

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
Retour en haut `div.row > div.footer__bottom-content > div.footer__bottom-lower > i.back`

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close consent banner `body > div#tc-privacy-wrapper > div#popin_tc_privacy > button#popin_tc_privacy_btn_close`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#popin_tc_privacy_container_text > div#popin_tc_privacy_text > div#tc_test > img#tc_banner_logo `div#popin_tc_privacy_container_text > div#popin_tc_privacy_text > div#tc_test > img#tc_banner_logo`

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.header > div.header__base > div.headerFull__actions > a#header-help-part `header.header > div.header__base > div.headerFull__actions > a#header-help-part`
Lot de 5 cartons adaptables varia x-pack 3 format 305x235x105 mm `article#productCard-mp-500025506 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 25 Boîtes postales brunes 150x150x60 mm `article#productCard-mp-500027220 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Carton d'emballage 20 x 15 x 11 cm `article#productCard-mp-500079535 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 5 cartons d'emballage 31 x 21 x 7,5 cm `article#productCard-mp-500079541 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 10 Boîtes Pochettes Carton XS - hauteur 3cm - format 140x225 mm `article#productCard-mp-500026244 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 10 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500117208 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 50 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500117149 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 250 planches d’étiquette colissimo 150 x 100 mm `article#productCard-mp-600039944 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 500 planches a4 de 2 étiquettes compatibles colissimo à bords vifs 210 x… `article#productCard-mp-500574875 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 500 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500025260 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 100 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500117185 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 250 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500127635 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 1000 planches d’étiquette colissimo 150 x 100 mm `article#productCard-mp-600039945 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 3000 feuilles A4 avec étiquette autocollante Colissimo intégrée 150 x 10… `article#productCard-mp-500545383 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Lot de 1000 planches a4 avec étiquette colissimo intégrée 164 x 120 mm `article#productCard-mp-500025255 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Étiquette d’expédition spéciale e-commerce avery colissimo `article#productCard-mp-500042842 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
div.component > div.row > div.app > a.app__link `div.component > div.row > div.app > a.app__link`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Personnaliser `div#tc-privacy-wrapper > div#popin_tc_privacy > div#popin_tc_privacy_container_button > button#popin_tc_privacy_button`
Ne pas accepter et fermer `div#tc-privacy-wrapper > div#popin_tc_privacy > div#popin_tc_privacy_container_button > button#popin_tc_privacy_button_2`
Accepter et fermer `div#tc-privacy-wrapper > div#popin_tc_privacy > div#popin_tc_privacy_container_button > button#popin_tc_privacy_button_3`

○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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Description
`A bad HTTP response code (403) was received when fetching the script.`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js
www.laposte.fr/ecom/_nuxt/ace3671.modern.js

●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 issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#popin_tc_privacy_container_text > div#popin_tc_privacy_text > div#tc_test > img#tc_banner_logo `div#popin_tc_privacy_container_text > div#popin_tc_privacy_text > div#tc_test > img#tc_banner_logo`

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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid