C — https://plex.tv | BeaverCheck Audit

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

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.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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

Google Search Console · 3543 peers

You 77

Avg 73

At average

0 50 100

Better than 83% of Google Search Console sites See full Google Search Console benchmark →

Google Workspace · 1660 peers

You 77

Avg 73

At average

0 50 100

Better than 78% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

24 button(s) with no accessible text

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

Accessibility › Link & Button Quality

218 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

225 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fplex.tv)](https://beavercheck.com/results/37ba41c1-c645-4dc3-bf1b-0168f848df2c)

HTML

<a href="https://beavercheck.com/results/37ba41c1-c645-4dc3-bf1b-0168f848df2c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fplex.tv" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fplex.tv

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. The 2 performance issues below shape how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

2 performance issues — Akamai's research found 53% of mobile users abandon pages over 3s.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 3 warning

4 barrier(s) likely increasing bounce by ~13%.

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

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

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

159 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

CHF 845 investment → CHF 0.63/month returns + CHF 250,000 risk avoided

Payback period: > 2 years First-year ROI: -99%

Investment

CHF 845

6h · 5 findings

Monthly returns

CHF 0.63 /mo

~CHF 7.50 / year

Bandwidth savings CHF 0.63

Regulatory risk avoided

CHF 250,000

if kept compliant

nDSG/FADP CHF 250,000

CHF 130 — 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

CHF845

6.5 developer hours at CHF130/hr

Based on Switzerland rates (CHF130/hr)

Quick wins

CHF130 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

CHF /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

CHF 20,834 / month at risk

~CHF 250,008 / year if left unfixed

Compliance Risk

CHF 250,000

nDSG/FADP

No privacy policy link detected
nDSG/FADP: CHF 1,000 – CHF 250,000
Trackers detected but no cookie policy found
nDSG/FADP: CHF 1,000 – CHF 250,000
Trackers detected but no privacy policy found
nDSG/FADP: CHF 1,000 – CHF 250,000

+1 more

Bandwidth Waste

CHF 0.63 /mo

8828.6 MB/mo × 0.071 CHF/GB

Optimize transfer: save ~883 KB per page load
Saves CHF 0.63/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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.11 s

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

0 ms

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

0 ms

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

0.005

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

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

—

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.

Request	Cache TTL	Transfer Size
www.gstatic.com/eureka/clank/147/cast_sender.js	86400.0 s	13.4 KiB
js.sentry-cdn.com/eb76eae607a34d13b8a50419d1ffaee2.min.js	3600.0 s	2.6 KiB

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:107.072 source:map[column:7483 line:1 type:source-location url:https://watch.plex.tv/_next/static/chunks/0b5~.n6cv._dk.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:59.758 source:map[column:9878 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/07tl3rotd2mc_.js urlProvider:network]] map[reflowTime:47.314 source:map[column:10359 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/07tl3rotd2mc_.js urlProvider:network]] map[reflowTime:0.837 source:map[column:11432 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/0-mdppugogl1w.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.

	URL	Resource Size	Est Savings
main._13usayk0 > div.MaxLineWidthContainer-module__MEYx5G__container > div.page-module__26JAeW__background > img `main._13usayk0 > div.MaxLineWidthContainer-module__MEYx5G__container > div.page-module__26JAeW__background > img`	/photo?size=medium-240&scale=2&url=https%3A%2F%2Fwatch.pl...	40.0 KiB	36.8 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	24.4 KiB	10.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	23.4 KiB	9.3 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	22.4 KiB	8.3 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.8 KiB	7.9 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	21.1 KiB	7.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	21.1 KiB	7.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.8 KiB	6.7 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.7 KiB	6.6 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	20.6 KiB	6.6 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.5 KiB	6.5 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	19.7 KiB	5.7 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.5 KiB	5.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.5 KiB	5.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.1 KiB	5.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.1 KiB	5.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	18.7 KiB	4.6 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	18.6 KiB	4.5 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	18.5 KiB	4.4 KiB

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.

URL	Transfer Size
watch.plex.tv/_next/static/chunks/0y0u9y4h7ec3t.css	216 B
watch.plex.tv/_next/static/chunks/01r1fw9y.oasj.css	528 B
watch.plex.tv/_next/static/chunks/0fya108mn-sir.css	685 B
watch.plex.tv/_next/static/chunks/0ty1ncwpdrp68.css	721 B
watch.plex.tv/_next/static/chunks/0xakpy8jbfiyn.css	1.2 KiB
watch.plex.tv/_next/static/chunks/1517q4obivnz0.css	524 B
watch.plex.tv/_next/static/chunks/0smbf3wsvab5-.css	1.6 KiB
watch.plex.tv/_next/static/chunks/0iz3arwp4-m7n.css	1.8 KiB
watch.plex.tv/_next/static/chunks/00k00y0dfv9xe.css	355 B
watch.plex.tv/_next/static/chunks/0jrje-s--t2xv.css	303 B
watch.plex.tv/_next/static/chunks/0..mrf23c8lfz.css	2.5 KiB
watch.plex.tv/_next/static/chunks/0m..dgct052k0.css	470 B
watch.plex.tv/_next/static/chunks/00gxicr.n7dn0.css	955 B
watch.plex.tv/_next/static/chunks/185~rrs-dkfl2.css	1.0 KiB
watch.plex.tv/_next/static/chunks/14eg832tukr4i.css	1.2 KiB
watch.plex.tv/_next/static/chunks/00-tk-_mu0flt.css	1.4 KiB
watch.plex.tv/_next/static/chunks/0rbz9ubwqck0v.css	535 B
watch.plex.tv/_next/static/chunks/0b53._4vz-2.f.css	1.2 KiB
watch.plex.tv/_next/static/chunks/0v-jh6izbz_hb.css	344 B
watch.plex.tv/_next/static/chunks/0is~zce6~7v8o.css	1.4 KiB
watch.plex.tv/_next/static/chunks/04762~geobdbl.css	863 B
watch.plex.tv/_next/static/chunks/0jrr_mb8e-7pe.css	3.4 KiB
watch.plex.tv/_next/static/chunks/0z649sqx-ph0p.css	1.0 KiB
watch.plex.tv/_next/static/chunks/0i7ish49n248j.css	290 B
watch.plex.tv/_next/static/chunks/087tpnh8o_d5m.css	314 B
watch.plex.tv/_next/static/chunks/0hhd.tds38i2h.css	356 B
watch.plex.tv/_next/static/chunks/01s3q8j-8a9e3.css	4.2 KiB
watch.plex.tv/_next/static/chunks/0382mkbw46c1y.css	375 B
watch.plex.tv/_next/static/chunks/0o5pd79qgcp7p.css	1.0 KiB
watch.plex.tv/_next/static/chunks/0jc~gquh69su7.css	1.4 KiB
watch.plex.tv/_next/static/chunks/0tbl1g0n0h.d-.css	4.1 KiB
watch.plex.tv/_next/static/chunks/0y9v7rihnr7s~.css	1.1 KiB
watch.plex.tv/_next/static/chunks/0~6a.l-l-vg19.css	391 B
watch.plex.tv/_next/static/chunks/0c1boempfpe~0.css	3.5 KiB
watch.plex.tv/_next/static/chunks/0-0799m-p~90-.css	422 B

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

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.

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
watch.plex.tv/_next/static/chunks/12~bx1mtphe1a.js	124.4 KiB
watch.plex.tv/	115.1 KiB
watch.plex.tv/_next/static/chunks/03v8rkma_-~tx.js	113.4 KiB
accounts.google.com/gsi/client	96.4 KiB
watch.plex.tv/_next/static/chunks/0.9hh_j2ga8bo.js	80.6 KiB
watch.plex.tv/_next/static/chunks/0b5~.n6cv._dk.js	69.2 KiB
watch.plex.tv/_next/static/chunks/0lnysf8ih7x0c.js	54.7 KiB
watch.plex.tv/_next/static/media/83afe278b6a6bb3c-s.p.0q-301v4kxxnr.woff2	47.4 KiB
watch.plex.tv/_next/static/media/plexcircular_bold-s.p.0~lzwwd35msql.woff2	47.3 KiB
/photo?size=medium-240&scale=2&url=https%3A%2F%2Fwatch.pl...	40.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
watch.plex.tv/_next/static/chunks/0b5~.n6cv._dk.js	4.0 s	2.9 s	16 ms
watch.plex.tv/	3.6 s	168 ms	96 ms
Unattributable	920 ms	18 ms	0.0 ms
watch.plex.tv/_next/static/chunks/0.9hh_j2ga8bo.js	104 ms	76 ms	27 ms
watch.plex.tv/_next/static/chunks/12~bx1mtphe1a.js	62 ms	1.1 ms	60 ms
watch.plex.tv/_next/static/chunks/10.9~gg31g6wt.js	60 ms	28 ms	3.0 ms
watch.plex.tv/_next/static/chunks/03v8rkma_-~tx.js	52 ms	1.2 ms	50 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	3.6 s
Script Evaluation	3.3 s
Style & Layout	1.1 s
Rendering	480 ms
Script Parsing & Compilation	419 ms
Parse HTML & CSS	184 ms
Garbage Collection	143 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Avoid non-composited animations 3 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 160 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP breakdown

○LCP request discovery

○User Timing marks and measures

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
18% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
52% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
67% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
88% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
39% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
49% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
4% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
10% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
42% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
49% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
43% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
54% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
65% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
watch.plex.tv/	`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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
watch.plex.tv/_next/static/chunks/12~bx1mtphe1a.js
watch.plex.tv/_next/static/chunks/03v8rkma_-~tx.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.34 s

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

0 ms

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

0 ms

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.

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

—

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.

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 ▾

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.

Request	Cache TTL	Transfer Size
www.gstatic.com/eureka/clank/147/cast_sender.js	86400.0 s	13.4 KiB
js.sentry-cdn.com/eb76eae607a34d13b8a50419d1ffaee2.min.js	3600.0 s	2.6 KiB

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.

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:102.101 source:map[column:7483 line:1 type:source-location url:https://watch.plex.tv/_next/static/chunks/0b5~.n6cv._dk.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:53.639 source:map[column:9878 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/07tl3rotd2mc_.js urlProvider:network]] map[reflowTime:48.462 source:map[column:10359 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/07tl3rotd2mc_.js urlProvider:network]] map[reflowTime:0.967 source:map[column:11432 line:0 type:source-location url:https://watch.plex.tv/_next/static/chunks/0-mdppugogl1w.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.

	URL	Resource Size	Est Savings
main._13usayk0 > div.MaxLineWidthContainer-module__MEYx5G__container > div.page-module__26JAeW__background > img `main._13usayk0 > div.MaxLineWidthContainer-module__MEYx5G__container > div.page-module__26JAeW__background > img`	/photo?size=medium-360&scale=2&url=https%3A%2F%2Fwatch.pl...	70.4 KiB	46.8 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	24.4 KiB	10.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	23.4 KiB	9.3 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	22.4 KiB	8.3 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	21.1 KiB	7.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.8 KiB	6.7 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fimage.tmd...	20.7 KiB	6.6 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	20.6 KiB	6.6 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.5 KiB	5.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.5 KiB	5.4 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.1 KiB	5.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	19.1 KiB	5.0 KiB
figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img `figure._13usayk0 > div._1fh5d4i0 > div._1r30c241 > img`	/photo?size=small-120&scale=2&url=https%3A%2F%2Fmetadata-...	18.5 KiB	4.4 KiB

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.

URL	Transfer Size
watch.plex.tv/_next/static/chunks/0-0799m-p~90-.css	390 B
watch.plex.tv/_next/static/chunks/0b53._4vz-2.f.css	1.2 KiB
watch.plex.tv/_next/static/chunks/0c1boempfpe~0.css	3.5 KiB
watch.plex.tv/_next/static/chunks/0fya108mn-sir.css	689 B
watch.plex.tv/_next/static/chunks/0o5pd79qgcp7p.css	1.0 KiB
watch.plex.tv/_next/static/chunks/0iz3arwp4-m7n.css	1.8 KiB
watch.plex.tv/_next/static/chunks/0z649sqx-ph0p.css	1.0 KiB
watch.plex.tv/_next/static/chunks/0is~zce6~7v8o.css	1.4 KiB
watch.plex.tv/_next/static/chunks/0xakpy8jbfiyn.css	1.1 KiB
watch.plex.tv/_next/static/chunks/0hhd.tds38i2h.css	356 B
watch.plex.tv/_next/static/chunks/0y9v7rihnr7s~.css	1.1 KiB
watch.plex.tv/_next/static/chunks/0tbl1g0n0h.d-.css	4.1 KiB
watch.plex.tv/_next/static/chunks/087tpnh8o_d5m.css	314 B
watch.plex.tv/_next/static/chunks/1517q4obivnz0.css	524 B
watch.plex.tv/_next/static/chunks/0v-jh6izbz_hb.css	371 B
watch.plex.tv/_next/static/chunks/0jrr_mb8e-7pe.css	3.4 KiB
watch.plex.tv/_next/static/chunks/01s3q8j-8a9e3.css	4.2 KiB
watch.plex.tv/_next/static/chunks/0rbz9ubwqck0v.css	535 B
watch.plex.tv/_next/static/chunks/04762~geobdbl.css	863 B
watch.plex.tv/_next/static/chunks/0y0u9y4h7ec3t.css	216 B
watch.plex.tv/_next/static/chunks/0ty1ncwpdrp68.css	694 B
watch.plex.tv/_next/static/chunks/0smbf3wsvab5-.css	1.6 KiB
watch.plex.tv/_next/static/chunks/0m..dgct052k0.css	470 B
watch.plex.tv/_next/static/chunks/00-tk-_mu0flt.css	1.4 KiB
watch.plex.tv/_next/static/chunks/0382mkbw46c1y.css	375 B
watch.plex.tv/_next/static/chunks/0~6a.l-l-vg19.css	364 B
watch.plex.tv/_next/static/chunks/14eg832tukr4i.css	1.2 KiB
watch.plex.tv/_next/static/chunks/185~rrs-dkfl2.css	1.0 KiB
watch.plex.tv/_next/static/chunks/00k00y0dfv9xe.css	355 B
watch.plex.tv/_next/static/chunks/0jc~gquh69su7.css	1.4 KiB
watch.plex.tv/_next/static/chunks/00gxicr.n7dn0.css	955 B
watch.plex.tv/_next/static/chunks/0i7ish49n248j.css	290 B
watch.plex.tv/_next/static/chunks/0jrje-s--t2xv.css	330 B
watch.plex.tv/_next/static/chunks/01r1fw9y.oasj.css	527 B
watch.plex.tv/_next/static/chunks/0..mrf23c8lfz.css	2.5 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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 ▾

Source: Google web.dev / Lighthouse

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.

Category	Time Spent
Script Evaluation	838 ms
Other	734 ms
Style & Layout	262 ms
Rendering	111 ms
Script Parsing & Compilation	104 ms
Garbage Collection	50 ms
Parse HTML & CSS	50 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 2,564 KiB

●JavaScript execution time 0.8 s

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 80 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP breakdown

○LCP request discovery

○User Timing marks and measures

Accessibility

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
18% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
52% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
67% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
88% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
39% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
49% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
4% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
10% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
42% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
49% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
43% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
54% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`
65% complete `div._1r30c241 > div._1mcyqow0 > div._1mcyqowa > div.aiglaa0`

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`
div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0 `div._13usayk0 > div.xhahwj0 > div.det6jpo > button._1x9vcnm0`

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
accounts.google.com/gsi/client line 85, col 88	`[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.`
watch.plex.tv/	`Not signed in with the identity provider.`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
watch.plex.tv/_next/static/chunks/12~bx1mtphe1a.js
watch.plex.tv/_next/static/chunks/03v8rkma_-~tx.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Results for https://plex.tv

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (1)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts