Skip to content
https://wayfair.com

Lighthouse Desktop

· 0 checks — Desktop 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.

47

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Greetings from the outdoor shop. Sunnier days are here, and so are our staycati… div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/51079089/resize-h566-w2000^compr-r85/4186/418678979/g...236.3 KiB152.4 KiB
Wayfair Rewards members-only unbeatable savings on kitchen staples, plus 5% in … div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/60408892/resize-h566-w2000^compr-r85/3939/393937914/w...184.7 KiB100.8 KiB
Picks from $20, the spring-cleaning shop, reset for the season with a tidy and … div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/60342398/resize-h566-w2000^compr-r85/4224/422406965/p...161.4 KiB87.9 KiB
Mikhajlo Faux Leather Upholstered Bench div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/39658502/resize-h400-w400^compr-r85/2586/258617499/Mi...27.6 KiB24.4 KiB
Presly 3 Tier Cube Bookcase Modern Bookshelf with 10 Cubes div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/84688877/resize-h400-w400^compr-r85/3402/340203912/Pr...27.3 KiB24.2 KiB
April 25-27, Way Day, the best deals in home are coming, shop early. div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/29056180/resize-h566-w2000^compr-r85/4293/429300507/a...41.3 KiB22.5 KiB
Wayfair Sleep Standard Queen Size Polyester Plush Pillow div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/35407058/resize-h400-w400^compr-r85/4002/400262043/Wa...25.3 KiB22.2 KiB
Chessani 45.7'' Sideboard div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/58708951/resize-h400-w400^compr-r85/2833/283385047/Ch...24.7 KiB21.6 KiB
Huntsville Full Storage Bed with 4 Drawers Velvet Upholstered Headboard White P… div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/06416902/resize-h400-w400^compr-r85/3918/391823373/Hu...22.6 KiB19.8 KiB
Centerport Wall Light div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/48734095/resize-h400-w400^compr-r85/2768/276830428/Ce...20.1 KiB17.7 KiB
Bathesda Iron Semi Flush Mount div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/33258896/resize-h400-w400^compr-r85/2318/231875618/Ba...19.5 KiB17.1 KiB
Lora Mid-Century Modern Tufted Leather Bench, 44" Wide with Metal Legs div._6o3atz14b > div._6o3atz1bf > div._6o3atz14b > img.b32ygh0
/im/46605321/resize-h400-w400^compr-r85/2339/233917182/Lo...17.7 KiB15.5 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.

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

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 241 ms
URLTime Spent
wayfair.com/241 ms
www.wayfair.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 400 ms 2.0 MiB
URLTransfer SizeEst Savings
/webpack/sf-ui-core-funnel/_next/static/chunks/9297-97682...508.8 KiB478.9 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/app/(stand...361.2 KiB336.8 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/app/layout...298.5 KiB285.8 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/app/(stand...339.8 KiB234.0 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/app/(stand...310.6 KiB90.6 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/103-9791d6...111.2 KiB76.7 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/d778532c-5...58.6 KiB58.5 KiB
prx.wayfair.com/px/client/main.min.js128.9 KiB56.6 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/acc06427.e...112.1 KiB56.1 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/318-28ec0e...49.6 KiB46.6 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/9990-c79fb...62.1 KiB45.7 KiB
cdn.quantummetric.com/qscripts/quantum-wayfair.js114.6 KiB43.9 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/8baf20c0-d...36.1 KiB36.1 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/3069.445a6...31.2 KiB30.5 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e...66.5 KiB30.5 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/8794-b7f96...28.9 KiB25.4 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/5705-81cbd...39.4 KiB24.2 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/9661-4cc3e...28.5 KiB23.6 KiB
cdn02.taggstar.com/libs/jquery_v3.7.1.min.js30.0 KiB22.8 KiB
/webpack/sf-ui-core-funnel/_next/static/chunks/7677-53bf1...26.8 KiB21.1 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.

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 Evaluation2.8 s
Other1.0 s
Script Parsing & Compilation440 ms
Garbage Collection187 ms
Style & Layout164 ms
Rendering70 ms
Parse HTML & CSS46 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
April 25-27, Way Day, the best deals in home are coming, shop early. div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/29056180/resize-h566-w2000^compr-r85/4293/429300507/a...
Greetings from the outdoor shop. Sunnier days are here, and so are our staycati… div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/51079089/resize-h566-w2000^compr-r85/4186/418678979/g...
Picks from $20, the spring-cleaning shop, reset for the season with a tidy and … div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/60342398/resize-h566-w2000^compr-r85/4224/422406965/p...
Wayfair Rewards members-only unbeatable savings on kitchen staples, plus 5% in … div._6o3atz14b > div.l7xeeh4 > picture._6o3atz14b > img.gyz45k1
/im/60408892/resize-h566-w2000^compr-r85/3939/393937914/w...

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 11 long tasks found
●Avoid non-composited animations 4 animated elements found
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 580 ms
○INP breakdown
○User Timing marks and measures
○Avoid large layout shifts
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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Sale Furniture Outdoor Bedding & Bath Decor & Pillows Rugs Lighting Home Improv… div > div > span.mtsvz50 > ul

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.od63pv1 > div > h2._6o3atz12h > button._1pmvkjd1 a.od63pv1 > div > h2._6o3atz12h > button._1pmvkjd1

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.hb-theme-wayfair html.hb-theme-wayfair

These items highlight common accessibility best practices.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sale div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
Deals of the Day div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
Sale div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
Bundle and Save div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
Deals of the Day div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
Deals of the Day div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
30-Day Low Price div._6o3atz13e > div._6o3atz14b > div._6o3atzad > a._1d0yv060
○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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 use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
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
Access to CSS stylesheet at 'https://cdn02.taggstar.com/customers/wayfaircom/taggstar-v1.min.css' from origin 'https://www.wayfair.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
ApolloError: Response not successful: Received status code 429 at new t (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:88866) at https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:56744 at o (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:35861) at https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:35776 at new Promise (<anonymous>) at Object.then (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:35743) at Object.error (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:35871) at g (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:230400) at b (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:230901) at t.error (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/1010-4498e4af569120b6.js:1:231454)
Error: {"appId":"PX3Vk96I6i","jsClientSrc":"/3Vk96I6i/init.js","customLogo":"","firstPartyEnabled":true,"vid":"f07297ea-3de5-11f1-b2a0-e52ec795790a","uuid":"f0578a30-3de5-11f1-a6c3-5569f023238c","hostUrl":"/3Vk96I6i/xhr","blockScript":"/3Vk96I6i/captcha/captcha.js?a=c&u=f0578a30-3de5-11f1-a6c3-5569f023238c&v=f07297ea-3de5-11f1-b2a0-e52ec795790a&m=0&b=aHR0cHM6Ly93d3cud2F5ZmFpci5jb20vYS9jb3JlX2Z1bm5lbC9jb3JlX2Z1bm5lbF9kYXRhL3JlcGxhdGZvcm1lZF9mb290ZXI=&h=R0VU","altBlockScript":"https://captcha.px-cloud.net/PX3Vk96I6i/captcha.js?a=c&u=f0578a30-3de5-11f1-a6c3-5569f023238c&v=f07297ea-3de5-11f1-b2a0-e52ec795790a&m=0&b=aHR0cHM6Ly93d3cud2F5ZmFpci5jb20vYS9jb3JlX2Z1bm5lbC9jb3JlX2Z1bm5lbF9kYXRhL3JlcGxhdGZvcm1lZF9mb290ZXI=&h=R0VU"} at https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/417-fa0a6016a627ceee.js:1:30479 at async r (https://assets.wfcdn.com/webpack/sf-ui-core-funnel/_next/static/chunks/app/(standard)/layout-261916759edd4946.js:1:13477)
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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