Skip to content
https://highsnobiety.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

40

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

Performance issues directly impact user engagement and conversion rates.

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.

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.

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.

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:45.493 source:map[column:208910 line:2 type:source-location url:https://www.highsnobiety.com/static-assets/application/8f23d4f1-5f66-4470-bb30-741194d40477/133.js 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:26.063 source:map[column:95970 line:0 type:source-location url:https://www.highsnobiety.com/static-assets/application/8f23d4f1-5f66-4470-bb30-741194d40477/bundle.js urlProvider:network]] map[reflowTime:19.43 source:map[column:368677 line:0 type:source-location url:https://www.highsnobiety.com/static-assets/application/8f23d4f1-5f66-4470-bb30-741194d40477/bundle.js urlProvider:network]] map[reflowTime:11.89 source:map[column:395760 line:0 type:source-location url:https://app.usercentrics.eu/browser-ui/3.99.0/index.module.js urlProvider:network]] map[reflowTime:20.611 source:map[column:437178 line:0 type:source-location url:https://app.usercentrics.eu/browser-ui/3.99.0/index.module.js urlProvider:network]]]

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
Ad div.GoogleActiveViewElement > a#link-wrapper > div > img#img-elem
tpc.googlesyndication.com/simgad/4516178547338515213?902.9 KiB884.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 KiB148.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 KiB142.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 KiB110.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 KiB55.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 KiB51.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 KiB35.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 KiB20.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 KiB18.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-6-IMG
nodeLabel: milan-brand-guide
path: 1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,0,SECTION,0,DIV,0,A,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG
selector: div.responsiveImage___eTIU7 > div.wrapper___bGRjz > picture.picture___tD9x4 > img.image___Pa58C
snippet: <img alt="milan-brand-guide" class="image___Pa58C" data-cy="responsiveImageTag" decoding="async" loading="lazy" src="https://www.highsnobiety.com/static-assets/dato/1776872484-milan-headline-…" style="object-fit:contain">

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.

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
value: No additional origins are good candidates for preconnecting

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: 767 ms
URLTime 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.

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

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.

URLTotal CPU TimeScript EvaluationScript Parse
/static-assets/application/8f23d4f1-5f66-4470-bb30-741194...5.7 s4.3 s79 ms
www.highsnobiety.com/3.9 s170 ms43 ms
Unattributable2.0 s429 ms0.0 ms
/pagead/managed/js/activeview/current/ufs_web_display.js828 ms712 ms59 ms
/gtm.js?id=GTM-WP8MCR&gtm_auth=9ktne2rrMK0xNK6MpRKFLw&gtm...770 ms689 ms57 ms
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...721 ms567 ms72 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js352 ms279 ms69 ms
www.googletagmanager.com/gtag/destination?id=AW-10850315346&cx=c&gtm=4e64k1299 ms252 ms44 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js295 ms199 ms93 ms
www.googletagmanager.com/gtag/js?id=G-96E69F43W6&cx=c&gtm=4e64k1261 ms195 ms58 ms
static.chartbeat.com/js/chartbeat.js208 ms189 ms4.2 ms
app.usercentrics.eu/browser-ui/3.99.0/index.module.js204 ms103 ms2.3 ms
connect.facebook.net/en_US/fbevents.js185 ms145 ms39 ms
/signals/config/1875659569195783?v=2.9.303&r=stable&domai...184 ms165 ms19 ms
app.usercentrics.eu/browser-ui/3.99.0/CcpaData-ea1367bd-808080af.js175 ms170 ms0.2 ms
s.pinimg.com/ct/lib/main.10d2511a.js163 ms140 ms11 ms
loader.wisepops.com/get-loader.js?v=1&site=6EdSTcmhAo149 ms134 ms12 ms
sc-static.net/scevent.min.js123 ms110 ms9.5 ms
ep2.adtrafficquality.google/sodar/sodar2.js102 ms43 ms2.2 ms
www.googletagservices.com/tag/js/gpt.js96 ms85 ms10 ms
app.usercentrics.eu/browser-ui/latest/loader.js93 ms82 ms9.7 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js82 ms65 ms17 ms
/static-assets/application/8f23d4f1-5f66-4470-bb30-741194...80 ms4.5 ms75 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation9.4 s
Other3.3 s
Style & Layout1.6 s
Script Parsing & Compilation967 ms
Parse HTML & CSS871 ms
Rendering769 ms
Garbage Collection370 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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 16.1 KiB
URLTransfer SizeEst Savings
html,body,div,span,applet,object,iframe,h1,h2,h3,h4,h5,h6...22.1 KiB16.1 KiB

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 50 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
88

Accessibility

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

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

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.

Names and labels

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.

Why this matters

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.

Best practices

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUBSCRIBE div.contentSectionWrapper___TizIy > div.section___xVV4I > form.sectionForm___vvAPL > button.subscribeButton___uGjM7
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
`[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.
Select elements have associated label elements.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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
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
`[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
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
AttributionReporting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
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 browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
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`

Send Feedback