PageSpeed Insights

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

0–49 50–89 90–100

First Contentful Paint

4.1 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

8.6 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

820 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

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

4.9 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Captured at Mar 2, 2025, 8:00 AM UTC
Emulated Moto G Power with Lighthouse 12.2.3
Unthrottled CPU/Memory Power: 508 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.126 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"

Show audits relevant to:AllFCPLCPTBT

Largest Contentful Paint element 8,630 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	7%	600 ms
Load Delay	0%	0 ms
Load Time	0%	0 ms
Render Delay	93%	8,030 ms

Minimize main-thread work 2.8 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,004 ms
Style & Layout	315 ms
Garbage Collection	170 ms
Other	161 ms
Parse HTML & CSS	78 ms
Script Parsing & Compilation	44 ms
Rendering	17 ms

Reduce JavaScript execution time 1.9 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	1,629 ms	1,220 ms	13 ms
/fr/fr/ (www.hermes.com)	975 ms	860 ms	7 ms
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	520 ms	239 ms	4 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	82 ms	75 ms	0 ms
/tags.js (dd.hermes.com)	52 ms	45 ms	2 ms
Google Tag Manager tag-manager	503 ms	456 ms	21 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	386 ms	346 ms	13 ms
/gtag/js?id=… (www.googletagmanager.com)	117 ms	109 ms	7 ms
Unattributable	330 ms	70 ms	0 ms
Unattributable	330 ms	70 ms	0 ms
Optanon consent-provider	137 ms	85 ms	5 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	137 ms	85 ms	5 ms

Reduce unused JavaScript Potential savings of 442 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	579.0 KiB	300.5 KiB
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	543.4 KiB	269.2 KiB
…./node_modules/@angular/core/fesm2022/core.mjs	41.3 KiB	11.4 KiB
…./node_modules/@ngx-formly/core/fesm2020/ngx-formly-core.mjs	9.7 KiB	9.0 KiB
…./node_modules/@angular/cdk/fesm2022/overlay.mjs	8.6 KiB	8.1 KiB
…./node_modules/@angular/animations/fesm2022/browser.mjs	15.6 KiB	8.1 KiB
…./node_modules/@angular/router/fesm2022/router.mjs	20.2 KiB	7.9 KiB
…fr/2443.bd168…b13e.js (www.hermes.com)	35.6 KiB	31.3 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	296.2 KiB	100.2 KiB
/gtag/js?id=… (www.googletagmanager.com)	142.5 KiB	53.1 KiB
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	153.7 KiB	47.0 KiB
Optanon consent-provider	79.1 KiB	40.9 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	79.1 KiB	40.9 KiB

Serve static assets with an efficient cache policy 11 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
Optanon consent-provider		91 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	1d	80 KiB
/scripttemplates/otSDKStub.js (cdn.cookielaw.org)	1d	8 KiB
…static/powered_by_logo.svg (cdn.cookielaw.org)	1d	3 KiB
hermes.com 1st party		47 KiB
/tags.js (dd.hermes.com)	1h	43 KiB
…hermesedito/hermes-logo (assets.hermes.com)	17d 8h 24m 34s	5 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

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">	…static/powered_by_logo.svg (cdn.cookielaw.org)	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
…6.32.0/otBannerSdk.js:7:7241 (cdn.cookielaw.org)	Array.prototype.fill

Reduce unused CSS Potential savings of 25 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
.vjs-svg-icon{display:inline-block;background-repeat:no-repeat;background-position:center; … } …	10.3 KiB	10.3 KiB

Avoid long main-thread tasks 9 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		901 ms
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	9,001 ms	377 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	9,828 ms	367 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	10,506 ms	88 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	9,378 ms	69 ms
Google Tag Manager tag-manager		218 ms
/gtag/js?id=… (www.googletagmanager.com)	8,084 ms	113 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	4,166 ms	105 ms
Unattributable		154 ms
Unattributable	1,422 ms	96 ms
Unattributable	7,062 ms	58 ms
Optanon consent-provider		61 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	7,152 ms	61 ms

Minimize third-party usage Third-party code blocked the main thread for 130 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	298 KiB	121 ms
/gtag/js?id=… (www.googletagmanager.com)	144 KiB	63 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	155 KiB	58 ms
Optanon consent-provider	131 KiB	11 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	80 KiB	11 ms
…9cd94024-8f29-4b75-bcc7-1a1a6b30f0cd/fr.json (cdn.cookielaw.org)	16 KiB	0 ms
…v2/otPcCenter.json (cdn.cookielaw.org)	12 KiB	0 ms
/scripttemplates/otSDKStub.js (cdn.cookielaw.org)	8 KiB	0 ms
…assets/otCommonStyles.css (cdn.cookielaw.org)	5 KiB	0 ms
…assets/otCenterRounded.json (cdn.cookielaw.org)	3 KiB	0 ms
…static/powered_by_logo.svg (cdn.cookielaw.org)	3 KiB	0 ms
…870afb0c-7f7a-4f57-a8d9-a461bd01c779/870afb0c-7f7a-4f57-a….json (cdn.cookielaw.org)	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
Google Analytics analytics	1 KiB	0 ms
/g/collect?v=… (www.google-analytics.com)	1 KiB	0 ms

Avoids an excessive DOM size 670 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		670
Maximum DOM Depth	div.cart-icon > h-svg-icon.icon-cart > svg > use <use _ngcontent-hermes-c3070670719="" href="#ng__cart">	19
Maximum Child Elements	Collection Printemps-Eté 2025Collection Automne-Hiver 2024Manteaux et vestesRob… <div _ngcontent-hermes-c1990139480="" class="seo-links ng-star-inserted">	107

User Timing marks and measures 40 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	184.16 ms	0.35 ms
Zone:ZoneAwarePromise	Measure	184.71 ms	0.69 ms
Zone:toString	Measure	185.55 ms	0.05 ms
Zone:util	Measure	185.73 ms	0.77 ms
Zone:timers	Measure	186.72 ms	0.38 ms
Zone:requestAnimationFrame	Measure	187.16 ms	0.14 ms
Zone:blocking	Measure	187.32 ms	0.08 ms
Zone:EventTarget	Measure	187.50 ms	0.90 ms
Zone:MutationObserver	Measure	188.58 ms	0.22 ms
Zone:IntersectionObserver	Measure	189.01 ms	0.19 ms
Zone:FileReader	Measure	189.27 ms	0.13 ms
Zone:on_property	Measure	189.49 ms	29.21 ms
Zone:customElements	Measure	218.84 ms	0.26 ms
Zone:XHR	Measure	219.19 ms	0.31 ms
Zone:geolocation	Measure	219.56 ms	0.14 ms
Zone:PromiseRejectionEvent	Measure	219.79 ms	0.11 ms
Zone:queueMicrotask	Measure	219.97 ms	0.03 ms
Zone	Mark	184.16 ms
Zone:ZoneAwarePromise	Mark	184.71 ms
Zone:toString	Mark	185.55 ms
Zone:util	Mark	185.73 ms
Zone:legacy	Mark	186.61 ms
Zone:timers	Mark	186.72 ms
Zone:requestAnimationFrame	Mark	187.16 ms
Zone:blocking	Mark	187.32 ms
Zone:EventTarget	Mark	187.50 ms
Zone:MutationObserver	Mark	188.58 ms
Zone:IntersectionObserver	Mark	189.01 ms
Zone:FileReader	Mark	189.27 ms
Zone:on_property	Mark	189.49 ms
Zone:customElements	Mark	218.84 ms
Zone:XHR	Mark	219.19 ms
Zone:geolocation	Mark	219.56 ms
Zone:PromiseRejectionEvent	Mark	219.79 ms
Zone:queueMicrotask	Mark	219.97 ms
mark_feature_usage	Mark	571.94 ms
mark_feature_usage	Mark	674.53 ms
mark_feature_usage	Mark	787.81 ms
mark_feature_usage	Mark	938.42 ms
mark_feature_usage	Mark	1,667.13 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

Avoids enormous network payloads Total size was 1,310 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	762.0 KiB
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	544.2 KiB
/fr/fr/ (www.hermes.com)	89.7 KiB
/tags.js (dd.hermes.com)	42.6 KiB
…fr/2443.bd168…b13e.js (www.hermes.com)	36.4 KiB
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	29.3 KiB
…fr/89294146-207c-4803-91fe-338f0d0094bd.82e34efed00bdf3d.woff2 (www.hermes.com)	19.8 KiB
Google Tag Manager tag-manager	298.3 KiB
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	154.8 KiB
/gtag/js?id=… (www.googletagmanager.com)	143.5 KiB
Optanon consent-provider	80.1 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	80.1 KiB
New Relic utility	33.3 KiB
/nr-spa-1.283.2.min.js (js-agent.newrelic.com)	33.3 KiB

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: 848.872 ms

Initial Navigation

/fr/fr/

(www.hermes.com)

…fr/runtime.ad580bf2e7ee442f.js

(www.hermes.com)

- 51.534 ms, 4.92 KiB

…fr/polyfills.3008f79f4eba0be9.js

(www.hermes.com)

- 55.396 ms, 13.51 KiB

…fr/main.4d6e093f3ab21d45.js

(www.hermes.com)

…fr/2443.bd168…b13e.js

(www.hermes.com)

- 26.191 ms, 36.40 KiB

…fr/9280.0e4bea84a6da0956.js

(www.hermes.com)

- 21.529 ms, 17.84 KiB

…fr/2280.8bdcec6f6d2c2974.js

(www.hermes.com)

- 22.22 ms, 29.33 KiB

…fr/4823.b4d7a8064e8e09a2.js

(www.hermes.com)

- 21.667 ms, 3.34 KiB

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

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

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.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://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

Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP

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.

100

Accessibility

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

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.

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.

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

Links are distinguishable without relying on color.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Links have a discernible name

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

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.

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.

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

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.

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.

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.

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

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

Best Practices

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?withShippingMethods=0&locale=fr_fr' 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/homepage?locale=fr_fr' 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?locale=fr_fr' 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.
/customer-session?withShipp…=0&locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED
/sync-form?locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED
/homepage?locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED

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

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

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 90.86% 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
…fr/hermes.e596e9b6fdd6ee6e.css:1:17031 (www.hermes.com)	h-root .skip-links, .sb-show-main .skip-links, .modal-service .skip-links	9.14%	11px
Unattributable
Legible text		90.86%	≥ 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
…fr/runtime.ad580bf2e7ee442f.js (www.hermes.com)	…fr/runtime.ad580bf2e7ee442f.js.map (www.hermes.com)
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	…fr/polyfills.3008f79f4eba0be9.js.map (www.hermes.com)
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	…fr/main.4d6e093f3ab21d45.js.map (www.hermes.com)
…fr/9280.0e4bea84a6da0956.js (www.hermes.com)	…fr/9280.0e4bea84a6da0956.js.map (www.hermes.com)
…fr/4823.b4d7a8064e8e09a2.js (www.hermes.com)	…fr/4823.b4d7a8064e8e09a2.js.map (www.hermes.com)
…fr/2443.bd168…b13e.js (www.hermes.com)	…fr/2443.bd168…b13e.js.map (www.hermes.com)
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	…fr/2280.8bdcec6f6d2c2974.js.map (www.hermes.com)

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.

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Show Hide

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Run these additional validators on your site to check additional SEO best practices.

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 have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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.

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.

Show Hide

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.

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

0–49 50–89 90–100

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

2.2 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,130 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.995

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

1.3 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Captured at Mar 2, 2025, 8:00 AM UTC
Emulated Desktop with Lighthouse 12.2.3
Unthrottled CPU/Memory Power: 366 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.126 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"

Avoid large layout shifts 1 layout shift found

Element	Layout shift score
main#main > div#content > h-main-content > div#main-content <div _ngcontent-hermes-c3015945050="" id="main-content" class="page-wrapper layout-with-margin-undefined">	0.995

Minimize main-thread work 3.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,413 ms
Style & Layout	596 ms
Other	163 ms
Garbage Collection	161 ms
Parse HTML & CSS	91 ms
Script Parsing & Compilation	48 ms
Rendering	20 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	1,941 ms	1,376 ms	14 ms
/fr/fr/ (www.hermes.com)	1,291 ms	974 ms	7 ms
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	402 ms	245 ms	4 ms
/tags.js (dd.hermes.com)	94 ms	77 ms	3 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	91 ms	80 ms	0 ms
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	64 ms	0 ms	0 ms
Google Tag Manager tag-manager	810 ms	552 ms	24 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	594 ms	357 ms	14 ms
/gtag/js?id=… (www.googletagmanager.com)	215 ms	195 ms	10 ms
Unattributable	253 ms	108 ms	0 ms
Unattributable	253 ms	108 ms	0 ms
Optanon consent-provider	218 ms	121 ms	5 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	218 ms	121 ms	5 ms
New Relic utility	81 ms	75 ms	2 ms
/nr-spa-1.283.2.min.js (js-agent.newrelic.com)	81 ms	75 ms	2 ms

Largest Contentful Paint element 2,160 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	7%	160 ms
Load Delay	0%	0 ms
Load Time	0%	0 ms
Render Delay	93%	2,000 ms

Reduce unused JavaScript Potential savings of 442 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	579.0 KiB	300.9 KiB
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	543.4 KiB	269.5 KiB
…./node_modules/@angular/core/fesm2022/core.mjs	41.3 KiB	11.4 KiB
…./node_modules/@ngx-formly/core/fesm2020/ngx-formly-core.mjs	9.7 KiB	9.0 KiB
…./node_modules/@angular/cdk/fesm2022/overlay.mjs	8.6 KiB	8.1 KiB
…./node_modules/@angular/animations/fesm2022/browser.mjs	15.6 KiB	8.1 KiB
…./node_modules/@angular/router/fesm2022/router.mjs	20.2 KiB	7.9 KiB
…fr/2443.bd168…b13e.js (www.hermes.com)	35.6 KiB	31.3 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	296.2 KiB	100.2 KiB
/gtag/js?id=… (www.googletagmanager.com)	142.5 KiB	53.2 KiB
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	153.7 KiB	47.0 KiB
Optanon consent-provider	79.1 KiB	40.9 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	79.1 KiB	40.9 KiB

Reduce the impact of third-party code Third-party code blocked the main thread for 370 ms

Third-Party	Transfer Size	Main-Thread Blocking Time
Google Tag Manager tag-manager	298 KiB	321 ms
/gtag/js?id=… (www.googletagmanager.com)	144 KiB	162 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	155 KiB	159 ms
Optanon consent-provider	131 KiB	48 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	80 KiB	48 ms
…9cd94024-8f29-4b75-bcc7-1a1a6b30f0cd/fr.json (cdn.cookielaw.org)	16 KiB	0 ms
…v2/otPcCenter.json (cdn.cookielaw.org)	12 KiB	0 ms
/scripttemplates/otSDKStub.js (cdn.cookielaw.org)	8 KiB	0 ms
…assets/otCommonStyles.css (cdn.cookielaw.org)	5 KiB	0 ms
…assets/otCenterRounded.json (cdn.cookielaw.org)	3 KiB	0 ms
…static/powered_by_logo.svg (cdn.cookielaw.org)	3 KiB	0 ms
…870afb0c-7f7a-4f57-a8d9-a461bd01c779/870afb0c-7f7a-4f57-a….json (cdn.cookielaw.org)	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
Google Analytics analytics	1 KiB	0 ms
/g/collect?v=… (www.google-analytics.com)	1 KiB	0 ms

Serve static assets with an efficient cache policy 11 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
Optanon consent-provider		91 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	1d	80 KiB
/scripttemplates/otSDKStub.js (cdn.cookielaw.org)	1d	8 KiB
…static/powered_by_logo.svg (cdn.cookielaw.org)	1d	3 KiB
hermes.com 1st party		47 KiB
/tags.js (dd.hermes.com)	1h	43 KiB
…hermesedito/hermes-logo (assets.hermes.com)	5d 12h 5m 37s	5 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

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">	…static/powered_by_logo.svg (cdn.cookielaw.org)	2.8 KiB	2.8 KiB

Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB

URL		Potential Savings
Optanon consent-provider		6.8 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)		6.8 KiB
…6.32.0/otBannerSdk.js:7:7241 (cdn.cookielaw.org)	Array.prototype.fill

Reduce unused CSS Potential savings of 25 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
.vjs-svg-icon{display:inline-block;background-repeat:no-repeat;background-position:center; … } …	10.3 KiB	10.3 KiB

Avoid long main-thread tasks 10 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,123 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	2,353 ms	484 ms
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	1,601 ms	349 ms
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	3,120 ms	96 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	2,260 ms	71 ms
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	1,950 ms	69 ms
/fr/fr/ (www.hermes.com)	390 ms	54 ms
Google Tag Manager tag-manager		331 ms
/gtag/js?id=… (www.googletagmanager.com)	2,873 ms	214 ms
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	1,045 ms	117 ms
Optanon consent-provider		98 ms
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	2,162 ms	98 ms
Unattributable		86 ms
Unattributable	2,042 ms	86 ms

Avoids an excessive DOM size 667 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		667
Maximum DOM Depth	div.cart-icon > h-svg-icon.icon-cart > svg > use <use _ngcontent-hermes-c3070670719="" href="#ng__cart">	19
Maximum Child Elements	Collection Printemps-Eté 2025Collection Automne-Hiver 2024Manteaux et vestesRob… <div _ngcontent-hermes-c1990139480="" class="seo-links ng-star-inserted">	107

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	232.21 ms	0.59 ms
Zone:ZoneAwarePromise	Measure	233.06 ms	1.04 ms
Zone:toString	Measure	234.20 ms	0.20 ms
Zone:util	Measure	234.54 ms	1.26 ms
Zone:legacy	Measure	235.85 ms	0.05 ms
Zone:timers	Measure	236.02 ms	0.48 ms
Zone:requestAnimationFrame	Measure	236.54 ms	0.16 ms
Zone:blocking	Measure	236.81 ms	0.29 ms
Zone:EventTarget	Measure	237.10 ms	1.50 ms
Zone:MutationObserver	Measure	238.70 ms	0.40 ms
Zone:IntersectionObserver	Measure	239.31 ms	0.39 ms
Zone:FileReader	Measure	239.71 ms	0.39 ms
Zone:on_property	Measure	240.15 ms	35.25 ms
Zone:customElements	Measure	275.51 ms	0.39 ms
Zone:XHR	Measure	276.05 ms	0.45 ms
Zone:geolocation	Measure	276.58 ms	3.32 ms
Zone:PromiseRejectionEvent	Measure	280.01 ms	0.29 ms
Zone:queueMicrotask	Measure	280.47 ms	0.23 ms
Zone	Mark	232.21 ms
Zone:ZoneAwarePromise	Mark	233.06 ms
Zone:toString	Mark	234.20 ms
Zone:util	Mark	234.54 ms
Zone:legacy	Mark	235.85 ms
Zone:timers	Mark	236.02 ms
Zone:requestAnimationFrame	Mark	236.54 ms
Zone:blocking	Mark	236.81 ms
Zone:EventTarget	Mark	237.10 ms
Zone:MutationObserver	Mark	238.70 ms
Zone:IntersectionObserver	Mark	239.31 ms
Zone:FileReader	Mark	239.71 ms
Zone:on_property	Mark	240.15 ms
Zone:customElements	Mark	275.51 ms
Zone:XHR	Mark	276.05 ms
Zone:geolocation	Mark	276.58 ms
Zone:PromiseRejectionEvent	Mark	280.01 ms
Zone:queueMicrotask	Mark	280.47 ms
mark_feature_usage	Mark	591.16 ms
mark_feature_usage	Mark	738.91 ms
mark_feature_usage	Mark	842.95 ms
mark_feature_usage	Mark	1,024.80 ms
mark_feature_usage	Mark	1,908.84 ms

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

Avoids enormous network payloads Total size was 1,311 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	762.1 KiB
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	544.2 KiB
/fr/fr/ (www.hermes.com)	89.8 KiB
/tags.js (dd.hermes.com)	42.6 KiB
…fr/2443.bd168…b13e.js (www.hermes.com)	36.4 KiB
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	29.3 KiB
…fr/89294146-207c-4803-91fe-338f0d0094bd.82e34efed00bdf3d.woff2 (www.hermes.com)	19.8 KiB
Google Tag Manager tag-manager	298.3 KiB
/gtm.js?id=GTM-W39B2P (www.googletagmanager.com)	154.8 KiB
/gtag/js?id=… (www.googletagmanager.com)	143.5 KiB
Optanon consent-provider	80.1 KiB
…6.32.0/otBannerSdk.js (cdn.cookielaw.org)	80.1 KiB
New Relic utility	33.3 KiB
/nr-spa-1.283.2.min.js (js-agent.newrelic.com)	33.3 KiB

Avoid chaining critical requests 6 chains found

Maximum critical path latency: 918.224 ms

Initial Navigation

/fr/fr/

(www.hermes.com)

…fr/runtime.ad580bf2e7ee442f.js

(www.hermes.com)

- 39.343 ms, 4.92 KiB

…fr/polyfills.3008f79f4eba0be9.js

(www.hermes.com)

- 27.279 ms, 13.51 KiB

…fr/main.4d6e093f3ab21d45.js

(www.hermes.com)

…fr/2443.bd168…b13e.js

(www.hermes.com)

- 25.902 ms, 36.40 KiB

…fr/9280.0e4bea84a6da0956.js

(www.hermes.com)

- 20.699 ms, 17.84 KiB

…fr/2280.8bdcec6f6d2c2974.js

(www.hermes.com)

- 26.78 ms, 29.33 KiB

…fr/4823.b4d7a8064e8e09a2.js

(www.hermes.com)

- 47.99 ms, 3.34 KiB

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

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

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.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://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

Remove duplicate modules in JavaScript bundles

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP

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.

100

Accessibility

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.

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.

[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

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

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

Links are distinguishable without relying on color.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Links have a discernible name

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

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.

Heading elements appear in a sequentially-descending 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.

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

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

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.

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 treeitem elements have accessible names

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.

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.

Image elements do not have [alt] attributes that are redundant text.

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">

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

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

[lang] attributes have a valid value

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.

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

Best Practices

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?withShippingMethods=0&locale=fr_fr' 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/homepage?locale=fr_fr' 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?locale=fr_fr' 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.
/customer-session?withShipp…=0&locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED
/sync-form?locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED
/homepage?locale=fr_fr:1:0 (bck.hermes.com)	Failed to load resource: net::ERR_FAILED

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

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

Show Hide

Uses 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

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

No issues in the Issues panel in Chrome Devtools

Page has valid 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
…fr/runtime.ad580bf2e7ee442f.js (www.hermes.com)	…fr/runtime.ad580bf2e7ee442f.js.map (www.hermes.com)
…fr/polyfills.3008f79f4eba0be9.js (www.hermes.com)	…fr/polyfills.3008f79f4eba0be9.js.map (www.hermes.com)
…fr/main.4d6e093f3ab21d45.js (www.hermes.com)	…fr/main.4d6e093f3ab21d45.js.map (www.hermes.com)
…fr/9280.0e4bea84a6da0956.js (www.hermes.com)	…fr/9280.0e4bea84a6da0956.js.map (www.hermes.com)
…fr/4823.b4d7a8064e8e09a2.js (www.hermes.com)	…fr/4823.b4d7a8064e8e09a2.js.map (www.hermes.com)
…fr/2443.bd168…b13e.js (www.hermes.com)	…fr/2443.bd168…b13e.js.map (www.hermes.com)
…fr/2280.8bdcec6f6d2c2974.js (www.hermes.com)	…fr/2280.8bdcec6f6d2c2974.js.map (www.hermes.com)

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

100

SEO

Show Hide

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Run these additional validators on your site to check additional SEO best practices.

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 have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Links are 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.

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.

Show Hide

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.