Skip to content
Audit Complete

Results for https://netflix.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 16, 2026 16:57 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

Room to improve — your 8.5s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

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.

How the composite score is calculated

How you compare

Amazon Route 53 sites average 72
At average
Better than 47% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple sites average 73
At average
Better than 36% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

Cookie 'nfvdid' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fnetflix.com)](https://beavercheck.com/results/f61c5436-5f78-40f5-9f23-e65d2bd3466c)
<a href="https://beavercheck.com/results/f61c5436-5f78-40f5-9f23-e65d2bd3466c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnetflix.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnetflix.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 8.5s to load

+12% bounce

Users abandon at ~3s — you're 6.0s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.6s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (1)

No structured data

+2% bounce

No 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, …)

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard 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.

Return on Investment

$450 investment → $6,370/month returns + USD 150,000 risk avoided

Payback period: < 1 month First-year ROI: +16886%

Investment

$450

4h · 5 findings

Monthly returns

$6,370 /mo

~$76,438 / year

  • Conversions recovered $6,369
  • Bandwidth savings $0.84

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

Payback period

0 12mo 24mo

$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.

Full methodology & sources

Estimated Remediation Cost

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,501 / month at risk

~$150,010 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000
  • Heading level skipped: H1 → H3 (missing H2)
    ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.84 /mo

10548.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves $0.84/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

21
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
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.

4.96 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.46 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.57 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.226

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.31 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.

26.15 s

Detailed Report

Audit breakdown by category with detailed findings.

21

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.22649] map[node:map[boundingRect:map[bottom:564 height:564 left:-758 right:1170 top:0 width:1928] lhId:page-8-DIV nodeLabel:div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV selector:div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu snippet:<div dir="ltr" class="default-ltr-iqcdef-cache-bg95xu e1j9j09b0"> type:node] score:0.22649]]

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:30.901 source:map[column:527205 line:121 type:source-location url:https://assets.nflxext.com/web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc229dc9c54f05b4357.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:78.375 source:map[type:text value:[unattributed]]] map[reflowTime:16.936 source:map[column:774737 line:120 type:source-location url:https://assets.nflxext.com/web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc229dc9c54f05b4357.js urlProvider:network]] map[reflowTime:11.583 source:map[column:675611 line:0 type:source-location url:https://assets.nflxext.com/web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc229dc9c54f05b4357.js urlProvider:network]] map[reflowTime:1.755 source:map[column:675909 line:0 type:source-location url:https://assets.nflxext.com/web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc229dc9c54f05b4357.js urlProvider:network]] map[reflowTime:0.627 source:map[column:2.023281e+06 line:0 type:source-location url:https://assets.nflxext.com/web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc229dc9c54f05b4357.js urlProvider:network]] map[reflowTime:0.957 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.387 source:map[column:170629 line:6 type:source-location url:https://help.nflxext.com/helpcenter/OneTrust/oneTrust_production_2026-03-26/scripttemplates/202602.1.0/otBannerSdk.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45952b2/web...156.7 KiB28.8 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABURoPsYCXbsu2...25.3 KiB16.5 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABSkC5iPPgRiOp...24.4 KiB15.5 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABXKKmczFuU20u...22.3 KiB13.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABYEpB1yOguPpi...20.3 KiB11.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABWrJSjnwiNecJ...18.8 KiB10.0 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABdDl3grDRIiZb...16.3 KiB7.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABdzBq9maVugeY...14.8 KiB6.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,1,IMG
selector: div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
snippet: <img src="https://assets.nflxext.com/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45…" srcset="https://assets.nflxext.com/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45…" alt="" aria-hidden="true" class="default-ltr-iqcdef-cache-19j6xtr">

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.

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
value: no origins were preconnected
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
value: No additional origins are good candidates for preconnecting

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.

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.

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.

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: 2.5 s

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu
0.226

Diagnostics

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 Evaluation4.3 s
Other1.3 s
Script Parsing & Compilation1.1 s
Style & Layout882 ms
Rendering408 ms
Garbage Collection155 ms
Parse HTML & CSS155 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.

Estimated savings: 0.0 ms 20.3 KiB
URLTransfer SizeEst Savings
23.1 KiB20.3 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

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

Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 4 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 10 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 130 ms
Server Backend Latencies 220 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 550 ms
INP breakdown
94

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.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ready to watch? Enter your email to create or restart your membership. div.default-ltr-iqcdef-cache-1josprq > div.default-ltr-iqcdef-cache-noi56b > form.default-ltr-iqcdef-cache-14nc2q6 > h3.default-ltr-iqcdef-cache-18zqjlh

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
Form elements have associated labels
Select elements have associated label elements.
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
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 are distinguishable without relying on color.
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.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
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
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
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.
`<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.
100

Best Practices

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 browser errors logged to the console
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
91

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
help.netflix.com/legal/privacy#cookieshere

Format your HTML in a way that enables crawlers to better understand your app’s content.

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 are crawlable
robots.txt is valid
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

43
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
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.92 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.81 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

393 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.243

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.44 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.

6.37 s

Detailed Report

Audit breakdown by category with detailed findings.

43

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.24250899999999997] map[node:map[boundingRect:map[bottom:788 height:788 left:-289 right:1639 top:0 width:1928] lhId:page-8-DIV nodeLabel:div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV selector:div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu snippet:<div dir="ltr" class="default-ltr-iqcdef-cache-bg95xu e1j9j09b0"> type:node] score:0.238449] map[node:map[boundingRect:map[bottom:567 height:309 left:381 right:969 top:258 width:588] lhId:page-14-DIV nodeLabel:Unlimited movies, TV shows, and more Starts at BRL 20.90. Cancel anytime. Rea… path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,0,DIV selector:div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-15fecvd > div.default-ltr-iqcdef-cache-2lmy8v > div.default-ltr-iqcdef-cache-slza4h snippet:<div class="default-ltr-iqcdef-cache-slza4h"> type:node] score:0.003517] map[node:map[boundingRect:map[bottom:398 height:140 left:381 right:969 top:258 width:588] lhId:page-10-H1 nodeLabel:Unlimited movies, TV shows, and more path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,H1 selector:div.default-ltr-iqcdef-cache-2lmy8v > div.default-ltr-iqcdef-cache-slza4h > div > h1.default-ltr-iqcdef-cache-1klkeed snippet:<h1 class="default-ltr-iqcdef-cache-1klkeed e1cwop5t0"> type:node] score:0.000543]]

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:83.629 source:map[type:text value:[unattributed]]]]

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
div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45952b2/web...382.2 KiB154.0 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABURoPsYCXbsu2...25.3 KiB16.5 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABSkC5iPPgRiOp...24.4 KiB15.5 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABXKKmczFuU20u...22.3 KiB13.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABYEpB1yOguPpi...20.3 KiB11.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABWrJSjnwiNecJ...18.8 KiB10.0 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABdDl3grDRIiZb...16.3 KiB7.4 KiB
li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5 li.default-ltr-iqcdef-cache-uvpx8v > button.default-ltr-iqcdef-cache-1it3med > div.default-ltr-iqcdef-cache-3xjlkv > span.default-ltr-iqcdef-cache-cf8xw5
/dnm/api/v6/mAcAr9TxZIVbINe88xb3Teg5_OA/AAAABdzBq9maVugeY...14.8 KiB6.0 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,1,IMG
selector: div.default-ltr-iqcdef-cache-1tlz4mq > div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-t1swus > img.default-ltr-iqcdef-cache-19j6xtr
snippet: <img src="https://assets.nflxext.com/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45…" srcset="https://assets.nflxext.com/ffe/siteui/vlv3/5bd3572a-0d1b-4228-aaa7-5b2dc45…" alt="" aria-hidden="true" class="default-ltr-iqcdef-cache-19j6xtr">

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.

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
value: no origins were preconnected
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
value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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: 1.2 s

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 580 ms
URLTime Spent
www.netflix.com/br-en/680 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu div.default-ltr-iqcdef-cache-pw7jst > div.default-ltr-iqcdef-cache-8ylunr > div.default-ltr-iqcdef-cache-1i8lfih > div.default-ltr-iqcdef-cache-bg95xu
0.238
Unlimited movies, TV shows, and more Starts at BRL 20.90. Cancel anytime. Rea… div.default-ltr-iqcdef-cache-73ljnh > div.default-ltr-iqcdef-cache-15fecvd > div.default-ltr-iqcdef-cache-2lmy8v > div.default-ltr-iqcdef-cache-slza4h
0.004
Unlimited movies, TV shows, and more div.default-ltr-iqcdef-cache-2lmy8v > div.default-ltr-iqcdef-cache-slza4h > div > h1.default-ltr-iqcdef-cache-1klkeed
0.001

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.

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

Diagnostics

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 Evaluation1.1 s
Other405 ms
Script Parsing & Compilation270 ms
Style & Layout240 ms
Rendering105 ms
Parse HTML & CSS49 ms
Garbage Collection39 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.

Estimated savings: 0.0 ms 20.2 KiB
URLTransfer SizeEst Savings
23.1 KiB20.2 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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

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

Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 4 user timings
Avoid long main-thread tasks 7 long tasks found
Avoid non-composited animations 10 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 160 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
INP breakdown
94

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.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ready to watch? Enter your email to create or restart your membership. div.default-ltr-iqcdef-cache-1josprq > div.default-ltr-iqcdef-cache-noi56b > form.default-ltr-iqcdef-cache-14nc2q6 > h3.default-ltr-iqcdef-cache-18zqjlh

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
Form elements have associated labels
Select elements have associated label elements.
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
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 are distinguishable without relying on color.
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.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
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
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
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.
`<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.
100

Best Practices

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 browser errors logged to the console
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
91

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
help.netflix.com/legal/privacy#cookieshere

Format your HTML in a way that enables crawlers to better understand your app’s content.

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 are crawlable
robots.txt is valid
Document has a valid `hreflang`
Image elements have `[alt]` attributes
Document has a valid `rel=canonical`

Send Feedback