Skip to content
https://Sprinklepop.shop

Lighthouse Desktop

· 0 checks — Desktop 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.

99

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.

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-IMG
nodeLabel: Sprinkle All The Way - Christmas Sprinkles
path: 1,HTML,1,BODY,1,DIV,0,DIV,5,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,CENTER,0,A,0,IMG
selector: div.rte > center > a > img
snippet: <img src="https://cdn.shopify.com/s/files/1/2084/0205/files/Website_Banners_Desktop.…" alt="Sprinkle All The Way - Christmas Sprinkles" style="max-width:1000px; width:100%; height:auto; border:0;">

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.

URLResource SizeEst Savings
div.grid-product__image-mask > div.grid-product__secondary-image > image-element > img.image-style-- div.grid-product__image-mask > div.grid-product__secondary-image > image-element > img.image-style--
/cdn/shop/files/Royal-Icing-Grad-Balloons---2.png?v=17482...29.3 KiB8.2 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.

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

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.

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 3.0 KiB
URLTransfer SizeEst Savings
cdnjs.cloudflare.com/ajax/libs/mustache.js/3.1.0/mustache.js5.5 KiB3.0 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
Sprinkle All The Way - Christmas Sprinkles div.rte > center > a > img
/s/files/1/2084/0205/files/Website_Banners_Desktop.jpg?v=...

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
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.8 s
Max Potential First Input Delay 40 ms
Minify CSS
Reduce unused CSS
Avoids enormous network payloads Total size was 2,043 KiB
User Timing marks and measures 26 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.9 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 210 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 1 layout shift found
INP breakdown
Avoid long main-thread tasks
Avoid non-composited animations
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.header-layout > div.header-item > h1.site-header__logo > a.site-header__logo-link div.header-layout > div.header-item > h1.site-header__logo > a.site-header__logo-link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__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>`
`[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-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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
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
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.
No element has a `[tabindex]` value greater than 0
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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
77

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
AttributionReporting

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.

SourceDescription
sprinklepop.shop/ line 273, col 275
SyntaxError: Invalid left-hand side in assignment

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.

URLMap URL
sprinklepop.shop/
/cdn/shopifycloud/shop-js/modules/v2/loader.init-shop-car.../cdn/shopifycloud/shop-js/modules/v2/loader.init-shop-car...
/cdn/shopifycloud/shop-js/modules/v2/client.shop-cart-syn.../cdn/shopifycloud/shop-js/modules/v2/client.shop-cart-syn...
/cdn/shopifycloud/shop-js/modules/v2/client.init-shop-car.../cdn/shopifycloud/shop-js/modules/v2/client.init-shop-car...
/cdn/shopifycloud/shop-js/modules/v2/chunk.window_BV7pwtS.../cdn/shopifycloud/shop-js/modules/v2/chunk.window_BV7pwtS...
/cdn/shopifycloud/shop-js/modules/v2/chunk.validators_Cj2.../cdn/shopifycloud/shop-js/modules/v2/chunk.validators_Cj2...
sprinklepop.shop/cdn/shopifycloud/shop-js/modules/v2/chunk.v4_CSBSzmbm.esm.js/cdn/shopifycloud/shop-js/modules/v2/chunk.v4_CSBSzmbm.es...
/cdn/shopifycloud/shop-js/modules/v2/chunk.useUserRecogni.../cdn/shopifycloud/shop-js/modules/v2/chunk.useUserRecogni...
/cdn/shopifycloud/shop-js/modules/v2/chunk.useEventListen.../cdn/shopifycloud/shop-js/modules/v2/chunk.useEventListen...
/cdn/shopifycloud/shop-js/modules/v2/chunk.preact-module_.../cdn/shopifycloud/shop-js/modules/v2/chunk.preact-module_...
/cdn/shopifycloud/shop-js/modules/v2/chunk.MetricsProvide.../cdn/shopifycloud/shop-js/modules/v2/chunk.MetricsProvide...
sprinklepop.shop/cdn/shopifycloud/shop-js/modules/v2/chunk.hooks_CD5MknHr.esm.js/cdn/shopifycloud/shop-js/modules/v2/chunk.hooks_CD5MknHr...
sprinklepop.shop/cdn/shopifycloud/shop-js/modules/v2/chunk.hooks_BPe0V1kQ.esm.js/cdn/shopifycloud/shop-js/modules/v2/chunk.hooks_BPe0V1kQ...
/cdn/shopifycloud/shop-js/modules/v2/chunk.errors_DHmiSMJ.../cdn/shopifycloud/shop-js/modules/v2/chunk.errors_DHmiSMJ...
/cdn/shopifycloud/shop-js/modules/v2/chunk.document_C9LmO.../cdn/shopifycloud/shop-js/modules/v2/chunk.document_C9LmO...
/cdn/shopifycloud/shop-js/modules/v2/chunk.defineInitFunc.../cdn/shopifycloud/shop-js/modules/v2/chunk.defineInitFunc...
/cdn/shopifycloud/shop-js/modules/v2/chunk.casing_CQY6ZJf.../cdn/shopifycloud/shop-js/modules/v2/chunk.casing_CQY6ZJf...
/cdn/shopifycloud/shop-js/modules/v2/chunk.authorize_oZ0R.../cdn/shopifycloud/shop-js/modules/v2/chunk.authorize_oZ0R...
cdn.jsdelivr.net/npm/dompurify/dist/purify.min.jscdn.jsdelivr.net/npm/dompurify/dist/purify.min.js.map
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 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