Skip to content
Audit Complete

Results for https://hermes.com

Visit site
E-commerce · estimated Tracking: purchases
Spain Spain · Madrid Completed: Apr 22, 2026 22:45 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Room to improve — your 20.7s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Ecommerce · 644 peers
You 69
·
Avg 72
At average
0 50 100
Better than 8% of Ecommerce sites
Apple · 1227 peers
You 69
·
Avg 72
At average
0 50 100
Better than 7% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

Page weighs 14.4 MB (7.9 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

110 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fhermes.com)](https://beavercheck.com/results/9647db3c-064a-4425-a9d7-64539ca35487)
<a href="https://beavercheck.com/results/9647db3c-064a-4425-a9d7-64539ca35487"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhermes.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhermes.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 20.7s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 20.7s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~31%.

Speed (2)

Page takes 20.7s to load

+12% bounce

Users abandon at ~3s — you're 18.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.7s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$650 investment → $1.99/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -96%

Investment

$650

6h · 5 findings

Monthly returns

$1.99 /mo

~$24 / year

  • Bandwidth savings $1.99

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$650

6.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,127 / month at risk

~$157,524 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+5 more

Bandwidth Waste

$1.99 /mo

24840.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~2.5 MB per page load
    Saves $1.99/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

5.15 s

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

20.67 s

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

1.73 s

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

0.104

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

8.61 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

21.65 s

Detailed Report

Audit breakdown by category with detailed findings.

28

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/f577d1d7-378e-46ff-89cf-67b700d43727/loader.js?target_ty...7200.0 s50.0 KiB
dd.hermes.com/tags.js3600.0 s40.8 KiB
beacon.riskified.com/?shop=www.hermes.com&sid=600.0 s17.5 KiB
static.captcha-delivery.com/common/fonts/roboto/roboto.woff20.0 ms15.8 KiB
/is/image/hermesproduct/311950M 01_front_1?size=3000,3000...34303.0 s23.8 KiB
/is/image/hermesproduct/035007P_worn_1?size=3000,3000&ext...48797.0 s19.8 KiB
/captcha/assets/set/9990866c30ffb9417c77fbcb416009a424a2f...0.0 ms6.7 KiB
/captcha/assets/set/9990866c30ffb9417c77fbcb416009a424a2f...0.0 ms6.7 KiB
/is/image/hermesproduct/035001P_worn_1?size=3000,3000&ext...120206.0 s16.9 KiB
/is/image/hermesproduct/419001M 01_front_wm_1?size=3000,3...61823.0 s13.2 KiB
/is/image/hermesproduct/035016P_worn_1?size=3000,3000&ext...60764.0 s10.7 KiB
/is/image/hermesproduct/035017P_worn_1?size=3000,3000&ext...60764.0 s9.5 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
/is/image/hermesproduct/317087M 01_front_wm_1?size=3000,3...82923.0 s9.0 KiB
/is/image/hermesproduct/314159M 04_front_wm_1?size=3000,3...152135.0 s5.6 KiB
/captcha/assets/tpl/6dc485c0c428c35b53577b146dc6f9179f55e...0.0 ms1.8 KiB
/is/image/hermesedito/311950M 01_front_1?fit=wrap%2C0&wid...2511689.0 s15.7 KiB
static.captcha-delivery.com/captcha/assets/tpl/device-check/index.css0.0 ms1.4 KiB
/is/image/hermesedito/104326M 01_flat_wm_1?fit=wrap%2C0&w...2511689.0 s12.9 KiB
/is/image/hermesedito/P1_1080x1440_HERMES_MILAN_2026_Reve...2508454.0 s12.7 KiB
/is/image/hermesedito/082060CC55_front_wm_1?fit=wrap%2C0&...2511689.0 s11.7 KiB
/is/image/hermesedito/069016P_back_wm_4?fit=wrap%2C0&wid=...2511689.0 s9.9 KiB
static.captcha-delivery.com/common/fonts/roboto/font-face.css0.0 ms880 B
/is/image/hermesedito/261094Z A3_front_wm_1?fit=wrap%2C0&...2511689.0 s8.9 KiB
/is/image/hermesedito/261941ZHGN_front_wm_1?fit=wrap%2C0&...2511689.0 s8.7 KiB
/is/image/hermesedito/P_1080x1440_Hermes_Milan_2026_INSIT...2503997.0 s8.1 KiB
/is/image/hermesedito/087170CMAD?fit=wrap%2C0&wid=414&res...2511689.0 s7.0 KiB
www.hermes.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2870.0 s741 B
/is/image/hermesedito/750620ME01_detail_wm_4?fit=wrap%2C0...2511689.0 s3.1 KiB
/img/image-l.gif?t=17768978901900.39202502576145415&c=6qt...0.0 ms207 B
/img/image-l.gif?t=17768978905780.8747030666219023&c=6qth...0.0 ms206 B
/img/image-l.gif?t=17768978906930.980193751604135&c=6qth1...0.0 ms206 B
/img/image-l.gif?t=17768978908040.1763452365516649&c=6qth...0.0 ms206 B
/img/image-l.gif?t=17768978909170.8611429778342948&c=6qth...0.0 ms206 B
static.captcha-delivery.com/common/fonts/roboto/roboto.woff20.0 ms0 B
static.captcha-delivery.com/common/fonts/roboto/font-face.css0.0 ms0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.103607] map[node:map[boundingRect:map[bottom:645 height:549 left:0 right:412 top:96 width:412] lhId:page-1-DIV nodeLabel:h-video.fill-mode > div.video-button > div#vjs_video_3 > div.vjs-text-track-display path:1,HTML,1,BODY,3,H-ROOT,0,DIV,0,H-SHELL,0,DIV,4,MAIN,0,DIV,0,H-MAIN-CONTENT,0,DIV,1,H-HOME-PAGE,0,H-STORY-BLOCKS-CONTAINER,0,DIV,0,H-BLOCK-TEXT-ON-FULL-MEDIA,0,H-POSITIONED-UNDER-HEADER,0,DIV,0,SECTION,0,DIV,0,DIV,0,H-MEDIA-CTA,1,DIV,1,DIV,0,H-VIDEO,1,DIV,0,DIV,3,DIV selector:h-video.fill-mode > div.video-button > div#vjs_video_3 > div.vjs-text-track-display snippet:<div class="vjs-text-track-display" translate="yes" aria-live="off" aria-atomic="true" style="inset-block: 96px;"> type:node] score:0.103607 subItems:map[items:[map[cause:Unsized image element]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.044973] map[score:0.044973 subItems:map[items:[map[cause:Unsized image element]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:23.848 source:map[column:8495 line:5 type:source-location url:https://www.hermes.com/es/es/ urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:9.381 source:map[type:text value:[unattributed]]] map[reflowTime:0.737 source:map[column:1.47502e+06 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:2.205 source:map[column:759885 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:3.287 source:map[column:761047 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:3.968 source:map[column:762286 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:0.827 source:map[column:635117 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:7.331 source:map[column:3739 line:0 type:source-location url:https://www.hermes.com/es/es/9036.8bd135c62c248141.js urlProvider:network]] map[reflowTime:3.346 source:map[column:1.201805e+06 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:0.123 source:map[column:760502 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:0.184 source:map[column:23 line:305 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-W39B2P urlProvider:network]] map[reflowTime:0.144 source:map[column:1.368231e+06 line:2 type:source-location url:https://www.hermes.com/es/es/main.cdfa9c1e21af3105.js urlProvider:network]] map[reflowTime:0.126 source:map[column:88567 line:1 type:source-location url:https://dd.hermes.com/tags.js urlProvider:network]] map[reflowTime:1.288 source:map[column:630162 line:0 type:source-location url:https://www.hermes.com/es/es/1003.e6e65ab89fced861.js urlProvider:network]] map[reflowTime:2.109 source:map[column:104234 line:1 type:source-location url:https://sdk.privacy-center.org/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-web-es-web.22ecd6bfac93de604efec0b75b2c796ee1675f92.js urlProvider:network]] map[reflowTime:17.133 source:map[column:10385 line:1 type:source-location url:https://sdk.privacy-center.org/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-web-es-web.22ecd6bfac93de604efec0b75b2c796ee1675f92.js urlProvider:network]] map[reflowTime:3.756 source:map[column:260208 line:0 type:source-location url:https://www.hermes.com/es/es/1003.e6e65ab89fced861.js urlProvider:network]]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined
/is/image/hermesproduct/311950M 01_front_1?size=3000,3000...23.5 KiB8.4 KiB
a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined
/is/image/hermesproduct/035007P_worn_1?size=3000,3000&ext...19.4 KiB7.0 KiB
a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined
/is/image/hermesproduct/035001P_worn_1?size=3000,3000&ext...16.5 KiB5.9 KiB
a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined a.product-card > h-image-resizer.ng-star-inserted > div.media-wrap-square > img#img-undefined
/is/image/hermesproduct/419001M 01_front_wm_1?size=3000,3...12.9 KiB4.6 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s
URLTime Spent
hermes.com/855 ms
www.hermes.com/809 ms
www.hermes.com/es/es/0.0 ms

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 CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
h-video.fill-mode > div.video-button > div#vjs_video_3 > div.vjs-text-track-display h-video.fill-mode > div.video-button > div#vjs_video_3 > div.vjs-text-track-display
0.104
0.045

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation5.3 s
Other1.5 s
Style & Layout387 ms
Garbage Collection191 ms
Script Parsing & Compilation182 ms
Parse HTML & CSS131 ms
Rendering111 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.2 KiB
URLTransfer SizeEst Savings
26.8 KiB3.2 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 32.9 KiB
URLTransfer SizeEst Savings
26.8 KiB22.2 KiB
www.hermes.com/es/es/hermes.f6a45669f376039d.css12.7 KiB10.7 KiB

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

Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 45 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
97

Accessibility

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ver el vídeo de ilustración div.media-container > h-video.fill-mode > div.video-button > div#vjs_video_3

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MANTAS Y COJINES div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
OBJETOS DE DECORACIÓN div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
MALETAS Y BOLSOS DE VIAJE div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
SANDALIAS HOMBRE div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
MOBILIARIO Y ARTÍCULOS DE ILUMINACIÓN div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
SERVICIO DE MESA div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
SANDALIAS MUJER div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
CARTERAS div.block-media > ul.block-category-line > li.block-category-image-wrapper > a.block-category-cta
Jarrón Delta, tamaño grande ,  Precio 3.250 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Estuche Casaque Step Pyramid para 6 relojes y gemelos ,  Precio 8.800 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Globo terráqueo Odyssée 24 ,  Precio 24.700 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Papelera Chromatic ,  Precio 7.450 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Plato de postre Mosaïque au 24 platino ,  Precio 160 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Plato llano Mosaïque au 24 platino ,  Precio 195 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Taza de té y platillo Mosaïque au 24 platino ,  Precio 230 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Taza de café y platillo Mosaïque au 24 platino ,  Precio 215 € div.focus-order-undefined > div.products > h-product-card.ng-star-inserted > a.product-card
Enviar un mensaje de correo electrónico h-customer-service-contact > div.ng-star-inserted > div.email-us > a.paragraph-small
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Desktop audit not available for this result.

Send Feedback