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

32

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:8.021 source:map[column:4560 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:44.787 source:map[column:10280 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js urlProvider:network]] map[reflowTime:0.733 source:map[column:10760 line:12 type:source-location url:https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.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
Oddli Oddli Tankini Bottom - amelia plaid a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/AMELIA_PLAID_SWIM_MARKETING_WHITEBOARD_-_...195.8 KiB168.3 KiB
Oddli Cropped Gaucho - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/YELLOW_BASICS_MARKETING_WHITEBOARD_-_EMAI...110.4 KiB53.0 KiB
Oddli Oddli Tankini Top - amelia plaid a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/AMELIA_PLAID_SWIM_MARKETING_WHITEBOARD_-_...56.5 KiB43.5 KiB
Oddli Oddli Tankini Top - amelia plaid a.w-full > div.relative > div.relative > img.object-cover
oddli.com/cdn/shop/files/AMELIA_PLAID_TANKINI_TOP.jpg?v=1792091910&width=75053.4 KiB41.4 KiB
main#main-content > div#shopify-section-template--20004299047108__full_image_c6kQHk > div.w-full > img.w-full main#main-content > div#shopify-section-template--20004299047108__full_image_c6kQHk > div.w-full > img.w-full
/cdn/shop/files/AMELIA_PLAID_SWIM_MARKETING_WHITEBOARD_-_...89.7 KiB36.6 KiB
Oddli Oddli Tankini Bottom - amelia plaid a.w-full > div.relative > div.relative > img.object-cover
oddli.com/cdn/shop/files/AMELIA_PLAID_TANKINI_BOTTOM.jpg?v=1792091963&width=75042.9 KiB33.3 KiB
Oddli Jaden's Bralette - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/JADEN_S_PIECES_MARKETING_WHITEBOARD_-_EMA...60.8 KiB29.2 KiB
Oddli Bralette Bikini Top - amelia plaid a.w-full > div.relative > div.relative > img.object-cover
oddli.com/cdn/shop/files/AMEILA_PLAID_BRALETTE.jpg?v=1792091918&width=75037.2 KiB28.8 KiB
Oddli Bralette Bikini Top - amelia plaid a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/AMELIA_PLAID_SWIM_MARKETING_WHITEBOARD_-_...29.3 KiB22.6 KiB
Oddli 3/4 Sleeve Boat Neck Top - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/YELLOW_3_15beac87-8ced-4ff4-bba3-b9e04a44...46.7 KiB22.4 KiB
Oddli Jaden's Skirt - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/JADEN_S_PIECES_MARKETING_WHITEBOARD_-_EMA...36.7 KiB17.6 KiB
Oddli Jaden's Ruched Tank - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/JADEN_S_PIECES_MARKETING_WHITEBOARD_-_EMA...28.0 KiB13.5 KiB
Oddli Jaden's Skirt - butter yellow a.w-full > div.relative > div.relative > img.object-cover
oddli.com/cdn/shop/files/JADEN_SKIRT_YELLOW.jpg?v=1791936895&width=75027.5 KiB13.2 KiB
Oddli 3/4 Sleeve Boat Neck Dress - butter yellow a.w-full > div.relative > div.relative > img.absolute
/cdn/shop/files/YELLOW_2_052447c3-06aa-462b-a81b-1921bf41...25.9 KiB12.5 KiB
div.flex-1 > a.block > div.h-[125vw] > img.h-full div.flex-1 > a.block > div.h-[125vw] > img.h-full
/cdn/shop/files/Jensen_s_Favorite_Oddli_Photos_-_Current-...37.6 KiB5.1 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:214.464 label:Time to first byte subpart:timeToFirstByte] map[duration:10882.875 label:Element render delay subpart:elementRenderDelay]]
lhId: page-15-DIV
nodeLabel: receive 10% off your first order.
path: 1,HTML,1,BODY,11,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,FORM,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV
selector: div.needsclick > div.needsclick > div#rich-text-01M22TP7F64KR1E0RXVGB3Q9FN > div
snippet: <div style="text-align: center; line-height: 1;">

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

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.

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

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.

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
Unattributable2.6 s282 ms0.0 ms
oddli.com/1.1 s155 ms28 ms
/shopify.widget.js?shop=oddli-inc.myshopify.com&entrypoin...975 ms724 ms189 ms
shopify-widget.route.com/shopify.widget.js?shop=oddli-inc.myshopify.com611 ms448 ms160 ms
oddli.com/cdn/wpm/b264bf420w2e1681cap8d55857fm7d879f9cm.js550 ms428 ms31 ms
/powr.js?powr-token=oddli-inc.myshopify.com&external-type...410 ms400 ms5.7 ms
/onsite/js/vendors~reviews~in_app_forms~signup_forms~atla...397 ms316 ms3.2 ms
www.googletagmanager.com/gtag/js?id=AW-11131598712338 ms292 ms44 ms
oddli.com/cdn/shop/t/54/assets/base.js?v=54159610724131935301793117065312 ms88 ms1.3 ms
www.googletagmanager.com/gtag/js?id=G-LY41CW4VJG295 ms205 ms84 ms
connect.facebook.net/en_US/fbevents.js228 ms195 ms31 ms
www.googletagmanager.com/gtag/js?id=GT-NBBXWTQ209 ms168 ms40 ms
/cdn/s/trekkie.storefront.387430da5919a2f9b410f0ffaf5b702...198 ms184 ms12 ms
static.klaviyo.com/onsite/js/5663.c10b1970f298b.js?cb=2196 ms180 ms2.7 ms
/signals/config/174496264616186?v=2.9.429&r=stable&domain...185 ms154 ms30 ms
cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js161 ms49 ms10.0 ms
static.klaviyo.com/onsite/js/Render.ee1725c4b757f.js?cb=2119 ms100 ms18 ms
static.klaviyo.com/onsite/js/ClientStore.24eedccc4f3ff.js?cb=2113 ms112 ms0.8 ms
oddli.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.11.0.min.js102 ms91 ms6.1 ms
www.googletagmanager.com/gtag/js?id=AW-11131598712&cx=c&gtm=4e6ar067 ms23 ms43 ms
/shopifycloud/shop-js/modules/v2/chunk.useEventListener_B...58 ms52 ms0.0 ms
oddli.com/cdn/shopifycloud/storefront/assets/shop_events_listener-4e26a9ce.js57 ms54 ms1.5 ms
www.googletagmanager.com/gtag/js?id=GT-NBBXWTQ&cx=c&gtm=4e6ar050 ms19 ms32 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 Evaluation5.5 s
Other3.0 s
Script Parsing & Compilation865 ms
Style & Layout709 ms
Parse HTML & CSS178 ms
Garbage Collection106 ms
Rendering65 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 6.4 KiB
URLTransfer SizeEst Savings
@font-face{font-family:RM Neue; … } …29.4 KiB6.4 KiB

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 6.3 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 29.4 KiB
URLTransfer SizeEst Savings
@font-face{font-family:RM Neue; … } …29.4 KiB29.4 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
●Modern HTTP
●Optimize viewport for mobile
●User Timing marks and measures 29 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 17 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 190 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 170 ms
○INP breakdown
○LCP request discovery
○Avoid large layout shifts
96

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
div#shopify-section-template--20004299047108__hero_Jz3Kwd > div.flex > div.flex-1 > a.block div#shopify-section-template--20004299047108__hero_Jz3Kwd > div.flex > div.flex-1 > a.block

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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○Heading elements appear in a sequentially-descending order
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<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.
○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

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
oddli.com/blogs/storiesRead More

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Send Feedback