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

45

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.

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.

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:25.385 source:map[column:4598 line:1 type:source-location url:https://www.beautybakerie.com/cdn/shop/t/427/assets/theme.js?v=90278808250692751391763673199 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:88.823 source:map[type:text value:[unattributed]]] map[reflowTime:3.889 source:map[column:119 line:3935 type:source-location url:https://www.beautybakerie.com/ urlProvider:network]] map[reflowTime:25.385 source:map[column:12565 line:13 type:source-location url:https://www.beautybakerie.com/cdn/shop/t/427/assets/theme.js?v=90278808250692751391763673199 urlProvider:network]] map[reflowTime:0.582 source:map[column:10108 line:48 type:source-location url:https://www.beautybakerie.com/cdn/shop/t/427/assets/theme.js?v=90278808250692751391763673199 urlProvider:network]]]

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
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-...189.5 KiB147.5 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-2x.png?v=11938844668...173.4 KiB95.3 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...114.2 KiB72.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...73.0 KiB26.6 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

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: 890 ms

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 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: 150 ms 27.8 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.

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.

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 Evaluation168.6 s
Style & Layout3.5 s
Rendering1.7 s
Other1.4 s
Script Parsing & Compilation303 ms
Garbage Collection168 ms
Parse HTML & CSS167 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
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 15 user timings
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 1 animated element found
●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 390 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
85

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
I'm ready div.section-stack > div.section-header > div.prose > a.button
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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to item 1 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 2 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 3 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area
Go to item 4 div.section-stack > div.text-with-icons > page-dots.page-dots > button.tap-area

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

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.

SourceDescription
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 500 ()
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
Uncaught (in promise) SyntaxError: Unexpected token '<', " <!doctype "... is not valid JSON
●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
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Cherry Flambé Matte Lip Whip product-list.product-list > product-card.product-card > div.product-card__figure > a
Cherry Flambé Matte Lip Whip div.product-card__info > div.v-stack > span.product-card__title > a
Cranberry Stiletto Matte Lip Whip product-list.product-list > product-card.product-card > div.product-card__figure > a
Cranberry Stiletto Matte Lip Whip div.product-card__info > div.v-stack > span.product-card__title > a
Cookie Jar Vegan Eyelash Collection product-list.product-list > product-card.product-card > div.product-card__figure > a
Cookie Jar Vegan Eyelash Collection div.product-card__info > div.v-stack > span.product-card__title > a
Double Dip Eyeshadow Duo product-list.product-list > product-card.product-card > div.product-card__figure > a
Double Dip Eyeshadow Duo div.product-card__info > div.v-stack > span.product-card__title > a
Breakfast In Bed Eyeshadow Palette product-list.product-list > product-card.product-card > div.product-card__figure > a
Breakfast In Bed Eyeshadow Palette div.product-card__info > div.v-stack > span.product-card__title > a

To appear in search results, crawlers need access to your app.

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

Send Feedback