Lighthouse Desktop

· 0 checks — Desktop 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
/signals/config/652808605949138?v=2.9.419&r=stable&domain...	1200.0 s	104.4 KiB
www.redditstatic.com/ads/pixel.js	60.0 s	24.6 KiB
app.tncapp.com/get_script/?shop_url=morris-and-king.myshopify.com	0.0 ms	18.3 KiB
/mcjs-connected/js/users/da184d956f7ef62815f4509a7/782769...	278.0 s	5.8 KiB
zegsuapps.com/imgs/instagenie/instagram-user.png	86400.0 s	10.6 KiB
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	2.4 KiB
sdks.automizely.com/conversions/v1/mat_popup_bars.js	86400.0 s	5.1 KiB
/conversions/v1/conversions.js?app_connection_id=9a95b40b...	86400.0 s	4.8 KiB
mcjs.prd.a.intuit.com/assets/pixel-reporting-sdk/1.22.0/main-qizrsdxz.js	0.0 ms	1.5 KiB
mcjs.prd.a.intuit.com/assets/pixel-reporting-sdk/1.22.0/user-service-B5PzfKgO.js	0.0 ms	1.5 KiB
/assets/pixel-reporting-sdk/1.22.0/service-manager-BvDqRa...	0.0 ms	1.1 KiB
/shopifycloud/shop-js/modules/v2/loader.init-shop-cart-sy...	1800.0 s	1.1 KiB
/assets/pixel-reporting-sdk/1.22.0/window-service-Bip1-Xz...	0.0 ms	962 B
/assets/pixel-reporting-sdk/1.22.0/storage-service-C3akGE...	0.0 ms	957 B
/assets/pixel-reporting-sdk/1.22.0/logger-service-CY6PdnV...	0.0 ms	932 B
cdn.shopify.com/s/javascripts/currencies.js	90060.0 s	2.2 KiB
/assets/pixel-reporting-sdk/1.22.0/shopify-service-Dk_KSG...	0.0 ms	887 B
/assets/pixel-reporting-sdk/1.22.0/error-handling-service...	0.0 ms	817 B
mcjs.prd.a.intuit.com/assets/pixel-reporting-sdk/1.22.0/pixel-reporting-sdk.js	0.0 ms	772 B
shop.app/checkouts/internal/preloads.js?locale=en-US&shop_id=55789617342	60.0 s	501 B
/assets/pixel-reporting-sdk/1.22.0/assert-unreachable-C45...	0.0 ms	426 B

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.

URL	Est Savings
/cdn/fonts/montserrat/montserrat_n7.3c434e22befd5c18a6b4a...	30 ms

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:3.544 source:map[column:6189 line:799 type:source-location url:https://www.morrisandking.com/ 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:61.006 source:map[type:text value:[unattributed]]] map[reflowTime:3.544 source:map[column:182060 line:0 type:source-location url:https://www.morrisandking.com/cdn/wpm/b9f5e2762wb720532ap19708c42m93b2bec3m.js urlProvider:network]] map[reflowTime:33.308 source:map[column:18205 line:3 type:source-location url:https://zegsuapps.com/shopify/instagenie/widget?version=1.0.0&shop=morris-and-king.myshopify.com urlProvider:network]] map[reflowTime:3.293 source:map[column:17437 line:3 type:source-location url:https://zegsuapps.com/shopify/instagenie/widget?version=1.0.0&shop=morris-and-king.myshopify.com urlProvider:network]] map[reflowTime:0.239 source:map[column:17520 line:3 type:source-location url:https://zegsuapps.com/shopify/instagenie/widget?version=1.0.0&shop=morris-and-king.myshopify.com urlProvider:network]] map[reflowTime:1.194 source:map[column:19397 line:3 type:source-location url:https://zegsuapps.com/shopify/instagenie/widget?version=1.0.0&shop=morris-and-king.myshopify.com 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.

	URL	Resource Size	Est Savings
div.slideshow__slide > div.content-over-media > picture > img `div.slideshow__slide > div.content-over-media > picture > img`	www.morrisandking.com/cdn/shop/files/MTMbanner-3.png?v=1791588335&width=1400	244.3 KiB	112.2 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-1-VIDEO

nodeLabel: div.slideshow__slide > div.content-over-media > video-media.hidden > video

path: 1,HTML,1,BODY,15,MAIN,0,SECTION,0,SLIDESHOW-CAROUSEL,0,DIV,0,DIV,0,VIDEO-MEDIA,0,VIDEO

selector: div.slideshow__slide > div.content-over-media > video-media.hidden > video

snippet: <video playsinline="true" muted="muted" preload="metadata" poster="//www.morrisandking.com/cdn/shop/files/preview_images/c49762458dca4ca09da7…">

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

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	Duration
/extensions/019fa265-ea78-7872-b6d5-b1ba4069dba7/easy-who...	1.7 KiB	235 ms
/cdn/shop/t/14/assets/theme.css?v=11503022074907993719176...	23.5 KiB	55 ms
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	2.4 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

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.

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: 40 ms 19.1 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/14/assets/theme.css?v=11503022074907993719176...	22.8 KiB	19.1 KiB

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: 60 ms 797.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-Z53SLNVD67&cx=c&gtm=4e6ae1	190.6 KiB	129.1 KiB
www.googletagmanager.com/gtag/js?id=GT-WVCFKSP6&cx=c&gtm=4e6ae1	153.1 KiB	115.7 KiB
www.googletagmanager.com/gtag/js?id=G-Z53SLNVD67	190.6 KiB	77.2 KiB
www.googletagmanager.com/gtag/js?id=GT-WVCFKSP6	153.1 KiB	69.1 KiB
www.googletagmanager.com/gtag/js?id=AW-16495992117	164.3 KiB	53.0 KiB
sdks.automizely.com/conversions/v1/am_760.9ee7b8aa.js	48.6 KiB	44.1 KiB
connect.facebook.net/en_US/fbevents.js	111.3 KiB	38.7 KiB
www.morrisandking.com/cdn/wpm/b9f5e2762wb720532ap19708c42m93b2bec3m.js	82.6 KiB	37.5 KiB
sdks.automizely.com/conversions/v1/am_760.9ee7b8aa.js	48.6 KiB	36.8 KiB
sdks.automizely.com/conversions/v1/am_988.7efdcc28.js	40.5 KiB	32.9 KiB
/signals/config/652808605949138?v=2.9.419&r=stable&domain...	103.9 KiB	31.8 KiB
/shopify/instagenie/widget?version=1.0.0&shop=morris-and-...	61.2 KiB	31.5 KiB
sdks.automizely.com/conversions/v1/am_697.0aed64b8.js	31.5 KiB	29.8 KiB
/cdn/shop/t/14/assets/theme.js?v=120688118179581468051769...	36.3 KiB	25.1 KiB
sdks.automizely.com/conversions/v1/am_697.0aed64b8.js	31.5 KiB	24.7 KiB
ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js	29.6 KiB	20.7 KiB

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	1.1 s
Other	529 ms
Style & Layout	365 ms
Script Parsing & Compilation	196 ms
Parse HTML & CSS	58 ms
Rendering	40 ms
Garbage Collection	18 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 12.4 KiB

URL	Transfer Size	Est Savings
app.tncapp.com/get_script/?shop_url=morris-and-king.myshopify.com	17.6 KiB	3.4 KiB
/extensions/01a1349d-f0ae-7b79-84e1-fccde23ad9e8/auction-...	5.7 KiB	3.2 KiB
/extensions/01a1349d-f0ae-7b79-84e1-fccde23ad9e8/auction-...	5.7 KiB	3.1 KiB
/mcjs-connected/js/users/da184d956f7ef62815f4509a7/782769...	5.2 KiB	2.8 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
www.morrisandking.com/cdn/shop/files/MTMbanner-3.png?v=1791588335&width=1400	245.2 KiB
www.googletagmanager.com/gtag/js?id=G-Z53SLNVD67&cx=c&gtm=4e6ae1	190.7 KiB
www.googletagmanager.com/gtag/js?id=G-Z53SLNVD67	190.7 KiB
/cdn/shopifycloud/checkout-web/assets/c1/164ad2e3.FTBuhkT...	184.1 KiB
www.googletagmanager.com/gtag/js?id=AW-16495992117	164.7 KiB
www.googletagmanager.com/gtag/js?id=GT-WVCFKSP6&cx=c&gtm=4e6ae1	153.2 KiB
www.googletagmanager.com/gtag/js?id=GT-WVCFKSP6	153.2 KiB
connect.facebook.net/en_US/fbevents.js	111.5 KiB
/signals/config/652808605949138?v=2.9.419&r=stable&domain...	104.4 KiB
/cdn/shopifycloud/checkout-web/assets/c1/6a2fc6d6.ob2Vz3Q...	89.8 KiB

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

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 32 user timings

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 12 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 280 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 130 ms

○INP breakdown

○Avoid large layout shifts

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.content-over-media > video-media.hidden > video > img `div.content-over-media > video-media.hidden > video > img`

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
USD $ `ul.contents > li.localization-selectors > div.relative > button.localization-toggle`

○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]` values are valid

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

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

●Buttons have an accessible name

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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

100

Best Practices

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

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.content-over-media > video-media.hidden > video > img `div.content-over-media > video-media.hidden > video > img`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`