PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 25, 2025, 6:00:55 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.8 s
Page LoadsGood (≤ 2.5 s)83%Needs Improvement (2.5 s - 4 s)9%Poor (> 4 s)8%75th Percentile - 1.8 sCore Web Vital
Interaction to Next Paint (INP)
268 ms
Page LoadsGood (≤ 200 ms)63%Needs Improvement (200 ms - 500 ms)27%Poor (> 500 ms)10%75th Percentile - 268 msCore Web Vital
Cumulative Layout Shift (CLS)
0.69
Page LoadsGood (≤ 0.1)51%Needs Improvement (0.1 - 0.25)8%Poor (> 0.25)41%75th Percentile - 0.69Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)91%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)4%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)87%Needs Improvement (0.8 s - 1.8 s)9%Poor (> 1.8 s)4%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.1 s
Page LoadsGood (≤ 2.5 s)81%Needs Improvement (2.5 s - 4 s)11%Poor (> 4 s)8%75th Percentile - 2.1 sCore Web Vital
Interaction to Next Paint (INP)
232 ms
Page LoadsGood (≤ 200 ms)69%Needs Improvement (200 ms - 500 ms)24%Poor (> 500 ms)7%75th Percentile - 232 msCore Web Vital
Cumulative Layout Shift (CLS)
0.22
Page LoadsGood (≤ 0.1)66%Needs Improvement (0.1 - 0.25)9%Poor (> 0.25)25%75th Percentile - 0.22Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.3 s
Page LoadsGood (≤ 1.8 s)89%Needs Improvement (1.8 s - 3 s)8%Poor (> 3 s)3%75th Percentile - 1.3 s 
Time to First Byte (TTFB)
0.9 s
Page LoadsGood (≤ 0.8 s)70%Needs Improvement (0.8 s - 1.8 s)25%Poor (> 1.8 s)4%75th Percentile - 0.9 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
34 FCP+1LCP+0TBT+5CLS+25SI+2 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
4.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
9.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
8.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 25, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 492 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 4.5 s
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 workTBT
Category
Time Spent
Script Evaluation
2,915 ms
Style & Layout
734 ms
Garbage Collection
372 ms
Other
331 ms
Parse HTML & CSS
111 ms
Script Parsing & Compilation
45 ms
Rendering
28 ms
Largest Contentful Paint element 9,800 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
En cliquant sur « Accepter tous les cookies », vous acceptez l’utilisation de c…
<p>
Phase
% of LCP
Timing
TTFB
6%
600 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
94%
9,200 ms
Reduce JavaScript execution time 2.7 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
hermes.com
1st party
2,631 ms
1,975 ms
15 ms
/fr/fr/
(www.hermes.com)
1,345 ms
1,200 ms
7 ms
596 ms
285 ms
5 ms
486 ms
309 ms
0 ms
132 ms
116 ms
0 ms
/tags.js
(dd.hermes.com)
72 ms
65 ms
3 ms
Google Tag Manager
tag-manager
1,014 ms
440 ms
16 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
1,014 ms
440 ms
16 ms
Unattributable
410 ms
108 ms
0 ms
Unattributable
410 ms
108 ms
0 ms
Optanon
consent-provider
159 ms
96 ms
7 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
159 ms
96 ms
7 ms
New Relic
utility
73 ms
67 ms
3 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
73 ms
67 ms
3 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 550 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
155 KiB
531 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
155 KiB
531 ms
Optanon
consent-provider
131 KiB
20 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
80 KiB
20 ms
16 KiB
0 ms
…v2/otPcCenter.json
(cdn.cookielaw.org)
12 KiB
0 ms
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
New Relic
utility
34 KiB
0 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/5ca1a0d07f?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/5ca1a0d07f?a=…
(bam.nr-data.net)
0 KiB
0 ms
Riskified
utility
17 KiB
0 ms
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
Reduce unused JavaScript Potential savings of 530 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.LCPFCP
URL
Transfer Size
Potential Savings
hermes.com
1st party
775.2 KiB
438.3 KiB
541.1 KiB
263.0 KiB
…./node_modules/@angular/core/fesm2022/core.mjs
41.3 KiB
10.8 KiB
…./node_modules/@ngx-formly/core/fesm2020/ngx-formly-core.mjs
9.7 KiB
9.0 KiB
…./node_modules/@angular/animations/fesm2022/browser.mjs
15.6 KiB
8.2 KiB
…./node_modules/@angular/cdk/fesm2022/overlay.mjs
8.6 KiB
8.1 KiB
…./node_modules/@angular/router/fesm2022/router.mjs
20.2 KiB
7.9 KiB
199.8 KiB
145.3 KiB
…video.js/dist/video.es.js
154.2 KiB
115.0 KiB
…m3u8-parser/dist/m3u8-parser.es.js
7.0 KiB
6.9 KiB
…mpd-parser/dist/mpd-parser.es.js
5.6 KiB
5.3 KiB
…@xmldom/xmldom/lib/dom.js
5.6 KiB
4.4 KiB
…videojs-vtt.js/lib/vtt.js
4.6 KiB
3.7 KiB
34.3 KiB
30.0 KiB
…swiper/angular/fesm2015/swiper_angular.mjs
7.4 KiB
4.5 KiB
…dom7/dom7.esm.js
2.7 KiB
2.6 KiB
…swiper/modules/pagination/pagination.js
2.1 KiB
2.1 KiB
…swiper/core/core.js
2.2 KiB
2.1 KiB
…swiper/modules/scrollbar/scrollbar.js
1.5 KiB
1.5 KiB
Google Tag Manager
tag-manager
154.0 KiB
50.4 KiB
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
154.0 KiB
50.4 KiB
Optanon
consent-provider
79.1 KiB
40.9 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
79.1 KiB
40.9 KiB
Avoid an excessive DOM size 1,390 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
1,390
Maximum DOM Depth
White
<option id="captions-foreground-color-vjs_video_3_component_540-White" value="#FFF" aria-labelledby="captions-text-legend-vjs_video_3_component_540 captions-foreground-color-v…">
29
Maximum Child Elements
Collection Printemps-Eté 2025Collection Automne-Hiver 2024Manteaux et vestesRob…
<div _ngcontent-hermes-c1990139480="" class="seo-links ng-star-inserted">
107
Remove duplicate modules in JavaScript bundles Potential savings of 7 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
node_modules/@hermes/api-model-editorial
10 KiB
10 KiB
10 KiB
Serve static assets with an efficient cache policy 29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
hermes.com
1st party
2,638 KiB
/tags.js
(dd.hermes.com)
1h
44 KiB
23h 59m 19s
391 KiB
23h 59m 19s
202 KiB
23h 59m 19s
83 KiB
23h 59m 20s
110 KiB
1d 23h 59m 38s
266 KiB
1d 23h 59m 38s
185 KiB
1d 23h 59m 38s
77 KiB
1d 23h 59m 38s
54 KiB
22d 1h 23m 18s
159 KiB
22d 1h 23m 19s
219 KiB
22d 1h 23m 19s
125 KiB
22d 1h 23m 19s
32 KiB
22d 1h 23m 19s
28 KiB
24d 9h 59m 20s
200 KiB
29d 9h 59m 19s
91 KiB
30d 9h 59m 38s
175 KiB
30d 9h 59m 38s
94 KiB
30d 9h 59m 38s
67 KiB
30d 9h 59m 38s
36 KiB
Optanon
consent-provider
91 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
80 KiB
1d
8 KiB
1d
3 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
10m
15 KiB
Properly size images Potential savings of 2,391 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
hermes.com
1st party
2,587.0 KiB
2,390.8 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/104187T%2012_worn_1?size=3000,3…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
390.4 KiB
382.4 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251035Z%20AY_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
265.2 KiB
259.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/100088FP03_worn_3?size=3000,300…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
202.0 KiB
197.9 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/104145T%2011_thumbnail_20%2…" alt="">
199.6 KiB
186.7 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251129Z%2002_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
184.4 KiB
180.7 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/087170CMAA_front_wm_1?fit=w…" alt="">
174.7 KiB
163.4 KiB
figure.ng-star-inserted > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_34_PE25_CROSS_FT?fit=wrap…" alt="">
218.1 KiB
155.5 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_11_CH2_WATCHES_402992WW00…" alt="">
125.0 KiB
117.0 KiB
figure.ng-star-inserted > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_34_PE25_CROSS_ZF_2?fit=wr…" alt="">
158.3 KiB
112.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251210Z%20A3_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
109.6 KiB
107.4 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/557005HA3X?fit=wrap%2C0&amp;wid…" alt="">
93.2 KiB
87.2 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/242068N%200I_front_wm_2?fit…" alt="">
90.5 KiB
84.7 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/703203FB2O_front_wm_1?size=3000…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
82.9 KiB
81.2 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251200Z%2002_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
77.0 KiB
75.5 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/241851ZHE5_front_wm_1?fit=w…" alt="">
67.1 KiB
62.8 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/100043FJ03_front_wm_2?size=3000…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
53.7 KiB
52.6 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/100063FPP5?fit=wrap%2C0&amp;wid…" alt="">
35.8 KiB
33.5 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_11_CH2_BELT_054550CKAA?fi…" alt="">
31.9 KiB
29.9 KiB
div.poster-image > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_34_COVER_VIDEO_HEADER_ETR…" alt="">
27.5 KiB
19.6 KiB
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
Optanon
consent-provider
2.8 KiB
2.8 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
6.8 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
6.8 KiB
Array.prototype.fill
Reduce unused CSS Potential savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
17.2 KiB
14.2 KiB
Avoid enormous network payloads Total size was 3,965 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
hermes.com
1st party
2,538.4 KiB
541.9 KiB
390.8 KiB
265.7 KiB
218.5 KiB
202.4 KiB
200.6 KiB
199.9 KiB
184.9 KiB
175.0 KiB
158.7 KiB
Avoid long main-thread tasks 11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
hermes.com
1st party
1,509 ms
12,370 ms
653 ms
10,801 ms
519 ms
15,873 ms
136 ms
11,320 ms
85 ms
/fr/fr/
(www.hermes.com)
1,332 ms
66 ms
/fr/fr/
(www.hermes.com)
1,245 ms
50 ms
Google Tag Manager
tag-manager
586 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
5,141 ms
376 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
4,810 ms
149 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
4,749 ms
61 ms
Unattributable
77 ms
Unattributable
7,845 ms
77 ms
Optanon
consent-provider
70 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
7,962 ms
70 ms
User Timing marks and measures 41 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Name
Type
Start Time
Duration
Zone
Measure
247.31 ms
0.49 ms
Zone:ZoneAwarePromise
Measure
249.28 ms
0.92 ms
Zone:toString
Measure
250.31 ms
0.19 ms
Zone:util
Measure
250.55 ms
0.85 ms
Zone:legacy
Measure
251.54 ms
0.06 ms
Zone:timers
Measure
251.67 ms
0.43 ms
Zone:requestAnimationFrame
Measure
252.20 ms
0.11 ms
Zone:blocking
Measure
252.41 ms
0.10 ms
Zone:EventTarget
Measure
252.65 ms
1.25 ms
Zone:MutationObserver
Measure
254.02 ms
0.28 ms
Zone:IntersectionObserver
Measure
254.47 ms
1.53 ms
Zone:FileReader
Measure
256.12 ms
0.28 ms
Zone:on_property
Measure
256.40 ms
34.20 ms
Zone:customElements
Measure
290.75 ms
2.05 ms
Zone:XHR
Measure
292.90 ms
0.60 ms
Zone:geolocation
Measure
293.69 ms
4.21 ms
Zone:PromiseRejectionEvent
Measure
298.04 ms
0.16 ms
Zone:queueMicrotask
Measure
298.33 ms
0.17 ms
Zone
Mark
247.31 ms
Zone:ZoneAwarePromise
Mark
249.28 ms
Zone:toString
Mark
250.31 ms
Zone:util
Mark
250.55 ms
Zone:legacy
Mark
251.54 ms
Zone:timers
Mark
251.67 ms
Zone:requestAnimationFrame
Mark
252.20 ms
Zone:blocking
Mark
252.41 ms
Zone:EventTarget
Mark
252.65 ms
Zone:MutationObserver
Mark
254.02 ms
Zone:IntersectionObserver
Mark
254.47 ms
Zone:FileReader
Mark
256.12 ms
Zone:on_property
Mark
256.40 ms
Zone:customElements
Mark
290.75 ms
Zone:XHR
Mark
292.90 ms
Zone:geolocation
Mark
293.69 ms
Zone:PromiseRejectionEvent
Mark
298.04 ms
Zone:queueMicrotask
Mark
298.33 ms
mark_feature_usage
Mark
623.48 ms
mark_feature_usage
Mark
744.90 ms
mark_feature_usage
Mark
956.08 ms
mark_feature_usage
Mark
1,137.22 ms
mark_feature_usage
Mark
1,673.66 ms
Initial server response time was short Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
hermes.com
1st party
30 ms
/fr/fr/
(www.hermes.com)
30 ms
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,902.718 ms
Initial Navigation
/fr/fr/
(www.hermes.com)
- 70.202 ms, 4.93 KiB
- 62.497 ms, 13.51 KiB
- 31.08 ms, 35.10 KiB
- 54.373 ms, 22.74 KiB
- 47.449 ms, 29.26 KiB
- 53.177 ms, 200.58 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (19)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://adservice.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://www.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://stream.hermes.cn" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://www.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://td.doubleclick.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://region1.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Audio and video
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Failing Elements
h-video.ng-star-inserted > div.video-button > div#vjs_video_3 > video#vjs_video_3_html5_api
<video preload="none" class="vjs-tech" aria-hidden="false" autoplay="" id="vjs_video_3_html5_api" tabindex="-1" loop="" muted="muted" playsinline="playsinline">
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (29)
Show Hide
[aria-*] attributes match their roles
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.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
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.
Image elements have [alt] attributes
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.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
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.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (27)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
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.
ARIA input fields have accessible names
When an input field 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 more about input field labels.
ARIA meter elements have accessible names
When a meter 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 name meter elements.
ARIA progressbar elements have accessible names
When a progressbar 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 label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
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.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field 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 more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip 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 name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem 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 more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
General
Browser errors were logged to the console
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
Source
Description
hermes.com
1st party
/fr/fr/:1:0
(www.hermes.com)
Access to XMLHttpRequest at 'https://bck.hermes.com/customer-session?locale=fr_fr&withShippingMethods=0' from origin 'https://www.hermes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
/fr/fr/:1:0
(www.hermes.com)
Access to XMLHttpRequest at 'https://bck.hermes.com/sync-form' from origin 'https://www.hermes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
/sync-form:1:0
(bck.hermes.com)
Failed to load resource: net::ERR_FAILED
/fr/fr/:4:17733
(www.hermes.com)
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) No compatible source was found for this media. [object mt]
/fr/fr/:4:17733
(www.hermes.com)
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) No compatible source was found for this media. [object mt]
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Angular
18.2.3
Hammer.js
2.0.7
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (14)
Show Hide
Uses HTTPS
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.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 95.52% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
hermes.com
1st party
h-root .skip-links, .sb-show-main .skip-links, .modal-service .skip-links
4.48%
11px
Unattributable
Legible text
95.52%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
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
Map URL
Riskified
utility
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
/sm/d3d3Lmhlcm1lcy5jb20=/
(beacon.riskified.com)
SyntaxError: Unexpected end of JSON input
hermes.com
1st party
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
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
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
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.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.4 s
Page LoadsGood (≤ 2.5 s)88%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)4%75th Percentile - 1.4 sCore Web Vital
Interaction to Next Paint (INP)
143 ms
Page LoadsGood (≤ 200 ms)84%Needs Improvement (200 ms - 500 ms)12%Poor (> 500 ms)4%75th Percentile - 143 msCore Web Vital
Cumulative Layout Shift (CLS)
0.43
Page LoadsGood (≤ 0.1)54%Needs Improvement (0.1 - 0.25)5%Poor (> 0.25)41%75th Percentile - 0.43Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.6 s
Page LoadsGood (≤ 1.8 s)96%Needs Improvement (1.8 s - 3 s)2%Poor (> 3 s)1%75th Percentile - 0.6 s 
Time to First Byte (TTFB)
0.2 s
Page LoadsGood (≤ 0.8 s)94%Needs Improvement (0.8 s - 1.8 s)4%Poor (> 1.8 s)2%75th Percentile - 0.2 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.8 s
Page LoadsGood (≤ 2.5 s)86%Needs Improvement (2.5 s - 4 s)9%Poor (> 4 s)5%75th Percentile - 1.8 sCore Web Vital
Interaction to Next Paint (INP)
108 ms
Page LoadsGood (≤ 200 ms)90%Needs Improvement (200 ms - 500 ms)8%Poor (> 500 ms)2%75th Percentile - 108 msCore Web Vital
Cumulative Layout Shift (CLS)
0.44
Page LoadsGood (≤ 0.1)60%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)33%75th Percentile - 0.44Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)94%Needs Improvement (1.8 s - 3 s)4%Poor (> 3 s)1%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)77%Needs Improvement (0.8 s - 1.8 s)20%Poor (> 1.8 s)2%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
46 FCP+10LCP+6TBT+2CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,010 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 25, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 468 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 3.7 s
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 workTBT
Category
Time Spent
Script Evaluation
2,478 ms
Style & Layout
724 ms
Other
219 ms
Garbage Collection
140 ms
Parse HTML & CSS
79 ms
Script Parsing & Compilation
42 ms
Rendering
28 ms
Reduce JavaScript execution time 2.3 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
hermes.com
1st party
2,417 ms
1,675 ms
12 ms
/fr/fr/
(www.hermes.com)
1,415 ms
1,023 ms
5 ms
416 ms
265 ms
4 ms
399 ms
228 ms
0 ms
116 ms
104 ms
0 ms
/tags.js
(dd.hermes.com)
70 ms
55 ms
2 ms
Google Tag Manager
tag-manager
536 ms
328 ms
18 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
536 ms
328 ms
18 ms
Unattributable
286 ms
130 ms
0 ms
Unattributable
286 ms
130 ms
0 ms
Optanon
consent-provider
178 ms
71 ms
6 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
178 ms
71 ms
6 ms
New Relic
utility
71 ms
65 ms
2 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
71 ms
65 ms
2 ms
Largest Contentful Paint element 3,400 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
En cliquant sur « Accepter tous les cookies », vous acceptez l’utilisation de c…
<p>
Phase
% of LCP
Timing
TTFB
5%
160 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
95%
3,240 ms
Reduce unused JavaScript Potential savings of 529 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.LCPFCP
URL
Transfer Size
Potential Savings
hermes.com
1st party
775.3 KiB
438.2 KiB
541.1 KiB
263.0 KiB
…./node_modules/@angular/core/fesm2022/core.mjs
41.3 KiB
10.8 KiB
…./node_modules/@ngx-formly/core/fesm2020/ngx-formly-core.mjs
9.7 KiB
9.0 KiB
…./node_modules/@angular/animations/fesm2022/browser.mjs
15.6 KiB
8.2 KiB
…./node_modules/@angular/cdk/fesm2022/overlay.mjs
8.6 KiB
8.1 KiB
…./node_modules/@angular/router/fesm2022/router.mjs
20.2 KiB
7.9 KiB
199.9 KiB
145.2 KiB
…video.js/dist/video.es.js
154.3 KiB
114.9 KiB
…m3u8-parser/dist/m3u8-parser.es.js
7.0 KiB
6.9 KiB
…mpd-parser/dist/mpd-parser.es.js
5.6 KiB
5.4 KiB
…@xmldom/xmldom/lib/dom.js
5.6 KiB
4.4 KiB
…videojs-vtt.js/lib/vtt.js
4.6 KiB
3.7 KiB
34.3 KiB
30.0 KiB
…swiper/angular/fesm2015/swiper_angular.mjs
7.4 KiB
4.5 KiB
…dom7/dom7.esm.js
2.7 KiB
2.6 KiB
…swiper/modules/pagination/pagination.js
2.1 KiB
2.1 KiB
…swiper/core/core.js
2.2 KiB
2.1 KiB
…swiper/modules/scrollbar/scrollbar.js
1.5 KiB
1.5 KiB
Google Tag Manager
tag-manager
154.0 KiB
50.4 KiB
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
154.0 KiB
50.4 KiB
Optanon
consent-provider
79.1 KiB
40.9 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
79.1 KiB
40.9 KiB
Avoid an excessive DOM size 1,399 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
1,399
Maximum DOM Depth
White
<option id="captions-foreground-color-vjs_video_3_component_569-White" value="#FFF" aria-labelledby="captions-text-legend-vjs_video_3_component_569 captions-foreground-color-v…">
29
Maximum Child Elements
Collection Printemps-Eté 2025Collection Automne-Hiver 2024Manteaux et vestesRob…
<div _ngcontent-hermes-c1990139480="" class="seo-links ng-star-inserted">
107
Remove duplicate modules in JavaScript bundles Potential savings of 7 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
node_modules/@hermes/api-model-editorial
10 KiB
10 KiB
10 KiB
Serve static assets with an efficient cache policy 29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
hermes.com
1st party
2,088 KiB
/tags.js
(dd.hermes.com)
1h
43 KiB
6h 36m 30s
23 KiB
11h 20m 13s
27 KiB
1d 2h 45m 39s
26 KiB
1d 2h 47m 39s
38 KiB
1d 3h 13m 5s
12 KiB
1d 3h 58m 17s
18 KiB
1d 5h 41m 59s
45 KiB
1d 9h 21m 2s
18 KiB
22d 1h 2m 55s
153 KiB
22d 1h 2m 55s
132 KiB
22d 1h 2m 56s
323 KiB
22d 1h 2m 56s
230 KiB
22d 1h 2m 56s
207 KiB
22d 1h 2m 56s
157 KiB
22d 1h 2m 56s
83 KiB
22d 1h 2m 56s
61 KiB
22d 1h 2m 56s
33 KiB
22d 1h 2m 57s
338 KiB
25d 23h 21m 39s
121 KiB
Optanon
consent-provider
91 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
80 KiB
1d
8 KiB
1d
3 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
10m
15 KiB
Properly size images Potential savings of 1,801 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
hermes.com
1st party
2,026.2 KiB
1,801.2 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/087170CMAA_front_wm_1?fit=w…" alt="">
337.8 KiB
330.4 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/104145T%2011_thumbnail_20%2…" alt="">
322.6 KiB
315.5 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_11_CH2_WATCHES_402992WW00…" alt="">
207.0 KiB
202.4 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/557005HA3X?fit=wrap%2C0&amp;wid…" alt="">
156.9 KiB
153.4 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/242068N%200I_front_wm_2?fit…" alt="">
152.2 KiB
148.9 KiB
figure.ng-star-inserted > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_169_PE25_CROSS_FT?fit=wra…" alt="">
229.3 KiB
130.8 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/241851ZHE5_front_wm_1?fit=w…" alt="">
132.0 KiB
129.1 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_11_CH2_BELT_054550CKAA?fi…" alt="">
82.9 KiB
81.1 KiB
figure.ng-star-inserted > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_169_PE25_CROSS_ZF_2?fit=w…" alt="">
120.6 KiB
68.8 KiB
div.media-wrap > h-media-picture.picture > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/100063FPP5?fit=wrap%2C0&amp;wid…" alt="">
60.2 KiB
58.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/104187T%2012_worn_1?size=3000,3…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
44.8 KiB
38.2 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251035Z%20AY_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
37.3 KiB
31.8 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251129Z%2002_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
26.9 KiB
22.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/100088FP03_worn_3?size=3000,300…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
25.1 KiB
21.4 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251210Z%20A3_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
22.9 KiB
19.5 KiB
div.poster-image > h-media-picture.ng-star-inserted > picture.ng-star-inserted > img.full-parent
<img _ngcontent-hermes-c2314175782="" loading="lazy" class="full-parent" src="https://assets.hermes.com/is/image/hermesedito/P_169_COVER_VIDEO_HEADER_ET…" alt="">
33.1 KiB
18.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/703203FB2O_front_wm_1?size=3000…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
17.3 KiB
14.7 KiB
a.product-card > h-image-resizer.ng-star-inserted > picture.media-wrap-square > img#img-undefined
<img _ngcontent-hermes-c3492399480="" height="400" width="400" data-cs-override-id="" alt="" src="//assets.hermes.com/is/image/hermesproduct/251200Z%2002_front_wm_1?size=30…" id="img-undefined" fetchpriority="auto" loading="lazy" class="ng-star-inserted">
17.2 KiB
14.6 KiB
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
Optanon
consent-provider
2.8 KiB
2.8 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
6.8 KiB
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
6.8 KiB
Array.prototype.fill
Reduce unused CSS Potential savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
17.2 KiB
14.4 KiB
Avoid enormous network payloads Total size was 3,415 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
hermes.com
1st party
2,283.1 KiB
541.9 KiB
338.2 KiB
323.0 KiB
229.7 KiB
207.4 KiB
200.7 KiB
157.3 KiB
152.6 KiB
132.3 KiB
Google Tag Manager
tag-manager
155.0 KiB
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
155.0 KiB
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
hermes.com
1st party
1,185 ms
2,722 ms
606 ms
2,081 ms
401 ms
3,888 ms
97 ms
2,482 ms
81 ms
Google Tag Manager
tag-manager
157 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
1,067 ms
157 ms
Optanon
consent-provider
82 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
1,887 ms
82 ms
Unattributable
66 ms
Unattributable
1,767 ms
66 ms
Minimize third-party usage Third-party code blocked the main thread for 210 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
155 KiB
175 ms
/gtm.js?id=GTM-W39B2P
(www.googletagmanager.com)
155 KiB
175 ms
Optanon
consent-provider
131 KiB
32 ms
…6.32.0/otBannerSdk.js
(cdn.cookielaw.org)
80 KiB
32 ms
16 KiB
0 ms
…v2/otPcCenter.json
(cdn.cookielaw.org)
12 KiB
0 ms
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
New Relic
utility
34 KiB
0 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/5ca1a0d07f?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/5ca1a0d07f?a=…
(bam.nr-data.net)
0 KiB
0 ms
Riskified
utility
17 KiB
0 ms
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
User Timing marks and measures 41 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Name
Type
Start Time
Duration
Zone
Measure
227.01 ms
1.09 ms
Zone:ZoneAwarePromise
Measure
228.29 ms
1.21 ms
Zone:toString
Measure
229.52 ms
0.18 ms
Zone:util
Measure
229.75 ms
1.15 ms
Zone:legacy
Measure
230.96 ms
0.04 ms
Zone:timers
Measure
231.12 ms
0.48 ms
Zone:requestAnimationFrame
Measure
231.70 ms
0.20 ms
Zone:blocking
Measure
231.91 ms
0.19 ms
Zone:EventTarget
Measure
232.15 ms
1.35 ms
Zone:MutationObserver
Measure
233.55 ms
0.35 ms
Zone:IntersectionObserver
Measure
234.11 ms
0.29 ms
Zone:FileReader
Measure
234.40 ms
0.20 ms
Zone:on_property
Measure
234.67 ms
33.33 ms
Zone:customElements
Measure
268.12 ms
0.48 ms
Zone:XHR
Measure
268.69 ms
0.41 ms
Zone:geolocation
Measure
269.15 ms
0.35 ms
Zone:PromiseRejectionEvent
Measure
269.50 ms
0.20 ms
Zone:queueMicrotask
Measure
269.70 ms
0.10 ms
Zone
Mark
227.01 ms
Zone:ZoneAwarePromise
Mark
228.29 ms
Zone:toString
Mark
229.52 ms
Zone:util
Mark
229.75 ms
Zone:legacy
Mark
230.96 ms
Zone:timers
Mark
231.12 ms
Zone:requestAnimationFrame
Mark
231.70 ms
Zone:blocking
Mark
231.91 ms
Zone:EventTarget
Mark
232.15 ms
Zone:MutationObserver
Mark
233.55 ms
Zone:IntersectionObserver
Mark
234.11 ms
Zone:FileReader
Mark
234.40 ms
Zone:on_property
Mark
234.67 ms
Zone:customElements
Mark
268.12 ms
Zone:XHR
Mark
268.69 ms
Zone:geolocation
Mark
269.15 ms
Zone:PromiseRejectionEvent
Mark
269.50 ms
Zone:queueMicrotask
Mark
269.70 ms
mark_feature_usage
Mark
573.32 ms
mark_feature_usage
Mark
709.89 ms
mark_feature_usage
Mark
835.06 ms
mark_feature_usage
Mark
1,259.10 ms
mark_feature_usage
Mark
1,591.12 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Compte, hors ligneComptePanierPanier, vide
<nav _ngcontent-hermes-c3463046451="" aria-label="compte et panier" role="navigation" class="account-and-cart ng-tns-c3463046451-2">
0.000
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
hermes.com
1st party
20 ms
/fr/fr/
(www.hermes.com)
20 ms
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,923.88 ms
Initial Navigation
/fr/fr/
(www.hermes.com)
- 85.046 ms, 4.93 KiB
- 89.074 ms, 13.51 KiB
- 36.179 ms, 35.11 KiB
- 33.427 ms, 22.74 KiB
- 47.295 ms, 29.26 KiB
- 60.713 ms, 200.66 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://adservice.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://www.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://stream.hermes.cn" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://www.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://td.doubleclick.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://region1.google-analytics.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Audio and video
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Failing Elements
h-video.ng-star-inserted > div.video-button > div#vjs_video_3 > video#vjs_video_3_html5_api
<video preload="none" class="vjs-tech" aria-hidden="false" autoplay="" id="vjs_video_3_html5_api" tabindex="-1" loop="" muted="muted" playsinline="playsinline">
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (29)
Show Hide
[aria-*] attributes match their roles
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.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
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.
Image elements have [alt] attributes
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.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
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.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (27)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
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.
ARIA input fields have accessible names
When an input field 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 more about input field labels.
ARIA meter elements have accessible names
When a meter 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 name meter elements.
ARIA progressbar elements have accessible names
When a progressbar 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 label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
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.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field 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 more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip 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 name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem 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 more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
General
Browser errors were logged to the console
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
Source
Description
hermes.com
1st party
/fr/fr/:1:0
(www.hermes.com)
Access to XMLHttpRequest at 'https://bck.hermes.com/customer-session?locale=fr_fr&withShippingMethods=0' from origin 'https://www.hermes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
/fr/fr/:1:0
(www.hermes.com)
Access to XMLHttpRequest at 'https://bck.hermes.com/sync-form' from origin 'https://www.hermes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
/sync-form:1:0
(bck.hermes.com)
Failed to load resource: net::ERR_FAILED
/fr/fr/:4:17733
(www.hermes.com)
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) No compatible source was found for this media. [object mt]
/fr/fr/:4:17733
(www.hermes.com)
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) No compatible source was found for this media. [object mt]
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Angular
18.2.3
Hammer.js
2.0.7
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (13)
Show Hide
Uses HTTPS
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.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
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
Map URL
Riskified
utility
/?shop=www.hermes.com&sid=
(beacon.riskified.com)
/sm/d3d3Lmhlcm1lcy5jb20=/
(beacon.riskified.com)
SyntaxError: Unexpected end of JSON input
hermes.com
1st party
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
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
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
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.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.