Mobile 375 × 812

Desktop 1440 × 900

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.
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.
Cookie 'nfvdid' is missing the Secure flag
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.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
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/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.comThis badge auto-updates with your latest scan result.
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.
7 barrier(s) likely increasing bounce by ~29%.
Page takes 8.5s to load
+12% bounceUsers 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% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
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
Layout shifts during page load
+3% bounceContent 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% bounceVisitors 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
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, …)
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.
$450 investment → $6,370/month returns + USD 150,000 risk avoided
$450
4h · 5 findings
$6,370 /mo
~$76,438 / year
USD 150,000
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.
4.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$12,501 / month at risk
~$150,010 / year if left unfixed
$150,000
$0.84 /mo
10548.5 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.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
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.
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.
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.
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.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 KiB | 28.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 KiB | 16.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 KiB | 15.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 KiB | 13.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 KiB | 11.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 KiB | 10.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 KiB | 7.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 KiB | 6.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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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 |
|---|---|---|
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 8.9 KiB | 753 ms |
| /web/ffe/wp/@nf-web-ui/ui-shared/dist/less/signup/nmhp/nm... | 1.7 KiB | 754 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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 |
|---|---|
| netflix.com/ | 1.3 s |
| www.netflix.com/ | 1.1 s |
| www.netflix.com/br-en/ | 0.0 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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout 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 |
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc2... | 2.9 s | 2.2 s | 486 ms |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 2.1 s | 1.6 s | 454 ms |
| www.netflix.com/br-en/ | 1.8 s | 24 ms | 64 ms |
| Unattributable | 832 ms | 96 ms | 0.0 ms |
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 395 ms | 231 ms | 87 ms |
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 66 ms | 54 ms | 4.0 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 4.3 s |
| Other | 1.3 s |
| Script Parsing & Compilation | 1.1 s |
| Style & Layout | 882 ms |
| Rendering | 408 ms |
| Garbage Collection | 155 ms |
| Parse HTML & CSS | 155 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 |
|---|---|
| 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.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 244.4 KiB |
| /web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc2... | 707.8 KiB | 222.9 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 177.2 KiB |
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 128.7 KiB | 68.7 KiB |
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.
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.
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 |
|---|
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| help.netflix.com/legal/privacy#cookies | here |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.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
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.
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.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 KiB | 154.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 KiB | 16.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 KiB | 15.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 KiB | 13.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 KiB | 11.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 KiB | 10.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 KiB | 7.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 KiB | 6.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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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 |
|---|---|---|
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 8.9 KiB | 234 ms |
| /web/ffe/wp/@nf-web-ui/ui-shared/dist/less/signup/nmhp/nm... | 1.7 KiB | 202 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2 | 10 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 |
|---|---|
| netflix.com/ | 580 ms |
| www.netflix.com/ | 575 ms |
| www.netflix.com/br-en/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout 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.
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.
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 reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc2... | 727 ms | 532 ms | 120 ms |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 576 ms | 456 ms | 106 ms |
| www.netflix.com/br-en/ | 562 ms | 6.5 ms | 24 ms |
| Unattributable | 193 ms | 22 ms | 0.0 ms |
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 145 ms | 88 ms | 17 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.1 s |
| Other | 405 ms |
| Script Parsing & Compilation | 270 ms |
| Style & Layout | 240 ms |
| Rendering | 105 ms |
| Parse HTML & CSS | 49 ms |
| Garbage Collection | 39 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 |
|---|---|
| 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.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 244.4 KiB |
| /web/ffe/wp/ui/landingPages/nmhp/nmhpFrameworkClient.fcc2... | 707.8 KiB | 222.9 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 176.1 KiB |
| /helpcenter/OneTrust/oneTrust_production_2026-03-26/scrip... | 128.7 KiB | 68.7 KiB |
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.
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.
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 |
|---|
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| help.netflix.com/legal/privacy#cookies | here |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback