Skip to content
Audit Complete

Results for https://www.fashionnova.com

Visit site
United Stated United Stated · Santa Clara Completed: Apr 4, 2026 18:20 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

Cookie 'OptimizelyUserId' is missing the Secure flag

Security › Cookie Security
3

Cookie 'session' is missing the Secure flag

Security › Cookie Security
4

No Content-Security-Policy header found

Security › Content Security Policy
5

Page weighs 21.0 MB (11.3 MB transferred)

Performance › Page Weight Budget
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fashionnova.com)](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.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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

Detailed Report

Audit breakdown by category with detailed findings.

26

Performance

Insights

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.

RequestCache TTLTransfer Size
assets.bounceexchange.com/cache/2889/website-034989cbf75a0c1781360a7ed372e0b1.js120.0 s105.5 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/ui.js60.0 s93.3 KiB
cdn.optimizely.com/js/26979700476.js120.0 s90.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
creatives.attn.tv/fashionnova/Attentive_JUNE_JRS_efdfe758.jpg0.0 ms56.5 KiB
creatives.attn.tv/fashionnova/Proxima-Nova-Black_9ff65377.otf0.0 ms55.6 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/airgap.js60.0 s55.2 KiB
undgb.fashionnova.com/eat/core0.0 ms48.1 KiB
creatives.attn.tv/fashionnova/ProximaNova-Regular_5683b0c6.otf0.0 ms40.5 KiB
pixel.marqo-ep.ai/c/6091c430-20f8-49bb-bfd1-ea6585d80f65/p.min.js0.0 ms35.5 KiB
/signals/config/935181608215333?v=2.9.291&r=stable&domain...1200.0 s37.3 KiB
j.northbeam.io/vendor/nb-sp.min.js300.0 s32.9 KiB
creatives.attn.tv/fashionnova/Titling%20Gothic%20FB%20Wide%20Bold_6ff4e965.otf0.0 ms25.1 KiB
creatives.attn.tv/fashionnova/white_83bd7cb4.png0.0 ms18.9 KiB
/public/client_js/clientParamsHelper/clientParamsHelper.b...0.0 ms12.5 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
tag.wknd.ai/2889/i.js60.0 s8.4 KiB
www.datadoghq-browser-agent.com/datadog-logs.js14400.0 s12.1 KiB
cdn.attn.tv/growth-tag-assets/client-configs/Uwg.js120.0 s8.1 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/cm.css60.0 s4.2 KiB
static.klaviyo.com/onsite/js/klaviyo.js?company_id=XkHHQx1.0 s2.9 KiB
tags.creativecdn.com/eUCQernNGGvdlKl1D5sc.js3600.0 s2.7 KiB
cdn.attn.tv/fashionnova/dtag.js120.0 s2.1 KiB
undgb.fashionnova.com/fashionnova/load1200.0 s2.0 KiB
/state/js?website_id=2889&device_id=3332070333357392081&v...0.0 ms1.0 KiB
/sdks/pushowl-sdk.js?subdomain=fnova&environment=producti...3600.0 s1.2 KiB
/config/com/301bc76a-867d-419a-afb1-1ce91680f333.js?v=3.5...0.0 ms475 B
pix.cdnwidget.com/hash.gif?md5=none&sha1=none&sha256=none0.0 ms439 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=935181608215333&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/p.css?s=1&k=uce4gyt&ht=tk&f=137.169.173.175&a=142510884&...604800.0 s172 B

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:31.099 source:map[column:3232 line:0 type:source-location url:https://cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/index-8YyQ88Fz.js 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

URLResource SizeEst Savings
Phone Number or Email div.flex > div.order-2 > div > form.mt-3
creatives.attn.tv/fashionnova/white_83bd7cb4.png18.4 KiB17.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 KiB13.1 KiB
svg > defs > clippath#clip0_601_80690 > rect svg > defs > clippath#clip0_601_80690 > rect
creatives.attn.tv/fashionnova/Attentive_JUNE_JRS_efdfe758.jpg56.0 KiB6.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 KiB4.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.

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.

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.

TTI

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.

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.

Estimated savings: 300 ms 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.

URLTotal CPU TimeScript EvaluationScript Parse
cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/index-CeUCdvwZ.js3.6 s3.3 s1.6 ms
/oxygen-v2/29900/17398/35909/3301398/assets/entry.client-...3.2 s2.9 s1.0 ms
Unattributable3.2 s695 ms0.0 ms
www.fashionnova.com/1.4 s77 ms93 ms
www.googletagmanager.com/gtm.js?id=GTM-5R54C8M1.4 s1.2 s140 ms
www.googletagmanager.com/gtag/js?id=G-CHPZC04957&cx=c&gtm=4e6411684 ms622 ms56 ms
www.googletagmanager.com/gtag/js?id=AW-964745028604 ms551 ms45 ms
cdn.optimizely.com/js/26979700476.js571 ms541 ms28 ms
www.googletagmanager.com/gtag/js?id=AW-17897115191&cx=c&gtm=4e6411425 ms382 ms40 ms
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/ui.js391 ms266 ms124 ms
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js387 ms235 ms136 ms
connect.facebook.net/en_US/fbevents.js343 ms213 ms66 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js279 ms232 ms46 ms
/assets/smart-tag/versioned/main-v2_ca9cac840170c7a80240b...272 ms203 ms55 ms
undgb.fashionnova.com/eat/core256 ms201 ms21 ms
/state/js?website_id=2889&device_id=3332070333357392081&v...249 ms247 ms0.5 ms
scripts.clarity.ms/0.8.59/clarity.js241 ms228 ms8.3 ms
/onsite/js/build-preview/commit-f6f00cac0c842ff6b918911ae...227 ms213 ms6.5 ms
/signals/config/935181608215333?v=2.9.291&r=stable&domain...167 ms134 ms33 ms
sc-static.net/scevent.min.js158 ms138 ms16 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js145 ms122 ms19 ms
j.northbeam.io/vendor/nb-sp.min.js142 ms125 ms13 ms
www.googletagmanager.com/gtag/js?id=AW-964745028&cx=c&gtm=4e6411140 ms67 ms72 ms
cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/index-8YyQ88Fz.js129 ms1.1 ms0.4 ms
/assets/smart-tag/versioned/cjs_min_92abedfd1b9757a428bfc...123 ms105 ms10 ms
/assets/smart-tag/versioned/sms-v2_e39203556bab2366e56296...93 ms89 ms1.1 ms
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/airgap.js92 ms75 ms16 ms
/assets/smart-tag/versioned/wknd_audiences_2648fa8509e4b3...89 ms77 ms9.6 ms
/onsite/js/build-preview/commit-f6f00cac0c842ff6b918911ae...85 ms77 ms7.4 ms
assets.bounceexchange.com/assets/bounce/jquery-3.7.1.min.js85 ms52 ms30 ms
/onsite/js/build-preview/commit-f6f00cac0c842ff6b918911ae...83 ms73 ms8.8 ms
/onsite/js/build-preview/commit-f6f00cac0c842ff6b918911ae...72 ms66 ms4.7 ms
tags.creativecdn.com/eUCQernNGGvdlKl1D5sc.js62 ms59 ms1.1 ms
assets.bounceexchange.com/cache/2889/website-034989cbf75a0c1781360a7ed372e0b1.js60 ms19 ms40 ms
cdn.attn.tv/growth-tag-assets/client-configs/Uwg.js54 ms49 ms4.2 ms
cdn.shopify.com/shopifycloud/perf-kit/shopify-perf-kit-spa.min.js53 ms46 ms6.2 ms
j.northbeam.io/ota-sp/8196ff69-cc70-4c16-8a32-e00d4b1b285e.js50 ms35 ms13 ms

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

CategoryTime Spent
Script Evaluation14.5 s
Other3.2 s
Script Parsing & Compilation1.3 s
Style & Layout1.0 s
Garbage Collection452 ms
Parse HTML & CSS299 ms
Rendering192 ms

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 34 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 160 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 20 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
90

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.

Failing Elements
Get footer > div.fixed > div.relative > a.button-primary

These are opportunities to improve the legibility of your content.

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-hidden="true"]` is not present on the document `<body>`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` elements do not contain focusable descendents
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 are distinguishable without relying on color.
Document has a main landmark.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
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
Elements use only permitted ARIA attributes
`[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]`s are contained by their required parent element
`[role]` values are valid
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<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
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
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.
Uses ARIA roles only on compatible elements
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.
73

Best Practices

Trust and Safety

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.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
AttributionReporting

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

SourceDescription
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

53
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
69
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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

Detailed Report

Audit breakdown by category with detailed findings.

53

Performance

Insights

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.

RequestCache TTLTransfer Size
assets.bounceexchange.com/cache/2889/website-034989cbf75a0c1781360a7ed372e0b1.js120.0 s105.5 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/ui.js60.0 s93.4 KiB
cdn.optimizely.com/js/26979700476.js120.0 s90.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/airgap.js60.0 s55.3 KiB
undgb.fashionnova.com/eat/core0.0 ms48.1 KiB
pixel.marqo-ep.ai/c/6091c430-20f8-49bb-bfd1-ea6585d80f65/p.min.js0.0 ms35.5 KiB
/signals/config/935181608215333?v=2.9.291&r=stable&domain...1200.0 s37.3 KiB
j.northbeam.io/vendor/nb-sp.min.js300.0 s32.9 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/public/client_js/clientParamsHelper/clientParamsHelper.b...0.0 ms12.5 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
tag.wknd.ai/2889/i.js60.0 s8.4 KiB
cdn.attn.tv/growth-tag-assets/client-configs/Uwg.js120.0 s8.1 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/cm.css60.0 s4.2 KiB
static.klaviyo.com/onsite/js/klaviyo.js?company_id=XkHHQx1.0 s2.9 KiB
tags.creativecdn.com/eUCQernNGGvdlKl1D5sc.js3600.0 s2.7 KiB
cdn.attn.tv/fashionnova/dtag.js120.0 s2.1 KiB
undgb.fashionnova.com/fashionnova/load1200.0 s2.0 KiB
/state/js?website_id=2889&device_id=7277027461778984290&v...0.0 ms1.0 KiB
/sdks/pushowl-sdk.js?subdomain=fnova&environment=producti...3600.0 s1.2 KiB
/config/com/301bc76a-867d-419a-afb1-1ce91680f333.js?v=3.5...0.0 ms475 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/assets/uploads/clients/211/creatives/32a6af296611dc35808...604800.0 s1.4 KiB
pix.cdnwidget.com/hash.gif?md5=none&sha1=none&sha256=none0.0 ms88 B
/tr/?id=935181608215333&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/p.css?s=1&k=uce4gyt&ht=tk&f=137.169.173.175&a=142510884&...604800.0 s172 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B
/a?id=G-CHPZC04957&v=3&t=t&pid=958251743&gtm=45je6420h2v8...0.0 ms11 B

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:146.884 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.

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.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
DESERT HIGHWAY | 03.25.26 | JRS BANNER div.relative > a > div.relative > video.bg-neutral-100
/images/0v989dzu/production/9500d0875276d7b9b41ada0d6679f...114.7 KiB59.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 KiB5.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.

TTI

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.

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.

Estimated savings: 180 ms 1.1 MiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js362.6 KiB179.1 KiB
cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/root-CaL1mrvW.js157.5 KiB121.2 KiB
www.googletagmanager.com/gtag/js?id=AW-964745028&cx=c&gtm=4e6420h2144.0 KiB104.8 KiB
www.googletagmanager.com/gtag/destination?id=UA-45937828-1&cx=c&gtm=4e6420h2114.4 KiB63.0 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js109.1 KiB57.7 KiB
www.googletagmanager.com/gtag/js?id=G-CHPZC04957&cx=c&gtm=4e6420h2164.8 KiB56.7 KiB
/assets/smart-tag/versioned/main-v2_ca9cac840170c7a80240b...119.6 KiB54.9 KiB
www.googletagmanager.com/gtag/js?id=AW-964745028143.6 KiB54.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-5R54C8M186.6 KiB54.3 KiB
www.googletagmanager.com/gtag/js?id=AW-17897115191&cx=c&gtm=4e6420h2136.2 KiB52.2 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/ui.js93.0 KiB44.9 KiB
cdn.optimizely.com/js/26979700476.js89.9 KiB41.2 KiB
cdn.pushowl.com/latest/sdks/pushowl-sdk-main.js51.5 KiB36.1 KiB
connect.facebook.net/en_US/fbevents.js94.8 KiB33.0 KiB
cdn.shopify.com/oxygen-v2/29900/17398/35909/3301398/assets/CartMain-BKfEwzSr.js31.1 KiB30.0 KiB
undgb.fashionnova.com/eat/core48.0 KiB28.5 KiB
/oxygen-v2/29900/17398/35909/3301398/assets/UpdateLocatio...30.0 KiB27.4 KiB
transcend-cdn.com/cm/bb43296e-7ad2-48ef-8961-8ac1d2ed5b8c/airgap.js55.0 KiB25.0 KiB
/oxygen-v2/29900/17398/35909/3301398/assets/LocalizedLink...33.9 KiB23.6 KiB
pixel.marqo-ep.ai/c/6091c430-20f8-49bb-bfd1-ea6585d80f65/p.min.js35.3 KiB23.4 KiB

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

CategoryTime Spent
Script Evaluation3.9 s
Other966 ms
Style & Layout319 ms
Script Parsing & Compilation309 ms
Garbage Collection117 ms
Rendering98 ms
Parse HTML & CSS58 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.

Estimated savings: 0.0 ms 22.3 KiB

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 36 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 160 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 10 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
96

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.

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.

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
`[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
`[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
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.
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
The page contains a heading, skip link, or landmark region
Elements with visible text labels have matching accessible names.
`[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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[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
`<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
Heading elements appear in a sequentially-descending order
`<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
Form elements have associated labels
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
69

Best Practices

Trust and Safety

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.

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect 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)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
AttributionReporting

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

SourceDescription
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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`

Send Feedback