United Stated · New York Completed: Apr 16, 2026 18:08 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 67 / 100
Based on 8 categories, 0 sections
Room to improve — your 18.2s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
Heavier than average — reducing page weight saves energy and bandwidth.
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
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 20.6 MB (6.3 MB transferred)
Performance issues directly impact user engagement and conversion rates.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/7683e9f0-c6e2-4819-8b03-1d2a834ba302)<a href="https://beavercheck.com/results/7683e9f0-c6e2-4819-8b03-1d2a834ba302"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fzillow.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fzillow.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 18.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~30%.
Page takes 18.2s to load
+12% bounceUsers abandon at ~3s — you're 15.7s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 8.8s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$500 investment → $1.57/month returns + USD 157,500 risk avoided
$500
5h · 5 findings
$1.57 /mo
~$19 / year
USD 157,500
if kept compliant
$150 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,127 / month at risk
~$157,519 / year if left unfixed
$157,500
+6 more
$1.57 /mo
19680.1 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
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.
4.95 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
18.17 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
8.76 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
13.57 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.
45.28 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div > div > picture > img.StyledBox-c11n-8-111-2__sc-ocjv7k-0 div > div > picture > img.StyledBox-c11n-8-111-2__sc-ocjv7k-0 | www.zillowstatic.com/bedrock/app/uploads/sites/5/2024/07/image2-m%402x.jpg | 242.9 KiB | 168.5 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| fonts.googleapis.com/css?family=Open+Sans:400,600,700&display=swap | 2.2 KiB | 776 ms |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| zillow.com/ | 765 ms |
| www.zillow.com/ | 0.0 ms |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
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.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 16.2 s |
| Style & Layout | 2.9 s |
| Other | 2.6 s |
| Script Parsing & Compilation | 2.2 s |
| Garbage Collection | 440 ms |
| Rendering | 234 ms |
| Parse HTML & CSS | 142 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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
Performance issues directly impact user engagement and conversion rates.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.exclude-from-algorithmic-darkening, > iframe#px-captcha-modal body.exclude-from-algorithmic-darkening, > iframe#px-captcha-modal |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Get home recommendations div.Flex-c11n-8-111-2__sc-n94bjd-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > h5.Text-c11n-8-111-2__sc-aiai24-0 |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
§ 442-H New York Standard Operating Procedures div.pfs__wsq7ni-0 > div.pfs__sc-1sj5qgb-0 > p.Text-c11n-8-112-0__sc-aiai24-0 > a.Anchor-c11n-8-112-0__sc-hn4bge-0 |
§ New York Fair Housing Notice div.pfs__wsq7ni-0 > div.pfs__sc-1sj5qgb-0 > p.Text-c11n-8-112-0__sc-aiai24-0 > a.Anchor-c11n-8-112-0__sc-hn4bge-0 |
These items highlight common accessibility best practices.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > picture > img div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > picture > img | /s3/web-platform/sub-apps/hops-homepage/hops-homepage.pro... | 320 x 248 | 355 x 275 | 480 x 372 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | /s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 393 |
| Unload event listeners are deprecated and will be removed. | /HYx10rg3/captcha/captcha.js?a=c&u=17e841f0-39bf-11f1-83e... line 1, col 206600 |
| Topics | /s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 393 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
/s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 176 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
/s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 176 | FetchFeatureFlagFailed: Failed to fetch feature flag. Using default "off" value for graceful degradation. This typically indicates a network issue or misconfigured feature flag.
at Object.FetchFeatureFlagValueFailed (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/663.e0033107.bundle.js:1:26095)
at https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/663.e0033107.bundle.js:1:40677
at https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:570445
at Generator.<anonymous> (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:567837)
at Generator.next (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:566616)
at t (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:563242)
at b (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:563445) |
Not signed in with the identity provider. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
853 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.69 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.13 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.39 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.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div > div > picture > img.StyledBox-c11n-8-111-2__sc-ocjv7k-0 div > div > picture > img.StyledBox-c11n-8-111-2__sc-ocjv7k-0 | www.zillowstatic.com/bedrock/app/uploads/sites/5/2024/07/image2-xl%401x.jpg | 186.6 KiB | 80.0 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| fonts.googleapis.com/css?family=Open+Sans:400,600,700&display=swap | 2.2 KiB | 230 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| zillow.com/ | 216 ms |
| www.zillow.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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
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.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 4.7 s |
| Style & Layout | 990 ms |
| Other | 933 ms |
| Script Parsing & Compilation | 577 ms |
| Garbage Collection | 196 ms |
| Rendering | 62 ms |
| Parse HTML & CSS | 36 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in a sub frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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
Performance issues directly impact user engagement and conversion rates.
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.exclude-from-algorithmic-darkening, > iframe#px-captcha-modal body.exclude-from-algorithmic-darkening, > iframe#px-captcha-modal |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Get home recommendations div.Flex-c11n-8-111-2__sc-n94bjd-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > h5.Text-c11n-8-111-2__sc-aiai24-0 |
About Zillow's Recommendations div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.Flex-c11n-8-111-2__sc-n94bjd-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > h6.Text-c11n-8-111-2__sc-aiai24-0 |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Sign in div.pfs__sc-1ve4drk-0 > ul.pfs__sc-1elvxkv-1 > li.pfs__sc-585qe5-0 > a.Anchor-c11n-8-112-0__sc-hn4bge-0 |
§ 442-H New York Standard Operating Procedures div.pfs__wsq7ni-0 > div.pfs__sc-1sj5qgb-0 > p.Text-c11n-8-112-0__sc-aiai24-0 > a.Anchor-c11n-8-112-0__sc-hn4bge-0 |
§ New York Fair Housing Notice div.pfs__wsq7ni-0 > div.pfs__sc-1sj5qgb-0 > p.Text-c11n-8-112-0__sc-aiai24-0 > a.Anchor-c11n-8-112-0__sc-hn4bge-0 |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > picture > img div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > div.StyledBox-c11n-8-111-2__sc-ocjv7k-0 > picture > img | /s3/web-platform/sub-apps/hops-homepage/hops-homepage.pro... | 464 x 360 (1.29) | 513 x 416 (1.23) |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | /s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 393 |
| Unload event listeners are deprecated and will be removed. | /HYx10rg3/captcha/captcha.js?a=c&u=2aa68950-39bf-11f1-8f7... line 1, col 206600 |
| Topics | /s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 393 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
/s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 176 | [GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token. |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
/s3/shopper-platform/_next/static/chunks/pages/_app-74514... line 13, col 176 | FetchFeatureFlagFailed: Failed to fetch feature flag. Using default "off" value for graceful degradation. This typically indicates a network issue or misconfigured feature flag.
at Object.FetchFeatureFlagValueFailed (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/663.e0033107.bundle.js:1:26095)
at https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/663.e0033107.bundle.js:1:40677
at https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:570445
at Generator.<anonymous> (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:567837)
at Generator.next (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:566616)
at t (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:563242)
at b (https://www.zillowstatic.com/s3/web-platform/sub-apps/buyability-sub-app/buyability-sub-app.prod.main.13920130.3ecd049b/web/33.4cbf4102.bundle.js:200:563445) |
Not signed in with the identity provider. |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 div.StyledPropertyCardPhotoWrapper-c11n-8-111-2__sc-1gbptz1-0 > div.StyledPropertyCardPhotoBody-c11n-8-111-2__sc-yln73l-0 > div.StyledPropertyCardPhoto-c11n-8-111-2__sc-radyfj-0 > img.Image-c11n-8-111-2__sc-1rtmhsc-0 |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback