Skip to content
Audit Complete

Results for https://www.laposte.fr

Visit site
Singapore Singapore · Singapore Completed: Apr 7, 2026 20:42 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 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)

1

HSTS header is missing

Security › Security Headers
2

No <main> landmark found

Accessibility › Landmark Structure
3

No favicon or icon links detected

Accessibility › Favicon & Branding
4

110 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
5

Cookie 'lb-cookie' has no SameSite attribute

Security › Cookie Security
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.laposte.fr)](https://beavercheck.com/results/6039f86b-0a0b-27be-7a12-9ea420b2e8d0)
<a href="https://beavercheck.com/results/6039f86b-0a0b-27be-7a12-9ea420b2e8d0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.laposte.fr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.laposte.fr

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

29
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
71
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

12.37 s

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

19.38 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.61 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

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

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

19.39 s

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

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.

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.

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.

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.

URLTransfer SizeDuration
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js81.7 KiB453 ms
www.laposte.fr/ecom/_nuxt/css/35fd672.css47.7 KiB151 ms
www.laposte.fr/ecom/_nuxt/css/0b3682a.css542 B
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css81.6 KiB453 ms
www.laposte.fr/ecom/_nuxt/css/f3af2ce.css2.4 KiB
www.laposte.fr/ecom/_nuxt/css/86e357d.css2.6 KiB
www.laposte.fr/ecom/_nuxt/css/f3bbfb3.css4.4 KiB151 ms
www.laposte.fr/ecom/_nuxt/css/da75bd6.css10.4 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js30.0 s11.2 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43.js21600.0 s2.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.

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.

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.

Estimated savings: 600 ms 133.8 KiB
URLTransfer SizeEst Savings
www.laposte.fr/ecom/_nuxt/css/20dcb8a.css81.3 KiB78.2 KiB
www.laposte.fr/ecom/_nuxt/css/35fd672.css47.4 KiB45.5 KiB
www.laposte.fr/ecom/_nuxt/css/da75bd6.css10.1 KiB10.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.

Estimated savings: 6.0 s 1.1 MiB
URLTransfer SizeEst Savings
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js553.1 KiB440.8 KiB
www.laposte.fr/ecom/_nuxt/ace3671.modern.js192.1 KiB139.7 KiB
www.laposte.fr/ecom/_nuxt/9aeea0a.modern.js127.2 KiB127.1 KiB
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js163.8 KiB86.9 KiB
www.laposte.fr/ecom/_nuxt/ca3c383.modern.js74.8 KiB56.5 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js80.0 KiB45.4 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js104.6 KiB40.3 KiB
www.laposte.fr/ecom/_nuxt/5130bf2.modern.js89.7 KiB36.9 KiB
www.laposte.fr/ecom/_nuxt/678a774.modern.js47.7 KiB36.0 KiB
www.laposte.fr/ecom/_nuxt/dc72e0b.modern.js48.8 KiB34.5 KiB
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js81.3 KiB29.1 KiB
www.laposte.fr/ecom/_nuxt/ebc0c65.modern.js46.4 KiB28.3 KiB
www.laposte.fr/ecom/_nuxt/1163fe9.modern.js51.4 KiB25.8 KiB
www.laposte.fr/ecom/_nuxt/2593fae.modern.js28.5 KiB23.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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable1.7 s119 ms0.0 ms
www.laposte.fr/ecom/_nuxt/c0a16e9.modern.js1.5 s1.1 s3.5 ms
www.laposte.fr/ecom/_nuxt/f17692a.modern.js1.1 s943 ms0.3 ms
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js942 ms859 ms27 ms
www.laposte.fr/592 ms33 ms47 ms
www.laposte.fr/ecom/_nuxt/e1f0dc9.modern.js338 ms55 ms5.9 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js283 ms223 ms52 ms
cdn.trustcommander.net/privacy/1491/privacy_v2_67.js202 ms61 ms16 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js181 ms125 ms53 ms
try.abtasty.com/shared/analytics.6c9b51bdfcbabb565f02.js139 ms42 ms3.1 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_23.js110 ms90 ms19 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_6.js92 ms74 ms16 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js80 ms75 ms4.4 ms
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_27.js70 ms43 ms24 ms
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43.js55 ms34 ms6.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

CategoryTime Spent
Script Evaluation3.9 s
Other1.9 s
Style & Layout737 ms
Script Parsing & Compilation325 ms
Parse HTML & CSS179 ms
Garbage Collection163 ms
Rendering128 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

Failure reasonFailure 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

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
71

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

URLDisplayed sizeActual sizeExpected 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 6472 x 7296 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

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.

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
92

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.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

49
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
71
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

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

3.15 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

444 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.011

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

2.89 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.52 s

Detailed Report

Audit breakdown by category with detailed findings.

49

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.

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

URLResource SizeEst 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 KiB346.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 KiB174.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 KiB171.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 KiB96.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 KiB68.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 KiB27.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.

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.

URLTransfer SizeDuration
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js81.7 KiB82 ms
www.laposte.fr/ecom/_nuxt/ActualiteCard.CmTTAxUI.css8.2 KiB
www.laposte.fr/ecom/_nuxt/ArticleCard.CTV14oi8.css8.3 KiB
www.laposte.fr/ecom/_nuxt/InformationBannerItem.N1qPPLtz.css8.3 KiB
www.laposte.fr/ecom/_nuxt/Control.BiPFbY2Y.css7.7 KiB
www.laposte.fr/ecom/_nuxt/Calculator.B5quL4xR.css8.2 KiB
www.laposte.fr/ecom/_nuxt/Faq.DBGhYkPg.css8.2 KiB
www.laposte.fr/ecom/_nuxt/EnCeMomentALaPoste.B0sY4-ty.css8.2 KiB
www.laposte.fr/ecom/_nuxt/ArticleCards.BIUnBHma.css8.1 KiB
www.laposte.fr/ecom/_nuxt/InformationBanner.BcHQcV4-.css8.1 KiB
www.laposte.fr/ecom/_nuxt/SuiviEnvoi.Bikma-GE.css8.1 KiB
www.laposte.fr/ecom/_nuxt/Spacing.CCSch5dQ.css7.7 KiB
www.laposte.fr/ecom/_nuxt/SmartBanner.DlSfz-7-.css8.1 KiB
www.laposte.fr/ecom/_nuxt/FooterBottom.CxJI1ZCX.css9.0 KiB
www.laposte.fr/ecom/_nuxt/FooterHeadingsList.EbNlufEp.css15.4 KiB
www.laposte.fr/ecom/_nuxt/FooterSocial.CAmqbYB1.css8.2 KiB
www.laposte.fr/ecom/_nuxt/ServiceRow.lsFagR6y.css8.4 KiB
www.laposte.fr/ecom/_nuxt/FooterAppLink.CSQD42fJ.css7.8 KiB
www.laposte.fr/ecom/_nuxt/FooterApps.CJbIhS9q.css8.0 KiB
www.laposte.fr/ecom/_nuxt/FooterEngagement.B7cVu5Zc.css8.2 KiB
www.laposte.fr/ecom/_nuxt/HtmlRenderer.DnINTCJp.css8.1 KiB
www.laposte.fr/ecom/_nuxt/entry.C0t7vErM.css722.4 KiB616 ms
www.laposte.fr/ecom/_nuxt/ServiceTile.CWzOZcbb.css8.3 KiB
www.laposte.fr/ecom/_nuxt/Animco.BLMlXN3k.css9.0 KiB
www.laposte.fr/ecom/_nuxt/Row.CmtUyaqT.css15.2 KiB
www.laposte.fr/ecom/_nuxt/DirectLinks.CpSQ5g-n.css15.2 KiB
www.laposte.fr/ecom/_nuxt/MenuPanel.C2pxmLFJ.css9.4 KiB
www.laposte.fr/ecom/_nuxt/MainMenu.Bi6DnkrV.css8.2 KiB
www.laposte.fr/ecom/_nuxt/QuickAccess.BivUaHUQ.css7.9 KiB
www.laposte.fr/ecom/_nuxt/QuickAccess.VE8J6xaQ.css8.1 KiB
www.laposte.fr/ecom/_nuxt/HeaderQuick.CAzXDMwO.css8.3 KiB
www.laposte.fr/ecom/_nuxt/Chip.BbDjxImb.css8.3 KiB
www.laposte.fr/ecom/_nuxt/SearchboxProductPrice.D3c7m-Nz.css7.9 KiB
www.laposte.fr/ecom/_nuxt/SearchboxProduct.D4NZ59Qa.css8.0 KiB
www.laposte.fr/ecom/_nuxt/SearchboxDropdown.BKCxKm8i.css8.7 KiB
www.laposte.fr/ecom/_nuxt/SearchboxInput.C_yZk6zj.css8.5 KiB
www.laposte.fr/ecom/_nuxt/Searchbox.DXAgY0pC.css8.2 KiB
www.laposte.fr/ecom/_nuxt/PanelHeader.8GiC9i71.css30.3 KiB
www.laposte.fr/ecom/_nuxt/Navbar.WzFhc5u4.css8.1 KiB
www.laposte.fr/ecom/_nuxt/AccountSidePanel.BHVLvQ7A.css8.5 KiB
www.laposte.fr/ecom/_nuxt/AccessLinks.DHaiYpdn.css8.4 KiB
www.laposte.fr/ecom/_nuxt/AccessLinksBlock.Hk5KTflr.css8.2 KiB
www.laposte.fr/ecom/_nuxt/index.BRfEChR5.css24.2 KiB
www.laposte.fr/ecom/_nuxt/HeaderFull.B-TvWNb0.css15.3 KiB
www.laposte.fr/ecom/_nuxt/HeaderLight.B03CoPsn.css7.7 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/recos.95ab0575a0df949e0f20.js30.0 s11.2 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43.js21600.0 s2.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.

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

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: 700 ms 831.3 KiB
URLTransfer SizeEst Savings
www.laposte.fr/ecom/_nuxt/entry.C0t7vErM.css722.0 KiB719.1 KiB
www.laposte.fr/ecom/_nuxt/PanelHeader.8GiC9i71.css29.9 KiB29.9 KiB
www.laposte.fr/ecom/_nuxt/index.BRfEChR5.css23.8 KiB23.0 KiB
www.laposte.fr/ecom/_nuxt/FooterHeadingsList.EbNlufEp.css15.0 KiB15.0 KiB
www.laposte.fr/ecom/_nuxt/Row.CmtUyaqT.css14.8 KiB14.8 KiB
www.laposte.fr/ecom/_nuxt/HeaderFull.B-TvWNb0.css14.9 KiB14.7 KiB
www.laposte.fr/ecom/_nuxt/DirectLinks.CpSQ5g-n.css14.8 KiB14.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.

Estimated savings: 250 ms 510.3 KiB
URLTransfer SizeEst Savings
www.laposte.fr/ecom/_nuxt/C6m16DWd.js505.9 KiB279.4 KiB
www.laposte.fr/poc-av/chatbot/main.CmxAWFs4.js132.6 KiB116.5 KiB
cdn.tagcommander.com/1491/tc_LaboutiqueLaPoste_21.js80.0 KiB45.3 KiB
try.abtasty.com/5714a31785e8fb2356ca3d1bd25e4a43/main.1e0116ad91cee0a97856.js104.6 KiB40.3 KiB
www.laposte.fr/ruxitagentjs_ICA7NVfhqrux_10333260303165926.js81.3 KiB28.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

CategoryTime Spent
Other1.2 s
Script Evaluation1.0 s
Style & Layout430 ms
Parse HTML & CSS265 ms
Script Parsing & Compilation78 ms
Rendering50 ms
Garbage Collection31 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

Failure reasonFailure 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

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
71

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

Insecure URLRequest Resolution
/usr/src/assets/images/nav/nav-part-courrier.svgAllowed
/usr/src/assets/images/nav/nav-part-colis.svgAllowed
/usr/src/assets/images/nav/nav-part-demenagement.svgAllowed
/usr/src/assets/images/nav/nav-part-services.svgAllowed
/usr/src/assets/images/nav/nav-part-tous-les-produits.svgAllowed

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

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

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
83

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

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.

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

Send Feedback