Mobile 375 × 812

Desktop 1440 × 900

Score: 72 / 100
Based on 8 categories, 0 sections
Room to improve — your 5.3s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
29 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/4c66e204-7d43-4ba8-96f1-527ad69f9f60)<a href="https://beavercheck.com/results/4c66e204-7d43-4ba8-96f1-527ad69f9f60"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhighsnobiety.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fhighsnobiety.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~28%.
Page takes 5.3s to load
+12% bounceUsers abandon at ~3s — you're 2.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 5.0s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No structured data
+2% bounceNo 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, …)
29 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
No skip-to-content link
+1% bounceKeyboard 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
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€383 investment → €3,247/month returns + EUR 120,500,000 risk avoided
€383
4h · 5 findings
€3,247 /mo
~€38,959 / year
EUR 120,500,000
if kept compliant
€128 — 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.
4.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,668 / month at risk
~€120,500,011 / year if left unfixed
€120,500,000
+5 more
€0.91 /mo
12280.3 MB/mo × 0.074 EUR/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
2.15 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.27 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5.00 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
8.75 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.
23.81 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Ad div.GoogleActiveViewElement > a#link-wrapper > div > img#img-elem | tpc.googlesyndication.com/simgad/4516178547338515213? | 902.9 KiB | 884.9 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872737-1776756775-hs_ed_milan_bra... | 168.6 KiB | 148.5 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872577-iuter-ss26-friends-and-fam... | 148.3 KiB | 142.3 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872814-2026-01-18-mtl-look-book-f... | 128.2 KiB | 110.9 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872814-image00009.jpg?fp-x=0.5&fp... | 59.0 KiB | 55.6 KiB |
milan-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776873129-1670784.jpg?fp-x=0.5&fp-y=... | 54.5 KiB | 51.7 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776871149-app-look0019.jpg?fp-x=0.5&... | 41.4 KiB | 35.8 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872484-milan-headline-4x5.png?fp-... | 33.7 KiB | 20.5 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776871713-4x5-brands-milan-headline.... | 29.6 KiB | 18.0 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| highsnobiety.com/ | 767 ms |
| www.highsnobiety.com/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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 reduce Javascript execution time.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 9.4 s |
| Other | 3.3 s |
| Style & Layout | 1.6 s |
| Script Parsing & Compilation | 967 ms |
| Parse HTML & CSS | 871 ms |
| Rendering | 769 ms |
| Garbage Collection | 370 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| html,body,div,span,applet,object,iframe,h1,h2,h3,h4,h5,h6... | 22.1 KiB | 16.1 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Highsnobiety Magazine Teaser Video div > aside.drawerMenu___DAflD > nav.nav___iLV_l > div.tileSlideshow___UkpPw |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
CULTURE div.contentSection___s6xm3 > footer.footer___lyeFj > ul.categoryList___dNv2e > li.categoryItem___gUdai |
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ div.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
PAUL THOMPSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
ANNA SILMAN div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
IVA DIXIT div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4 |
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4 |
HENRY LEVINSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TREY DICKENSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CHRIS ERIK THOMAS div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
HIGHSNOBIETY div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CHRIS ERIK THOMAS div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
YOHANA DESTA div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
JORDAN COLEY div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CLAIRE LANDSBAUM div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
PAUL CHAUMIEN div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TOM BARKER div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SUBSCRIBE div.contentSectionWrapper___TizIy > div.section___xVV4I > form.sectionForm___vvAPL > button.subscribeButton___uGjM7 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | /pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234 |
| AttributionReporting | /static-assets/application/8f23d4f1-5f66-4470-bb30-741194... line 1, col 323981 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
570 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.37 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
620 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.89 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.70 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Ad div.GoogleActiveViewElement > a#link-wrapper > div > img#img-elem | tpc.googlesyndication.com/simgad/1397186003224063017? | 972.8 KiB | 896.5 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872737-1776756775-hs_ed_milan_bra... | 376.7 KiB | 362.4 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872577-iuter-ss26-friends-and-fam... | 322.8 KiB | 313.2 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776871149-app-look0019.jpg?fp-x=0.5&... | 227.5 KiB | 215.3 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872814-image00009.jpg?fp-x=0.5&fp... | 182.5 KiB | 177.0 KiB |
milan-brand-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776872814-2026-01-18-mtl-look-book-f... | 190.3 KiB | 164.2 KiB |
milan-guide div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776873129-1670784.jpg?fp-x=0.5&fp-y=... | 78.0 KiB | 68.6 KiB |
milan div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C | /static-assets/dato/1776875085-new-brands-milan.png?fp-x=... | 31.4 KiB | 12.2 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| highsnobiety.com/ | 211 ms |
| www.highsnobiety.com/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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 reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /static-assets/application/8f23d4f1-5f66-4470-bb30-741194... | 1.6 s | 1.2 s | 29 ms |
| www.highsnobiety.com/ | 1.0 s | 57 ms | 12 ms |
| Unattributable | 574 ms | 98 ms | 0.0 ms |
| /gtm.js?id=GTM-WP8MCR>m_auth=9ktne2rrMK0xNK6MpRKFLw>m... | 246 ms | 225 ms | 14 ms |
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js | 238 ms | 180 ms | 20 ms |
| /pagead/managed/js/activeview/current/ufs_web_display.js | 206 ms | 177 ms | 13 ms |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js | 127 ms | 107 ms | 11 ms |
| www.googletagmanager.com/gtag/destination?id=AW-10850315346&cx=c>m=4e64k1 | 127 ms | 114 ms | 11 ms |
| /signals/config/1875659569195783?v=2.9.303&r=stable&domai... | 78 ms | 67 ms | 8.7 ms |
| www.googletagmanager.com/gtag/js?id=G-96E69F43W6&cx=c>m=4e64k1 | 72 ms | 53 ms | 16 ms |
| s.pinimg.com/ct/lib/main.10d2511a.js | 59 ms | 49 ms | 8.5 ms |
| connect.facebook.net/en_US/fbevents.js | 56 ms | 42 ms | 13 ms |
| script.hotjar.com/modules.6a0f3932cb1341a35c18.js | 54 ms | 43 ms | 9.9 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 2.7 s |
| Other | 943 ms |
| Style & Layout | 436 ms |
| Script Parsing & Compilation | 279 ms |
| Parse HTML & CSS | 242 ms |
| Rendering | 184 ms |
| Garbage Collection | 86 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| html,body,div,span,applet,object,iframe,h1,h2,h3,h4,h5,h6... | 22.2 KiB | 12.9 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js | 187.7 KiB | 98.1 KiB |
| /static-assets/application/8f23d4f1-5f66-4470-bb30-741194... | 202.8 KiB | 85.9 KiB |
| www.googletagmanager.com/gtag/js?id=G-96E69F43W6&cx=c>m=4e64k1 | 167.9 KiB | 65.4 KiB |
| www.googletagmanager.com/gtag/destination?id=AW-10850315346&cx=c>m=4e64k1 | 144.5 KiB | 59.1 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js | 105.1 KiB | 57.0 KiB |
| /gtm.js?id=GTM-WP8MCR>m_auth=9ktne2rrMK0xNK6MpRKFLw>m... | 168.8 KiB | 56.9 KiB |
| app.usercentrics.eu/browser-ui/3.99.0/index.module.js | 120.6 KiB | 54.3 KiB |
| /static-assets/application/8f23d4f1-5f66-4470-bb30-741194... | 49.7 KiB | 39.7 KiB |
| script.hotjar.com/modules.6a0f3932cb1341a35c18.js | 56.1 KiB | 36.6 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 34.4 KiB |
| app.usercentrics.eu/browser-ui/3.99.0/VirtualServiceItem-e4cab338.js | 48.6 KiB | 31.7 KiB |
| /pagead/managed/js/activeview/current/ufs_web_display.js | 73.1 KiB | 31.0 KiB |
| /pagead/managed/js/activeview/current/ufs_web_display.js | 73.1 KiB | 30.3 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Highsnobiety Magazine Teaser Video div > aside.drawerMenu___DAflD > nav.nav___iLV_l > div.tileSlideshow___UkpPw |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SPRING ‘26 ISSUE nav.horizontalMenu___r2CmG > ul.menuList___t5RuP > li.menuItem___ouxCQ > a.link___xA6rz |
CULTURE div.contentSection___s6xm3 > footer.footer___lyeFj > ul.categoryList___dNv2e > li.categoryItem___gUdai |
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz label.label___Ap4iz > div.wrapper > div.container___eA4W5 > span.label___Ap4iz |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ div.contentSectionWrapper___TizIy > div.heroDense___HZYas > article.primaryTeaser___A10XK > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ div.heroDense___HZYas > div.secondaryTeasers___Baqrq > article.secondaryTeaser___S5tsX > a.link___rADBZ |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
PAUL THOMPSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4 |
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4 |
(SHOP NOW) div.contentSection___s6xm3 > footer.footer___lyeFj > span.cta___ujsTk > a.ctaLink___oDDv4 |
HENRY LEVINSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
LUKAS MAUVE div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TOM BARKER div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
LUKAS MAUVE div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
DANIIL GRITSENKO div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TOM BARKER div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CHRIS ERIK THOMAS div.meta___kYipz > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
TREY DICKENSON div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CHRIS ERIK THOMAS div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
DELIA CAI div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
YOHANA DESTA div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
CLAIRE LANDSBAUM div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
LOUIS CHESLAW div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
JAZMINE HUGHES div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
ROSS SCARANO div.contentSection___s6xm3 > footer.footer___lyeFj > div.author___X9sGK > a.authorLink___rtr2w |
div#acc-controls-footer-0 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-0 > ul.topicContent___L8oIp > li > a.link___te5l8 |
div#acc-controls-footer-1 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-1 > ul.topicContent___L8oIp > li > a.link___te5l8 |
div#acc-controls-footer-2 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-2 > ul.topicContent___L8oIp > li > a.link___te5l8 |
div#acc-controls-footer-3 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-3 > ul.topicContent___L8oIp > li > a.link___te5l8 |
div#acc-controls-footer-4 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-4 > ul.topicContent___L8oIp > li > a.link___te5l8 |
div#acc-controls-footer-4 > ul.topicContent___L8oIp > li > a.link___te5l8 div#acc-controls-footer-4 > ul.topicContent___L8oIp > li > a.link___te5l8 |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SUBSCRIBE div.contentSectionWrapper___TizIy > div.section___xVV4I > form.sectionForm___vvAPL > button.subscribeButton___uGjM7 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | /pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234 |
| AttributionReporting | /static-assets/application/8f23d4f1-5f66-4470-bb30-741194... line 1, col 323981 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Send Feedback