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.

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:73.939 source:map[column:328006 line:1 type:source-location url:https://www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js urlProvider:network]] map[reflowTime:1.02 source:map[column:328091 line:1 type:source-location url:https://www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js urlProvider:network]] map[reflowTime:28.721 source:map[column:104089 line:10 type:source-location url:https://cdn.trustcommander.net/privacy/1491/privacy_v2_67.js urlProvider:network]] map[reflowTime:0.116 source:map[column:104218 line:10 type:source-location url:https://cdn.trustcommander.net/privacy/1491/privacy_v2_67.js urlProvider:network]] map[reflowTime:0.775 source:map[column:130338 line:10 type:source-location url:https://cdn.trustcommander.net/privacy/1491/privacy_v2_67.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:365.985 label:Time to first byte subpart:timeToFirstByte] map[duration:22.481 label:Resource load delay subpart:resourceLoadDelay] map[duration:80.8500000038147 label:Resource load duration subpart:resourceLoadDuration] map[duration:2070.6259999961853 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Réexpédiez votre courrier en toute simplicité

path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,1,DIV,0,DIV,5,MAIN,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,5,IMG

selector: div.animco > div.animco__wrapper > picture.animco__image > img.lp-picture__full-width

snippet: <img width="300" height="200" alt="Réexpédiez votre courrier en toute simplicité " aria-hidden="true" src="https://www.laposte.fr/ecom/occ/smartedit/medias/sys_master/cms/h31/hed/30…" fetchpriority="high" class="lp-picture__full-width" data-v-314b3fed="">

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

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.7 KiB	453 ms
www.laposte.fr/ecom/_nuxt/css/35fd672.css	47.7 KiB	151 ms
www.laposte.fr/ecom/_nuxt/css/0b3682a.css	542 B
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.6 KiB	453 ms
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.

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: 600 ms 133.8 KiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.3 KiB	78.2 KiB
www.laposte.fr/ecom/_nuxt/css/35fd672.css	47.4 KiB	45.5 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: 6.0 s 1.1 MiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js	553.1 KiB	440.8 KiB
www.laposte.fr/ecom/_nuxt/ace3671.modern.js	192.1 KiB	139.7 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.9 KiB
www.laposte.fr/ecom/_nuxt/ca3c383.modern.js	74.8 KiB	56.5 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	80.0 KiB	45.4 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	36.9 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	34.5 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	28.3 KiB
www.laposte.fr/ecom/_nuxt/1163fe9.modern.js	51.4 KiB	25.8 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
Unattributable	1.7 s	119 ms	0.0 ms
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js	1.5 s	1.1 s	3.5 ms
www.laposte.fr/ecom/_nuxt/f17692a.modern.js	1.1 s	943 ms	0.3 ms
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	942 ms	859 ms	27 ms
www.laposte.fr/	592 ms	33 ms	47 ms
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js	338 ms	55 ms	5.9 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js	283 ms	223 ms	52 ms
cdn.trustcommander.net/privacy/1491/privacy_v2_67.js	202 ms	61 ms	16 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	181 ms	125 ms	53 ms
try.abtasty.com/shared/analytics.6c9b51bdfcbabb565f02.js	139 ms	42 ms	3.1 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_23.js	110 ms	90 ms	19 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_6.js	92 ms	74 ms	16 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js	80 ms	75 ms	4.4 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_27.js	70 ms	43 ms	24 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43.js	55 ms	34 ms	6.6 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.9 s
Other	1.9 s
Style & Layout	737 ms
Script Parsing & Compilation	325 ms
Parse HTML & CSS	179 ms
Garbage Collection	163 ms
Rendering	128 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
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.5 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/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	81.7 KiB
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css	81.6 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	80.2 KiB
www.laposte.fr/ecom/_nuxt/ca3c383.modern.js	75.5 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○User Timing marks and measures

○Avoid large layout shifts

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
Livr. offerte Nouv. Monnaie De Paris Le Seigneur des Anneaux Monnaie de 250€ Or… `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`
`div.animco > div.animco__wrapper > picture.animco__image > img.lp-picture__full-width`
`div.informationBanner__content > a.informationBanner__item > picture.informationBannerItem__image > img.lazyload`

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`
Le Seigneur des Anneaux Monnaie de 250€ Or Le drapeau du Rohan `article#productCard-mp-600513316 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Le Seigneur des Anneaux Monnaie de 10€ Argent La fiole de Galadriel `article#productCard-mp-600513321 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Île de France Monnaie de 10€ Argent hexagonale `article#productCard-mp-600513305 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Occitanie Monnaie de 10€ Argent hexagonale `article#productCard-mp-600513306 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Grand Est Monnaie de 10€ Argent hexagonale `article#productCard-mp-600513307 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Grand Est Monnaie de 5€ Or 1/2g `article#productCard-mp-600513309 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Île de France Monnaie de 500€ Or hexagonale `article#productCard-mp-600512288 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Occitanie Monnaie de 500€ Or hexagonale `article#productCard-mp-600512287 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Collection des régions - Grand Est Monnaie de 500€ Or hexagonale `article#productCard-mp-600512289 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Le Génie Français - Génie de la Liberté Monnaie de 100€ Argent `article#productCard-mp-600511213 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
Le Petit Prince - Le désert Monnaie de 2€ commémorative `article#productCard-mp-600447305 > section.lp-card__medias > div.productCard__medias > a.productCard__imageWrapper`
div.informationBanner > div.informationBanner__container > div.informationBanner__header > a.informationBanner__link `div.informationBanner > div.informationBanner__container > div.informationBanner__header > a.informationBanner__link`
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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chic, un colis plus élégant ! `div.articleCards__container > div.articleCard > div.articleCard__text > h4.articleCard__title`

These are opportunities to improve keyboard navigation in your application.

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

○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

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Les applications La Poste `div.smartBanner > div.smartBanner__media > picture.smartBanner__media__content > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/h7d/h7d/1271429...	64 x 64	72 x 72	96 x 96

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

●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`
`div.animco > div.animco__wrapper > picture.animco__image > img.lp-picture__full-width`
`div.informationBanner__content > a.informationBanner__item > picture.informationBannerItem__image > img.lazyload`

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