Mobile 375 × 812

Desktop 1440 × 900

Score: 69 / 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
Cookie 'OptimizelyUserId' is missing the Secure flag
Cookie 'session' is missing the Secure flag
No Content-Security-Policy header found
Page weighs 21.0 MB (11.3 MB transferred)
[](https://beavercheck.com/results/01a3cdea-2057-42b3-9a56-54391b88051c)<a href="https://beavercheck.com/results/01a3cdea-2057-42b3-9a56-54391b88051c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fashionnova.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fashionnova.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.
10.83 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
18.21 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
7.29 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
11.21 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.
42.23 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.
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 | |
|---|---|---|---|
Phone Number or Email div.flex > div.order-2 > div > form.mt-3 | creatives.attn.tv/fashionnova/white_83bd7cb4.png | 18.4 KiB | 17.5 KiB |
Woman in black sunglasses and white graphic crop top featuring a motorcycle des… div.relative > a > picture > img.absolute | /images/0v989dzu/production/ebf18777695051063d071785de04d... | 110.2 KiB | 13.1 KiB |
svg > defs > clippath#clip0_601_80690 > rect svg > defs > clippath#clip0_601_80690 > rect | creatives.attn.tv/fashionnova/Attentive_JUNE_JRS_efdfe758.jpg | 56.0 KiB | 6.3 KiB |
Woman in a shimmering bronze strapless mini dress with ruching, showcasing eleg… div.grid > div.relative > a.group > img | /images/0v989dzu/production/82a05889b43b8ce26a5578601cc1f... | 31.0 KiB | 4.2 KiB |
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.
| URL | Transfer Size | Duration |
|---|---|---|
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/main-BqfuWbND.css | 26.4 KiB | 461 ms |
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/Slider-BcQFRtnu.css# | 1.2 KiB | 917 ms |
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.
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.
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 |
|---|---|---|
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/main-BqfuWbND.css | 26.0 KiB | 23.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.
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 | 14.5 s |
| Other | 3.2 s |
| Script Parsing & Compilation | 1.3 s |
| Style & Layout | 1.0 s |
| Garbage Collection | 452 ms |
| Parse HTML & CSS | 299 ms |
| Rendering | 192 ms |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Get footer > div.fixed > div.relative > a.button-primary |
These are opportunities to improve the legibility of your content.
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 273, col 769 |
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 |
|---|---|
Failed to load resource: net::ERR_NAME_NOT_RESOLVED |
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.
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.
1.63 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.12 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
540 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.95 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.
8.32 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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/Slider-BcQFRtnu.css# | 837 B | 369 ms |
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/main-BqfuWbND.css | 26.5 KiB |
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 | |
|---|---|---|---|
DESERT HIGHWAY | 03.25.26 | JRS BANNER div.relative > a > div.relative > video.bg-neutral-100 | /images/0v989dzu/production/9500d0875276d7b9b41ada0d6679f... | 114.7 KiB | 59.3 KiB |
Woman in a shimmering bronze strapless mini dress with ruching, showcasing eleg… div.grid > div.relative > a.group > img | /images/0v989dzu/production/82a05889b43b8ce26a5578601cc1f... | 25.0 KiB | 5.2 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.
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.
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.9 s |
| Other | 966 ms |
| Style & Layout | 319 ms |
| Script Parsing & Compilation | 309 ms |
| Garbage Collection | 117 ms |
| Rendering | 98 ms |
| Parse HTML & CSS | 58 ms |
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 |
|---|---|---|
| cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/main-BqfuWbND.css | 26.0 KiB | 22.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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
SWIM div.flex > a.flex > span.body-xs-bold > span.body-xs-bold |
These are opportunities to improve the legibility of your content.
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
Stylish woman models a dark brown leather fringe halter top and pants with sung… div.relative > a > picture.relative > img.aspect-[var(--imageAspectRatio)] | /images/0v989dzu/production/d6289bc45dad28c775a8dfda50336... | 376 x 278 (1.35) | 390 x 284 (1.37) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 273, col 769 |
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 |
|---|---|
Failed to load resource: net::ERR_NAME_NOT_RESOLVED |
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.
Send Feedback