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
www.beautybakerie.com/apps/awin/100631.js	600.0 s	15.1 KiB
/onsite/hosted-fonts/Poppins/latin/poppins_latin_regular_...	0.0 ms	8.0 KiB
/onsite/hosted-fonts/Poppins/latin/poppins_latin_regular_...	0.0 ms	7.9 KiB
cdn.attn.tv/beautybakerie/dtag.js	120.0 s	3.2 KiB
cdn1.stamped.io/files/widget.min.js	604800.0 s	30.2 KiB
static.klaviyo.com/onsite/js/VKAVbY/klaviyo.js?company_id=VKAVbY	1.0 s	2.7 KiB
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	2.2 KiB
cdn1.stamped.io/files/widget.min.css	604800.0 s	18.2 KiB
shop.app/checkouts/internal/preloads.js?locale=en-ES&shop_id=7364041	60.0 s	549 B
cdn.attn.tv/growth-tag-assets/client-configs/pcY.js	0.0 ms	369 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

URL	Est Savings
/cdn/shop/t/427/assets/wild-spirit.woff?v=871024687714062...	115 ms
www.beautybakerie.com/cdn/shop/files/proxima-nova-webfont.woff2	75 ms
/cdn/shop/t/427/assets/proxima-nova.woff?v=21421171389226...	70 ms
/cdn/shop/t/427/assets/ionicons.woff?v=697721085308104637...	60 ms
/cdn/shop/t/427/assets/proxima-nova-bold.woff?v=113778375...	55 ms
/cdn/shop/t/427/assets/bebas.woff?v=175485257906273820217...	45 ms
/cdn/shop/t/427/assets/proxima-nova-bold.woff2?v=66588467...	35 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:45.38 source:map[type:text value:[unattributed]]]]

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
form.needsclick > div.needsclick > div.needsclick > img.needsclick `form.needsclick > div.needsclick > div.needsclick > img.needsclick`	/company/VKAVbY/images/1e64b6a7-71c5-4655-9e9b-3e7b7937e4...	492.0 KiB	448.4 KiB
media-grid.media-grid > a.media-grid__item > div#media-grid-template--16893066707258__86ef2749-fc4a-4d61-92bc-ae2ae11351dd-166879625010a79bee-0 > img.content-over-media__media `media-grid.media-grid > a.media-grid__item > div#media-grid-template--16893066707258__86ef2749-fc4a-4d61-92bc-ae2ae11351dd-166879625010a79bee-0 > img.content-over-media__media`	/cdn/shop/files/BeautyBakerie_HimalayanLoose_1372_WebRes-...	155.8 KiB	120.8 KiB
media-grid.media-grid > a.media-grid__item > div#media-grid-template--16893066707258__86ef2749-fc4a-4d61-92bc-ae2ae11351dd-166879625010a79bee-2 > img.content-over-media__media `media-grid.media-grid > a.media-grid__item > div#media-grid-template--16893066707258__86ef2749-fc4a-4d61-92bc-ae2ae11351dd-166879625010a79bee-2 > img.content-over-media__media`	/cdn/shop/files/PS_ProofIsInThePuddin1_BL_April19.jpg?v=1...	90.1 KiB	55.1 KiB
div.relative > button.text-with-icon > div.h-stack > span.country-flags `div.relative > button.text-with-icon > div.h-stack > span.country-flags`	/cdn/shop/t/427/assets/country-flags.png?v=37230036826556...	72.0 KiB	52.4 KiB
div.section-stack > reveal-items.logo-list > a.logo-list__item > img.logo-list__image `div.section-stack > reveal-items.logo-list > a.logo-list__item > img.logo-list__image`	www.beautybakerie.com/cdn/shop/files/pr-gma.png?v=1664216939&width=230	11.9 KiB	7.2 KiB
Breakfast In Bed Eyeshadow Palette `product-card.product-card > div.product-card__figure > a > img.product-card__image`	/cdn/shop/products/PS_BreakfastInBed3_BriannaLevay_April1...	21.3 KiB	6.7 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 328 ms

URL	Time Spent
beautybakerie.com/	328 ms
www.beautybakerie.com/	0.0 ms

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

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: 320 ms 355.4 KiB

URL	Transfer Size	Est Savings
cdn.accessibly.app/accessibly/2.0.3/accessibly.js	221.5 KiB	74.7 KiB
www.googletagmanager.com/gtag/js?id=G-P4SVK2H9N8	166.9 KiB	58.9 KiB
/onsite/js/build-preview/commit-98747c9b1816a2f78e748cdc0...	51.6 KiB	36.4 KiB
www.beautybakerie.com/cdn/wpm/b0e8c7c7aw41bd75a1p837d7fd4m8b145375m.js	59.8 KiB	30.4 KiB
cdn1.stamped.io/files/widget.min.js	29.7 KiB	29.7 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_377e072d20	48.8 KiB	28.6 KiB
sdk.loyaltylion.net/static/2/20260408/loader.js	36.3 KiB	25.9 KiB
cdn1.stamped.io/files/widget.min.js?shop=beauty-bakerie-dev.myshopify.com	29.7 KiB	25.5 KiB
/cdn/shop/t/427/assets/legacy.js?v=1313694460960066784617...	38.8 KiB	23.1 KiB
code.jquery.com/jquery-3.7.0.min.js	29.6 KiB	22.2 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 47.4 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/427/assets/theme.css?v=8206518890282015674176...	25.7 KiB	19.6 KiB
cdn1.stamped.io/files/widget.min.css	17.8 KiB	17.8 KiB
.accessibly-app-hidden{visibility:hidden !important;display:none !important} …	10.6 KiB	10.0 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/Beauty_Bakerie_Web_Banner_16.svg?v=176037...	11.5 MiB
/company/VKAVbY/images/1e64b6a7-71c5-4655-9e9b-3e7b7937e4...	492.6 KiB
/cdn/shopifycloud/checkout-web/assets/c1/hooks-ButtonWith...	346.1 KiB
/cdn/shop/t/427/assets/wild-spirit.woff?v=871024687714062...	306.8 KiB
www.beautybakerie.com/cdn/shop/files/flour1200.png?v=1686747915&width=1000	270.8 KiB
cdn.accessibly.app/accessibly/2.0.3/accessibly.js	222.4 KiB
www.googletagmanager.com/gtag/js?id=G-P4SVK2H9N8	167.2 KiB
/cdn/shop/files/BeautyBakerie_HimalayanLoose_1372_WebRes-...	156.6 KiB
/cdn/shopifycloud/checkout-web/assets/c1/approval-scopes-...	108.5 KiB
/cdn/shop/files/PS_ProofIsInThePuddin1_BL_April19.jpg?v=1...	90.9 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
Other	42.0 s
Style & Layout	953 ms
Script Evaluation	947 ms
Rendering	456 ms
Parse HTML & CSS	51 ms
Script Parsing & Compilation	49 ms
Garbage Collection	42 ms

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 15 user timings

●JavaScript execution time 0.7 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid long main-thread tasks

○Avoid non-composited animations

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.

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
E-mail `form#newsletter-form-newsletter > div.fieldset-with-submit > div.form-control > label.floating-label`
By completing this form you are signing up to receive our emails and can unsubs… `div.newsletter-box > div.newsletter-content > form#newsletter-form-newsletter > p.text-xs`
E-mail `div.v-stack > form#footer-newsletter > div.form-control > label.floating-label`
Founded in 2011, learn more here. `div.footer__block-list > div.footer__block > div.prose > p`
Customer Care `div.footer__block > ul.v-stack > li > a.inline-block`
Shipping Policy `div.footer__block > ul.v-stack > li > a.inline-block`
Opt Out `div.footer__block > ul.v-stack > li > a.inline-block`
Privacy Policy `div.footer__block > ul.v-stack > li > a.inline-block`
Careers `div.footer__block > ul.v-stack > li > a.inline-block`
High Contrast Mode `div.footer__wrapper > div.footer__aside > div.footer__aside-bottom > label.footer__contrastInput`
Accept `div.privacy-bar__inner > div.v-stack > div.h-stack > button.button`
15% Off `div.needsclick > div#rich-text-016JB91TTR00000000003P14QS > h1 > span.ql-font-poppins`
Your Next Purchase `div.needsclick > div#rich-text-016JB91TTR00000000003P14QS > p > span.ql-font-poppins`

These are opportunities to improve the legibility of your content.

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--19819837030590__slideshow > x-slideshow.slideshow > slideshow-carousel#slideshow-template--19819837030590__slideshow > a#block-image_DELpyf `section#shopify-section-template--19819837030590__slideshow > x-slideshow.slideshow > slideshow-carousel#slideshow-template--19819837030590__slideshow > a#block-image_DELpyf`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●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

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

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 / Warning	Source
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	www.beautybakerie.com/

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
d.emails.beautybakerie.com/track.v2.js	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
api.ipgeolocation.io/ipgeo	`Failed to load resource: the server responded with a status of 401 ()`
/api/widgets/loyalty/launcher?apiKey=35b85b1d-2d28-4e21-8...	`Failed to load resource: the server responded with a status of 500 ()`
/cdn/shop/t/427/assets/legacy.js?v=1313694460960066784617... line 3, col 21631	`TypeError: Cannot read properties of undefined (reading 'name') at handleResponse (https://www.beautybakerie.com/cdn/shop/t/427/assets/legacy.js?v=131369446096006678461763673144:4:21632) at https://www.beautybakerie.com/cdn/shop/t/427/assets/legacy.js?v=131369446096006678461763673144:4:21736`
www.beautybakerie.com/ line 1, col 0	`Uncaught (in promise) SyntaxError: Unexpected token '<', " <!doctype "... is not valid JSON`

●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

●Page has valid source maps

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