Mobile 375 × 812

Desktop 1440 × 900

Score: 71 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
HSTS header is missing
No Content-Security-Policy header found
Page weighs 19.1 MB (7.0 MB transferred)
10 image-only link(s) without alt text
[](https://beavercheck.com/results/9ffe5f37-76db-4b30-a59f-e501c3a95727)<a href="https://beavercheck.com/results/9ffe5f37-76db-4b30-a59f-e501c3a95727"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcheekbonebeauty.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fcheekbonebeauty.comThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.67 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
14.36 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4.63 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.039
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
19.24 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
44.87 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
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.
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.
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.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| cheekbonebeauty.com/ | 891 ms |
| www.cheekbonebeauty.com/ | 0.0 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.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /cdn/shop/t/135/assets/theme.min.js?v=2245872118028019563... | 89.0 KiB | 27.5 KiB |
| cdn-widgetsrepository.yotpo.com/v1/loader/otsxLrXf6XjVfTCb2H0Ngg | 36.6 KiB | 11.4 KiB |
| /ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR/widget.js?shop=... | 21.1 KiB | 6.4 KiB |
| /v1/loader/ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR?langu... | 20.8 KiB | 6.3 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.
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.
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 11.9 s |
| Other | 7.5 s |
| Style & Layout | 5.5 s |
| Rendering | 2.1 s |
| Script Parsing & Compilation | 1.1 s |
| Parse HTML & CSS | 308 ms |
| Garbage Collection | 300 ms |
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
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR/widget.css?widg... | 40.7 KiB | 40.6 KiB |
| cdn-swell-assets.yotpo.com/bootstrap.min.css | 16.6 KiB | 16.6 KiB |
| @keyframes _notAvailableOpacity_3xpgy_1{0%,to{opacity:.8} … | 11.3 KiB | 10.2 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
| Failing Elements |
|---|
body.template-index > div > button.react-modal-sheet-backdrop body.template-index > div > button.react-modal-sheet-backdrop |
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.
| Failing Elements |
|---|
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9 div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9 |
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.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
| Failing Elements |
|---|
div > div.react-modal-sheet-container > div.react-modal-sheet-content > iframe.Giftbox-Popup-Iframe-3082023 div > div.react-modal-sheet-container > div.react-modal-sheet-content > iframe.Giftbox-Popup-Iframe-3082023 |
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.
| Failing Elements |
|---|
BUSY MOM BASICS MAKEUP BUNDLE div.product-item__inner > div.product-item__meta > div.product-item__text > h4.ff-body |
LET'S KEEP IN TOUCH div.footer__inner > div.footer__groups > div.footer__group > h4.footer__header |
These are opportunities to improve keyboard navigation in your application.
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.
| Failing Elements |
|---|
0 div.header__inner > div.header__row > div.header__row-segment > a.header__icon-touch |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| CSS appearance value slider-vertical is not standardized and will be removed. | www.cheekbonebeauty.com/ line 12936, col -1 |
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 273, col 769 |
| Unload event listeners are deprecated and will be removed. | cdn-swell-assets.yotpo.com/app.v1.0.368.js line 1, col 27328 |
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
| Source | Description |
|---|---|
d2sr58wdgggk0d.cloudfront.net/widget2/latest/main.l08DS3Jr.js line 25, col 8821 | [Amplify] Storefront access token is not set |
Refused to apply style from 'https://www.cheekbonebeauty.com/cdn/shop/t/135/assets/tiny.content.min.css?v=12520' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| /blogs/blog/lavender-rock-the-eye-shadow-pencil-that-make... | READ MORE |
| www.cheekbonebeauty.com/blogs/blog/cheekbone-x-ipsy-giveaway | READ MORE |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
764 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.08 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
489 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.048
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.97 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
9.13 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.image-hero__inner > div.image-hero__image-container > div.image > img.image__img div.image-hero__inner > div.image-hero__image-container > div.image > img.image__img | /cdn/shop/files/PRIMER_WATER_663c5829-05e8-4204-b35a-5081... | 465.9 KiB | 266.1 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
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.
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.
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.
| URL | Time Spent |
|---|---|
| cheekbonebeauty.com/ | 331 ms |
| www.cheekbonebeauty.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.
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.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /cdn/shop/t/135/assets/theme.min.js?v=2245872118028019563... | 89.0 KiB | 27.5 KiB |
| cdn-widgetsrepository.yotpo.com/v1/loader/otsxLrXf6XjVfTCb2H0Ngg | 36.6 KiB | 11.4 KiB |
| /ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR/widget.js?shop=... | 21.1 KiB | 6.4 KiB |
| /v1/loader/ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR?langu... | 20.8 KiB | 6.3 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.
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.
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
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.5 s |
| Other | 2.0 s |
| Style & Layout | 1.5 s |
| Rendering | 347 ms |
| Script Parsing & Compilation | 326 ms |
| Parse HTML & CSS | 94 ms |
| Garbage Collection | 88 ms |
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
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /ZVaOBZyzCCs6YfLE6eOInKzn52KugiMj2jCGCfnR/widget.css?widg... | 40.6 KiB | 40.6 KiB |
| cdn-swell-assets.yotpo.com/bootstrap.min.css | 16.6 KiB | 16.6 KiB |
| @keyframes _notAvailableOpacity_3xpgy_1{0%,to{opacity:.8} … | 11.3 KiB | 10.3 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
| Failing Elements |
|---|
div#giftbox-root > div.fixed > div > iframe.Giftbox-Popup-Iframe-3082023 div#giftbox-root > div.fixed > div > iframe.Giftbox-Popup-Iframe-3082023 |
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.
| Failing Elements |
|---|
BUSY MOM BASICS MAKEUP BUNDLE div.product-item__inner > div.product-item__meta > div.product-item__text > h4.ff-body |
FAVORITES div.footer__inner > div.footer__groups > div.footer__group > h4.footer__header |
These are opportunities to improve keyboard navigation in your application.
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.
| Failing Elements |
|---|
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item div.scrolling-content__inner > div.scrolling-content__marquee > span.scrolling-content__content > a.scrolling-content__item |
div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9 div._content_15jnv_59 > div._footer_15jnv_153 > div._footer_lx1p7_9 > a._root_9t7zi_9 |
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.
| Failing Elements |
|---|
0 div.header__inner > div.header__row > div.header__row-segment > a.header__icon-touch |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| CSS appearance value slider-vertical is not standardized and will be removed. | www.cheekbonebeauty.com/ line 7064, col -1 |
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 273, col 769 |
| Unload event listeners are deprecated and will be removed. | cdn-swell-assets.yotpo.com/app.v1.0.368.js line 1, col 27328 |
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
| Source | Description |
|---|---|
d2sr58wdgggk0d.cloudfront.net/widget2/latest/main.l08DS3Jr.js line 25, col 8821 | [Amplify] Storefront access token is not set |
Refused to apply style from 'https://www.cheekbonebeauty.com/cdn/shop/t/135/assets/tiny.content.min.css?v=12520' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| /blogs/blog/lavender-rock-the-eye-shadow-pencil-that-make... | READ MORE |
| www.cheekbonebeauty.com/blogs/blog/cheekbone-x-ipsy-giveaway | READ MORE |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback