Lighthouse Desktop

· 0 checks — Desktop 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.

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
div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width `div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/hb6/hf4/1353398...	347.6 KiB	346.3 KiB
`div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/ha2/h74/1188966...	176.6 KiB	174.8 KiB
`div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/h7d/h6a/1188966...	172.7 KiB	171.1 KiB
`div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/h73/h0e/1188966...	97.8 KiB	96.0 KiB
`div.serviceRow__tiles > a.serviceTile > picture.serviceTile__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/h99/h18/1188966...	70.7 KiB	68.8 KiB
`div.animco > div.animco__wrapper > picture.animco__image > img.lp-picture__full-width`	/ecom/occ/smartedit/medias/sys_master/cms/hf6/h4f/3095556...	34.5 KiB	27.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.7 KiB	82 ms
www.laposte.fr/ecom/_nuxt/ActualiteCard.CmTTAxUI.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/ArticleCard.CTV14oi8.css	8.3 KiB
www.laposte.fr/ecom/_nuxt/InformationBannerItem.N1qPPLtz.css	8.3 KiB
www.laposte.fr/ecom/_nuxt/Control.BiPFbY2Y.css	7.7 KiB
www.laposte.fr/ecom/_nuxt/Calculator.B5quL4xR.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/Faq.DBGhYkPg.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/EnCeMomentALaPoste.B0sY4-ty.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/ArticleCards.BIUnBHma.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/InformationBanner.BcHQcV4-.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/SuiviEnvoi.Bikma-GE.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/Spacing.CCSch5dQ.css	7.7 KiB
www.laposte.fr/ecom/_nuxt/SmartBanner.DlSfz-7-.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/FooterBottom.CxJI1ZCX.css	9.0 KiB
www.laposte.fr/ecom/_nuxt/FooterHeadingsList.EbNlufEp.css	15.4 KiB
www.laposte.fr/ecom/_nuxt/FooterSocial.CAmqbYB1.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/ServiceRow.lsFagR6y.css	8.4 KiB
www.laposte.fr/ecom/_nuxt/FooterAppLink.CSQD42fJ.css	7.8 KiB
www.laposte.fr/ecom/_nuxt/FooterApps.CJbIhS9q.css	8.0 KiB
www.laposte.fr/ecom/_nuxt/FooterEngagement.B7cVu5Zc.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/HtmlRenderer.DnINTCJp.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/entry.C0t7vErM.css	722.4 KiB	616 ms
www.laposte.fr/ecom/_nuxt/ServiceTile.CWzOZcbb.css	8.3 KiB
www.laposte.fr/ecom/_nuxt/Animco.BLMlXN3k.css	9.0 KiB
www.laposte.fr/ecom/_nuxt/Row.CmtUyaqT.css	15.2 KiB
www.laposte.fr/ecom/_nuxt/DirectLinks.CpSQ5g-n.css	15.2 KiB
www.laposte.fr/ecom/_nuxt/MenuPanel.C2pxmLFJ.css	9.4 KiB
www.laposte.fr/ecom/_nuxt/MainMenu.Bi6DnkrV.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/QuickAccess.BivUaHUQ.css	7.9 KiB
www.laposte.fr/ecom/_nuxt/QuickAccess.VE8J6xaQ.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/HeaderQuick.CAzXDMwO.css	8.3 KiB
www.laposte.fr/ecom/_nuxt/Chip.BbDjxImb.css	8.3 KiB
www.laposte.fr/ecom/_nuxt/SearchboxProductPrice.D3c7m-Nz.css	7.9 KiB
www.laposte.fr/ecom/_nuxt/SearchboxProduct.D4NZ59Qa.css	8.0 KiB
www.laposte.fr/ecom/_nuxt/SearchboxDropdown.BKCxKm8i.css	8.7 KiB
www.laposte.fr/ecom/_nuxt/SearchboxInput.C_yZk6zj.css	8.5 KiB
www.laposte.fr/ecom/_nuxt/Searchbox.DXAgY0pC.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/PanelHeader.8GiC9i71.css	30.3 KiB
www.laposte.fr/ecom/_nuxt/Navbar.WzFhc5u4.css	8.1 KiB
www.laposte.fr/ecom/_nuxt/AccountSidePanel.BHVLvQ7A.css	8.5 KiB
www.laposte.fr/ecom/_nuxt/AccessLinks.DHaiYpdn.css	8.4 KiB
www.laposte.fr/ecom/_nuxt/AccessLinksBlock.Hk5KTflr.css	8.2 KiB
www.laposte.fr/ecom/_nuxt/index.BRfEChR5.css	24.2 KiB
www.laposte.fr/ecom/_nuxt/HeaderFull.B-TvWNb0.css	15.3 KiB
www.laposte.fr/ecom/_nuxt/HeaderLight.B03CoPsn.css	7.7 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.

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.

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

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: 700 ms 831.3 KiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/entry.C0t7vErM.css	722.0 KiB	719.1 KiB
www.laposte.fr/ecom/_nuxt/PanelHeader.8GiC9i71.css	29.9 KiB	29.9 KiB
www.laposte.fr/ecom/_nuxt/index.BRfEChR5.css	23.8 KiB	23.0 KiB
www.laposte.fr/ecom/_nuxt/FooterHeadingsList.EbNlufEp.css	15.0 KiB	15.0 KiB
www.laposte.fr/ecom/_nuxt/Row.CmtUyaqT.css	14.8 KiB	14.8 KiB
www.laposte.fr/ecom/_nuxt/HeaderFull.B-TvWNb0.css	14.9 KiB	14.7 KiB
www.laposte.fr/ecom/_nuxt/DirectLinks.CpSQ5g-n.css	14.8 KiB	14.6 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: 250 ms 510.3 KiB

URL	Transfer Size	Est Savings
www.laposte.fr/ecom/_nuxt/C6m16DWd.js	505.9 KiB	279.4 KiB
www.laposte.fr/poc-av/chatbot/main.CmxAWFs4.js	132.6 KiB	116.5 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js	80.0 KiB	45.3 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js	104.6 KiB	40.3 KiB
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js	81.3 KiB	28.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	1.2 s
Script Evaluation	1.0 s
Style & Layout	430 ms
Parse HTML & CSS	265 ms
Script Parsing & Compilation	78 ms
Rendering	50 ms
Garbage Collection	31 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/entry.C0t7vErM.css	722.4 KiB
www.laposte.fr/ecom/_nuxt/C6m16DWd.js	508.2 KiB
www.laposte.fr/ecom/_nuxt/app_ng.-RgnTR19.png	361.2 KiB
/ecom/occ/smartedit/medias/sys_master/cms/hb6/hf4/1353398...	347.3 KiB
www.laposte.fr/ecom/_nuxt/CFs_9UKw.js	249.3 KiB
www.laposte.fr/ecom/_nuxt/Pdp.Bpj6SN7p.css	184.8 KiB
/ecom/occ/smartedit/medias/sys_master/cms/ha2/h74/1188966...	175.9 KiB
/ecom/occ/smartedit/medias/sys_master/cms/h7d/h6a/1188966...	172.1 KiB
www.laposte.fr/ecom/_nuxt/logo.CtPYZDkO.jpeg	172.1 KiB
www.laposte.fr/poc-av/chatbot/main.CmxAWFs4.js	133.0 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

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 8 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 150 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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

Accessibility

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

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Timbre `div.calculatorControl > div.dropdown__wrapper > fieldset.dropdown > div.dropdown__element`
Lettre verte (J+3) `div.calculatorControl > div.dropdown__wrapper > fieldset.dropdown > div.dropdown__element`
Unité `div.calculatorControl > div.dropdown__wrapper > fieldset.dropdown > div.dropdown__element`

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
Livraison offerte Nouveauté Monnaie De Paris Le Seigneur des Anneaux Monnaie de… `div.productCarousel > div.carousel > div.carousel__wrapper > div.carousel__container`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Le courrier `div.component > nav > ul.mainMenu > li.mainMenu__item`
Le colis `div.component > nav > ul.mainMenu > li.mainMenu__item`
Le transfert de courrier `div.component > nav > ul.mainMenu > li.mainMenu__item`
Les services `div.component > nav > ul.mainMenu > li.mainMenu__item`
Tous nos produits `div.component > nav > ul.mainMenu > li.mainMenu__item`

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

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Le courrier Le colis Le transfert de courrier Les services Tous nos produits Vé… `div.navbar__body > div.component > nav > ul.mainMenu`

These are opportunities to improve the experience of reading tabular or list data using 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`
N° de suivi, rechercher un produit ou un service .... `div.searchbox > div.searchbox__wrapper > div.searchbox__head > button.searchbox__entry`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

○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

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
/usr/src/assets/images/nav/nav-part-courrier.svg	Allowed
/usr/src/assets/images/nav/nav-part-colis.svg	Allowed
/usr/src/assets/images/nav/nav-part-demenagement.svg	Allowed
/usr/src/assets/images/nav/nav-part-services.svg	Allowed
/usr/src/assets/images/nav/nav-part-tous-les-produits.svg	Allowed

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.

Source	Description
www.laposte.fr/	`Not allowed to load local resource: file:///usr/src/assets/images/nav/nav-part-colis.svg`
www.laposte.fr/	`Not allowed to load local resource: file:///usr/src/assets/images/nav/nav-part-courrier.svg`
www.laposte.fr/	`Not allowed to load local resource: file:///usr/src/assets/images/nav/nav-part-demenagement.svg`
www.laposte.fr/	`Not allowed to load local resource: file:///usr/src/assets/images/nav/nav-part-services.svg`
www.laposte.fr/	`Not allowed to load local resource: file:///usr/src/assets/images/nav/nav-part-tous-les-produits.svg`

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/C6m16DWd.js

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
La Poste, aller à l'accueil `div.footer__bottom-content > div.footer__bottom-lower > div.footer__bottom-logo > a.logo__wrapper`

To appear in search results, crawlers need access to your app.

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid