Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	111.5 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	111.5 KiB
/signals/config/519578588728998?v=2.9.419&r=stable&domain...	1200.0 s	104.2 KiB
cdn.hextom.com/js/quickannouncementbar.js?shop=smoochiebabynyc.myshopify.com	86400.0 s	55.0 KiB
/widget/NGIAZgm4_O/loox.1705619886502.js?shop=smoochiebab...	129600.0 s	16.1 KiB
/signals/config/212128629999381?v=2.9.419&r=stable&domain...	1200.0 s	1.9 KiB
/shopifycloud/shop-js/modules/v2/loader.init-shop-cart-sy...	1800.0 s	1.1 KiB
shop.app/checkouts/internal/preloads.js?locale=en-US&shop_id=6966214707	60.0 s	403 B
/tr/?id=212128629999381&ev=PageView&dl=https%3A%2F%2Fsmoo...	0.0 ms	20 B
/tr/?id=519578588728998&ev=PageView&dl=https%3A%2F%2Fsmoo...	0.0 ms	20 B
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	0 B

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:32.666 source:map[column:30300 line:2 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 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:0.953 source:map[column:85979 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.386 source:map[column:52520 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.234 source:map[column:52578 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.291 source:map[column:52642 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:1.796 source:map[column:51866 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:28.431 source:map[column:51844 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.452 source:map[column:53473 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.123 source:map[column:54411 line:1 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:1.502 source:map[column:3346 line:9 type:source-location url:https://smoochiebaby.com/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891730924021 urlProvider:network]] map[reflowTime:0.171 source:map[type:text value:[unattributed]]]]

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-0-DIV

nodeLabel: div.slick-track > div.slide > a > div.rimage-outer-wrapper

path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,A,0,DIV

selector: div.slick-track > div.slide > a > div.rimage-outer-wrapper

snippet: <div class="rimage-outer-wrapper lazyload--manual fade-in fixed-height-item lazyloaded" data-bgset="//smoochiebaby.com/cdn/shop/files/1N0A1329_180x.jpg?v=1769636425 180w 144h…" data-parent-fit="cover" style="background-position: 50% 50%; background-image: url("https://smoochiebaby.…");">

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

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.

	URL	Resource Size	Est Savings
div.slick-track > div.slide > a > div.rimage-outer-wrapper `div.slick-track > div.slide > a > div.rimage-outer-wrapper`	/cdn/shop/files/Scene_Four_118_f0b160b7-daab-4b71-bd95-fe...	201.4 KiB	23.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
smoochiebaby.com/cdn/shop/t/5/assets/styles.css?v=156154446204586386931759333502	0 B
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	0 B

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.2 s 344.7 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891...	91.8 KiB	56.6 KiB
/extensions/01a14670-d8ec-7efa-b653-0e2fff8222da/littlere...	68.4 KiB	54.7 KiB
cdn.hextom.com/js/quickannouncementbar.js?shop=smoochiebabynyc.myshopify.com	54.7 KiB	45.2 KiB
smoochiebaby.com/cdn/wpm/b9f5e2762wb720532ap19708c42m93b2bec3m.js	82.6 KiB	39.2 KiB
connect.facebook.net/en_US/fbevents.js	111.3 KiB	38.7 KiB
/extensions/01a14670-d8ec-7efa-b653-0e2fff8222da/littlere...	37.9 KiB	34.5 KiB
/signals/config/519578588728998?v=2.9.419&r=stable&domain...	103.7 KiB	34.4 KiB
smoochiebaby.com/cdn/shop/t/5/assets/theme.js?v=174513841365284416661735923670	27.2 KiB	21.0 KiB
/extensions/01a14670-d8ec-7efa-b653-0e2fff8222da/littlere...	46.2 KiB	20.4 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.4 s	95 ms	0.0 ms
/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891...	1.2 s	641 ms	52 ms
smoochiebaby.com/	843 ms	136 ms	26 ms
connect.facebook.net/en_US/fbevents.js	428 ms	331 ms	78 ms
smoochiebaby.com/cdn/wpm/b9f5e2762wb720532ap19708c42m93b2bec3m.js	410 ms	364 ms	37 ms
/signals/config/519578588728998?v=2.9.419&r=stable&domain...	330 ms	266 ms	63 ms
smoochiebaby.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.11.0.min.js	245 ms	213 ms	13 ms
/cdn/s/trekkie.storefront.32ff6085714fe9c4d5859e332c5de5f...	171 ms	132 ms	18 ms
/widget/NGIAZgm4_O/loox.1705619886502.js?shop=smoochiebab...	128 ms	117 ms	8.5 ms
/cdn/shopifycloud/storefront/assets/shopify_pay/storefron...	117 ms	106 ms	9.7 ms
cdn.shopify.com/shopifycloud/shop-js/modules/v2/chunk.register_cLcgCW8c.esm.js	117 ms	112 ms	0.4 ms
/extensions/01a14670-d8ec-7efa-b653-0e2fff8222da/littlere...	114 ms	110 ms	1.1 ms
/extensions/01a14670-d8ec-7efa-b653-0e2fff8222da/littlere...	83 ms	82 ms	0.1 ms
cdn.hextom.com/js/quickannouncementbar.js?shop=smoochiebabynyc.myshopify.com	57 ms	20 ms	34 ms
/shopifycloud/shop-js/modules/v2/chunk.useEventListener_B...	52 ms	50 ms	0.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.

Category	Time Spent
Script Evaluation	3.3 s
Other	2.0 s
Style & Layout	491 ms
Script Parsing & Compilation	389 ms
Parse HTML & CSS	109 ms
Garbage Collection	73 ms
Rendering	55 ms

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 15.9 KiB

URL	Transfer Size	Est Savings
:host { --lr-primary-button-color: #e98a95; --lr-primary-button-text-color: #ffffff; … } …	17.4 KiB	15.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/cdn/shop/files/Scene_Four_118_f0b160b7-daab-4b71-bd95-fe...	202.2 KiB
smoochiebaby.com/cdn/shopifycloud/checkout-web/assets/c1/164ad2e3.FTBuhkTQ.js	184.1 KiB
/cdn/shop/files/NewWaveTribe2024-11-16at11.44.06pm20_1296...	174.6 KiB
smoochiebaby.com/cdn/shop/files/1N0A1329_1080x.jpg?v=1769636425	121.3 KiB
connect.facebook.net/en_US/fbevents.js	111.5 KiB
connect.facebook.net/en_US/fbevents.js	111.5 KiB
/signals/config/519578588728998?v=2.9.419&r=stable&domain...	104.2 KiB
/cdn/shop/t/5/assets/vendor.min.js?v=94133092853101918891...	92.8 KiB
smoochiebaby.com/cdn/shopifycloud/checkout-web/assets/c1/6a2fc6d6.ob2Vz3Qz.js	89.8 KiB
smoochiebaby.com/cdn/shopifycloud/checkout-web/assets/c1/4b4bc88f.z1yoAwwH.js	84.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Smoochie Baby `div.shoplogo > a > span.logoimg > img`	smoochiebaby.com/cdn/shop/files/sb-logo-reduced-white_480x.png?v=1613175101

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

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 17 user timings

●Avoid long main-thread tasks 17 long tasks found

●Avoid non-composited animations 8 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 120 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 10 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
For the Girls `div.overlay-text > div.overlay-text__inner > div.overlay-text__text > a`
clothing, shoes, accessories `div.overlay-text > div.overlay-text__inner > div.overlay-text__text > a`
1 2 3 4 5 `div#shopify-section-template--18680453497050__1478617204733 > div#section-id-template--18680453497050__1478617204733 > div.slideshow > ul.slick-dots`
div.slideshow > div.slide > div.overlay-text > a `div.slideshow > div.slide > div.overlay-text > a`
div.slide > div.overlay-text > div.overlay-text__inner > a `div.slide > div.overlay-text > div.overlay-text__inner > a`
Our Story it all began with a hip city mom in search of cool clothes for her s… `div.overlay-text > div.overlay-text__inner > div.overlay-text__text > a`
SEE MORE `div.overlay-text__inner > div.overlay-text__text > div.overlay-text__button-row > a.overlay-text__button`

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
Cart `span.cartsummary > span.cartsummary__inner > a > span.title`
(0) `span.cartsummary > span.cartsummary__inner > a > span.numitems`
SIGN UP `form#contact_form > div.inline-input-button-row > div.inline-input-button-row__button > button`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How it works `div.w-full > div.bg-[var(--lr-primary-bg-color)] > div.flex > h6.text-xl`

These are opportunities to improve keyboard navigation in your application.

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 > div.page-header > span.store-message > a `div > div.page-header > span.store-message > a`

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.

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
For the Girls clothing, shoes, accessories SEE MORE `div.slideshow > div.slick-list > div.slick-track > div.slide`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●Document has a `<title>` element

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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 `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

○Links are distinguishable without relying on color.

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
smoochiebaby.com/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

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

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 destination	Link Text
smoochiebaby.com/collections/end-of-season-sale	SEE MORE
smoochiebaby.com/collections/girls	SEE MORE
smoochiebaby.com/collections/boys	SEE MORE
smoochiebaby.com/collections/goods	SEE MORE
smoochiebaby.com/collections/new-arrivals	SEE MORE
smoochiebaby.com/collections/end-of-season-sale	SEE MORE
smoochiebaby.com/collections/girls	SEE MORE
smoochiebaby.com/pages/our-story	SEE 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`