Skip to content
https://www.unikclothing.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.

39

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.

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:83.23 source:map[column:154826 line:1 type:source-location url:https://www.unikclothing.com/cdn/shop/t/49/assets/theme.min.js?v=157152455648959233221785160653 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:42.561 source:map[type:text value:[unattributed]]] map[reflowTime:7.276 source:map[column:2883 line:0 type:source-location url:https://www.unikclothing.com/cdn/shop/t/49/assets/theme.min.js?v=157152455648959233221785160653 urlProvider:network]] map[reflowTime:45.424 source:map[column:15209 line:0 type:source-location url:https://www.unikclothing.com/cdn/shop/t/49/assets/theme.min.js?v=157152455648959233221785160653 urlProvider:network]] map[reflowTime:25.166 source:map[column:16887 line:0 type:source-location url:https://www.unikclothing.com/cdn/shop/t/49/assets/theme.min.js?v=157152455648959233221785160653 urlProvider:network]] map[reflowTime:5.364 source:map[column:21370 line:0 type:source-location url:https://www.unikclothing.com/cdn/shop/t/49/assets/theme.min.js?v=157152455648959233221785160653 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
value: No additional origins are good candidates for preconnecting

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
div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img
www.unikclothing.com/cdn/shop/files/23.png?v=1793014980&width=750101.2 KiB28.4 KiB
div.image-with-text-overlay__image--merged > div.responsive-image-wrapper > picture > img.theme-img div.image-with-text-overlay__image--merged > div.responsive-image-wrapper > picture > img.theme-img
/cdn/shop/files/pap_less_scroll_mobile.gif?v=1793013195&w...161.7 KiB25.7 KiB
div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img
www.unikclothing.com/cdn/shop/files/21.png?v=1793014979&width=75081.3 KiB16.7 KiB
div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img
/cdn/shop/files/1_33abaaed-3442-4eea-8d0f-08f28f14d2ea.pn...79.4 KiB16.3 KiB
UN:IK Clothing h1.site-header__logo > a.site-header__logo-image > div.responsive-image-wrapper > img.theme-img
/cdn/shop/files/unik_black_friday_d414f0d8-63f9-4182-9ba4...17.9 KiB16.1 KiB
div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img div.content-grid-item__image > div > div.responsive-image-wrapper > img.theme-img
www.unikclothing.com/cdn/shop/files/22.png?v=1793014979&width=75070.4 KiB14.5 KiB

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

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
www.unikclothing.com/3.5 s1.3 s59 ms
Unattributable1.8 s366 ms0.0 ms
www.unikclothing.com/cdn/wpm/b264bf420w2e1681cap8d55857fm7d879f9cm.js587 ms374 ms20 ms
/cdn/shop/t/49/assets/theme.min.js?v=15715245564895923322...409 ms65 ms0.1 ms
widget.reviews.io/modern-widgets/rating-bar.js406 ms331 ms38 ms
/cdn/shop/t/49/assets/component-grid-slider.js?v=13049910...273 ms100 ms0.2 ms
www.unikclothing.com/cdn-cgi/challenge-platform/scripts/jsd/main.js268 ms224 ms3.4 ms
www.unikclothing.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.11.0.min.js256 ms143 ms9.5 ms
www.googletagmanager.com/gtag/destination?id=G-BZL79ZHJJJ&cx=c&gtm=4e6ar0230 ms175 ms34 ms
www.googletagmanager.com/gtm.js?id=GTM-N86NXLDR210 ms174 ms33 ms
/extensions/01a182e5-2df4-795d-b2b4-1998be333dde/orbe-geo...173 ms110 ms9.7 ms
sdk-static.loyaltylion.net/static/2/chunk-8bb692-ec80a01da7c9b060.js162 ms157 ms1.1 ms
sdk-static.loyaltylion.net/static/2/lion-core-5930e313bdacfeba.js140 ms95 ms0.1 ms
/cdn/s/trekkie.storefront.387430da5919a2f9b410f0ffaf5b702...138 ms105 ms11 ms
sdk-static.loyaltylion.net/static/2/lion-loader-b9ae2b937c51c0c3.js114 ms72 ms0.5 ms
cdn.506.io/eg/script.js?shop=un-ik-clothing.myshopify.com&v=12108 ms56 ms51 ms
/onsite/js/default~in_app_forms~signup_forms.e93ad1ce2be1...104 ms51 ms5.3 ms
/cdn/shopifycloud/consent-tracking-api/v0.1/consent-track...89 ms84 ms0.1 ms
/cdn/shopifycloud/storefront/assets/shop_events_listener-...78 ms75 ms1.0 ms
static.klaviyo.com/onsite/js/default~ClientStore~Render~.a41a958476569.js?cb=264 ms54 ms9.6 ms
cdn.shopify.com/shopifycloud/shop-js/modules/v2/chunk.register_C2Sc-DlE.esm.js62 ms47 ms0.2 ms
/cdn/shopifycloud/storefront/assets/storefront/load_featu...61 ms58 ms1.8 ms
/extensions/01a17318-3a87-7ed1-ac85-a6c85f27c26f/essentia...58 ms54 ms3.1 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 Evaluation4.7 s
Other2.5 s
Style & Layout1.7 s
Rendering422 ms
Script Parsing & Compilation383 ms
Parse HTML & CSS321 ms
Garbage Collection122 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.5 KiB
URLTransfer SizeEst Savings
/extensions/01a1641d-e88c-7f60-b6fc-52e66f9e31fc/reviews-...6.5 KiB2.5 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 16.5 KiB
URLTransfer SizeEst Savings
static.klaviyo.com/onsite/js/4014.ccae962fcaa72.css16.5 KiB16.5 KiB

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 12 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 30 ms
●Server Backend Latencies 530 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○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.

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
section#shopify-section-template--26717907124605__image_with_text_overlay_KTB3EM > div.wrapper-spacing--v > div.image-with-text-overlay__grid > a.image-with-text-overlay__section-link section#shopify-section-template--26717907124605__image_with_text_overlay_KTB3EM > div.wrapper-spacing--v > div.image-with-text-overlay__grid > a.image-with-text-overlay__section-link
section#shopify-section-template--26717907124605__image_with_text_overlay_jeJKKk > div.wrapper-spacing--v > div.image-with-text-overlay__grid > a.image-with-text-overlay__section-link section#shopify-section-template--26717907124605__image_with_text_overlay_jeJKKk > div.wrapper-spacing--v > div.image-with-text-overlay__grid > a.image-with-text-overlay__section-link
div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link
div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link
div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link
div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link div.content-grid > div.content-grid-item > div.content-grid-item__content > a.content-grid-item__block-link

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.

○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]` 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.
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
○Elements with visible text labels have matching accessible names.
○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
FencedFrame
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
CLOTHING div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
BRANDS div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
ACCESSORIES div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
SALE div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link div.mobile-nav__has-sublist > div.mobile-nav__toggle > button.icon-fallback-text > a.mobile-nav__link
Shop by Category li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Trending Products li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Featured Brands li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Womens Exclusive li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Core li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Collabs li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item
Hats li.dropdown-submenu > div.inner > p.h4 > a.animated-link--item

To appear in search results, crawlers need access to your app.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback