C — https://fb.watch | BeaverCheck Audit

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

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.

Strong compliance posture across regulations.

Good content signals with minor gaps.

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

HSTS · 1596 peers

You 73

Avg 74

At average

0 50 100

Better than 33% of HSTS sites See full HSTS benchmark →

HTTP/3 · 855 peers

You 73

Avg 74

At average

0 50 100

Better than 29% of HTTP/3 sites See full HTTP/3 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

2 button(s) with no accessible text

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

Accessibility › Link & Button Quality

2 control(s) without accessible label

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

Accessibility › Form Accessibility

83 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

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%2Ffb.watch)](https://beavercheck.com/results/381040db-b041-4ef2-9030-b1c76e4dbde9)

HTML

<a href="https://beavercheck.com/results/381040db-b041-4ef2-9030-b1c76e4dbde9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffb.watch" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Ffb.watch

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. Your LCP of 15.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. The 2 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. 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.

2 accessibility issues exclude users who rely on assistive technology.

Your LCP is 15.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 5 warning

6 barrier(s) likely increasing bounce by ~26%.

Speed (2)

Page takes 15.0s to load

+12% bounce

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

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

High main-thread blocking time

+2% bounce

Page is non-interactive for 506ms after first paint

Fix: Defer third-party scripts and split large bundles

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 (1)

2 form field(s) without a label

+4% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

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

$600 investment → $0.52/month returns + USD 150,000 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$0.52 /mo

~$6.23 / year

Bandwidth savings $0.52

Regulatory risk avoided

USD 150,000

if kept compliant

ADA Title III USD 150,000

$100 — 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

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /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,006 / year if left unfixed

Compliance Risk

$150,000

ADA Title III

Multiple <main> landmarks (2 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
Multiple H1 headings (2 found)
ADA Title III: USD 25,000 – USD 150,000

+1 more

Bandwidth Waste

$0.52 /mo

6494.4 MB/mo × 0.080 USD/GB

Optimize transfer: save ~649 KB per page load
Saves $0.52/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

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

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

15.03 s

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

506 ms

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

0.011

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

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

15.20 s

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.

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.

URL	Est Savings
z-m-static.xx.fbcdn.net/rsrc.php/yK/r/IF3dHXMs8z1.woff2	35 ms
z-m-static.xx.fbcdn.net/rsrc.php/yg/r/t2wH1ftBDi2.woff2	35 ms
z-m-static.xx.fbcdn.net/rsrc.php/y8/r/dndzIs-1lCT.woff2	30 ms
z-m-static.xx.fbcdn.net/rsrc.php/yq/r/WiBRSzbLmOQ.woff2	30 ms
z-m-static.xx.fbcdn.net/rsrc.php/yD/r/IptncetaoAc.woff2	20 ms
z-m-static.xx.fbcdn.net/rsrc.php/yQ/r/HQWYFjqve2v.woff2	15 ms

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:53.78 source:map[column:10078 line:0 type:source-location url:https://m.facebook.com/watch/?wtsid=rdr_0fZJkr2aPRh6hC387 urlProvider:network]] map[reflowTime:0.578 source:map[type:text value:[unattributed]]] map[reflowTime:0.947 source:map[column:489 line:2459 type:source-location url:https://z-m-static.xx.fbcdn.net/rsrc.php/v4/ys/r/hgyh9VX6CGz.js?_nc_wlbi=mb urlProvider:network]] map[reflowTime:0.158 source:map[column:111 line:2701 type:source-location url:https://z-m-static.xx.fbcdn.net/rsrc.php/v4/ys/r/hgyh9VX6CGz.js?_nc_wlbi=mb 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
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/670680089_1289338773328734_397252620571607...	84.9 KiB	68.8 KiB
Video player `div.m > div.m > div.m > img.img`	/v/t15.5256-10/673953121_2155621928624151_451783271075456...	61.2 KiB	40.4 KiB
Video player `div.m > div.m > div.m > img.img`	/v/t15.5256-10/673687735_873788189060005_2055009846444776...	53.0 KiB	35.0 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/674585426_831596909984690_5868860360332780...	37.1 KiB	24.5 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/673953121_2155621928624151_451783271075456...	29.9 KiB	19.7 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/675348389_1313039064045770_872478623059401...	24.5 KiB	16.2 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/672811928_2112319506290582_336476407716206...	23.6 KiB	15.6 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/675751778_1664967484839388_313908078535474...	23.6 KiB	15.6 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/675965637_815919041582704_7307410913367699...	18.2 KiB	12.0 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/676076434_1565292565163720_246538909046495...	15.3 KiB	10.1 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/677101672_1711728219821572_593411319684206...	15.2 KiB	10.1 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	static.xx.fbcdn.net/rsrc.php/yw/r/lb9AGDLh1hK.webp	7.5 KiB	7.4 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	static.xx.fbcdn.net/rsrc.php/y_/r/pPeZK9-k_Ca.webp	6.9 KiB	6.8 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t15.5256-10/676923952_3195142070874537_428316204147434...	9.9 KiB	6.5 KiB
div.m > div.m > div.m > img.img `div.m > div.m > div.m > img.img`	/v/t51.71878-10/670634525_1472450500898024_63857629341327...	8.8 KiB	5.8 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-1-IMG

nodeLabel: Video player

path: 1,HTML,1,BODY,16,DIV,0,DIV,2,DIV,6,DIV,0,DIV,0,DIV,0,IMG

selector: div.m > div.m > div.m > img.img

snippet: <img src="https://scontent-sin2-3.xx.fbcdn.net/v/t15.5256-10/673953121_2155621928624…" data-type="image" alt="Video player" data-image-id="-1086360877777075174" class="img contain">

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

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
/v/t15.5256-10/675002762_1482258753676240_685463202449783...	1209600.0 s	164.8 KiB
/v/t15.5256-10/670680089_1289338773328734_397252620571607...	1209600.0 s	85.0 KiB
/v/t15.5256-10/673953121_2155621928624151_451783271075456...	1209600.0 s	61.2 KiB
/v/t15.5256-10/673687735_873788189060005_2055009846444776...	1209600.0 s	53.1 KiB
/v/t15.5256-10/673950207_2800484143633683_266472454976465...	1209600.0 s	49.2 KiB
/v/t51.82787-10/670915720_18587671906010852_4332118903654...	1209600.0 s	43.0 KiB
/v/t15.5256-10/674585426_831596909984690_5868860360332780...	1209600.0 s	37.2 KiB
/v/t51.71878-10/670580184_1292943642840108_48609697453107...	1209600.0 s	33.5 KiB
/v/t15.5256-10/673953121_2155621928624151_451783271075456...	1209600.0 s	29.9 KiB
/v/t15.5256-10/676883634_2869948183338687_867527107858536...	1209600.0 s	25.9 KiB
/v/t15.5256-10/675348389_1313039064045770_872478623059401...	1209600.0 s	24.6 KiB
/v/t15.5256-10/672811928_2112319506290582_336476407716206...	1209600.0 s	23.7 KiB
/v/t15.5256-10/675751778_1664967484839388_313908078535474...	1209600.0 s	23.7 KiB
/v/t51.71878-10/670634525_1472450500898024_63857629341327...	1209600.0 s	18.8 KiB
/v/t15.5256-10/675965637_815919041582704_7307410913367699...	1209600.0 s	18.3 KiB
/v/t15.5256-10/676076434_1565292565163720_246538909046495...	1209600.0 s	15.4 KiB
/v/t15.5256-10/677101672_1711728219821572_593411319684206...	1209600.0 s	15.3 KiB
/v/t15.5256-10/676923952_3195142070874537_428316204147434...	1209600.0 s	9.9 KiB
/v/t51.71878-10/670634525_1472450500898024_63857629341327...	1209600.0 s	8.9 KiB
/v/t39.30808-1/597847430_122104149003156106_2975973327229...	1209600.0 s	3.7 KiB
/v/t39.30808-1/480060008_1214477154020922_795198265209877...	1209600.0 s	3.5 KiB
/v/t39.30808-1/673804862_933751524094_8549732761640999770...	1209600.0 s	3.4 KiB
/v/t39.30808-1/481668914_1123169419820320_867289539373334...	1209600.0 s	2.5 KiB
/v/t39.30808-1/600373241_25031351269894213_56677365735527...	1209600.0 s	2.0 KiB
/v/t39.30808-1/231242617_361982052231233_7457792347275166...	1209600.0 s	1.7 KiB
/v/t39.30808-1/476161138_122122429610614787_7976006230394...	1209600.0 s	1.7 KiB
/v/t39.30808-1/263891967_105821945279711_3597897419680266...	1209600.0 s	1.5 KiB

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

URL	Time Spent
fb.watch/	953 ms
www.facebook.com/watch/	929 ms
m.facebook.com/watch/?wtsid=rdr_0fZJkr2aPRh6hC387	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

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

Estimated savings: 2.1 s 332.0 KiB

URL	Transfer Size	Est Savings
z-m-static.xx.fbcdn.net/rsrc.php/v4/ys/r/hgyh9VX6CGz.js?_nc_wlbi=mb	417.1 KiB	243.9 KiB
z-m-static.xx.fbcdn.net/rsrc.php/v4/yb/r/kEGNHTlCuU3.js?_nc_wlbi=3f64ff6a	116.8 KiB	88.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
z-m-static.xx.fbcdn.net/rsrc.php/v4/ys/r/hgyh9VX6CGz.js?_nc_wlbi=mb	1.2 s	698 ms	211 ms
m.facebook.com/watch/?wtsid=rdr_0fZJkr2aPRh6hC387#	996 ms	563 ms	30 ms
Unattributable	639 ms	21 ms	0.0 ms
m.facebook.com/watch/?wtsid=rdr_0fZJkr2aPRh6hC387	508 ms	12 ms	2.3 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4/yb/r/kEGNHTlCuU3.js?_nc_wlbi=3f64ff6a	286 ms	214 ms	64 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
Script Evaluation	1.5 s
Style & Layout	812 ms
Other	734 ms
Script Parsing & Compilation	315 ms
Parse HTML & CSS	98 ms
Garbage Collection	81 ms
Rendering	70 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 reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
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
Back/forward cache is disabled because WebSocket has been used.	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 10.2 KiB

URL	Transfer Size	Est Savings
z-m-static.xx.fbcdn.net/rsrc.php/v5/yF/l/0,cross/6KNv-fzEftQ.css	11.8 KiB	10.2 KiB

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 9 long tasks found

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

●Network Requests

●Network Round Trip Times 10 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 250 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#app-body > iframe#sem_pixel_iframe `body#app-body > iframe#sem_pixel_iframe`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.m > div.m > div.m > a `div.m > div.m > div.m > a`
div.m > div.m > div.m > a `div.m > div.m > div.m > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mary Lovett Fowler `div.m > div.m > div.m > div.m`
Mary Lovett Fowler `div.m > div.m > div.native-text > span.f2`
1.7M `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.native-text > span.f2`
40K `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.native-text > span.f2`
619,637 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
4,751 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
43,559 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
981,433 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
226,588 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
289,082 reactions `div.m > div.m > div.m > div.m`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
󱛻 22M 󱝍 `div.m > div.m > div.m > div.m`
󱛻 8.2M 󱝍 `div.m > div.m > div.m > div.m`
󱛻 7.5M 󱝍 `div.m > div.m > div.m > div.m`
Mary Lovett Fowler `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	z-m-static.xx.fbcdn.net/rsrc.php/v4/yb/r/kEGNHTlCuU3.js?_nc_wlbi=3f64ff6a line 15, col 229441

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	Map URL
z-m-static.xx.fbcdn.net/rsrc.php/v4/ys/r/hgyh9VX6CGz.js?_nc_wlbi=mb
z-m-static.xx.fbcdn.net/rsrc.php/v4/yb/r/kEGNHTlCuU3.js?_nc_wlbi=3f64ff6a	z-m-static.xx.fbcdn.net/rsrc.php/v4/yb/r/ozplayer.min.js.map

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
body#app-body > a `body#app-body > a`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●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

100

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

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

3.19 s

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

260 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.42 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.

3.36 s

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.

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:78.633 source:map[column:1634 line:232 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4/yV/r/ce-O1eEeZ9o.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:35.268 source:map[type:text value:[unattributed]]] map[reflowTime:58.159 source:map[column:1047 line:1340 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7IXxtAyPQ4tQwhPZghFabta6CDrC9UOnKt83K8bFOYAWX5t7ZgVWv8FRnWc_RghZQt77v8QrxHexsHi6G0lcS5xAv_03sE6NmmF4EGzH400hc7MnJGlnf6n2NZxWdqHbG6IWYRwNBms6P6BuiZ-nuDiI4j4SE1-LXf2eYAiEtFyMlq7jazmKZjbThfXjv_7A8OQE.js urlProvider:network]] map[reflowTime:13.147 source:map[column:988 line:1352 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7IXxtAyPQ4tQwhPZghFabta6CDrC9UOnKt83K8bFOYAWX5t7ZgVWv8FRnWc_RghZQt77v8QrxHexsHi6G0lcS5xAv_03sE6NmmF4EGzH400hc7MnJGlnf6n2NZxWdqHbG6IWYRwNBms6P6BuiZ-nuDiI4j4SE1-LXf2eYAiEtFyMlq7jazmKZjbThfXjv_7A8OQE.js urlProvider:network]] map[reflowTime:3.415 source:map[column:2189 line:1509 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7IXxtAyPQ4tQwhPZghFabta6CDrC9UOnKt83K8bFOYAWX5t7ZgVWv8FRnWc_RghZQt77v8QrxHexsHi6G0lcS5xAv_03sE6NmmF4EGzH400hc7MnJGlnf6n2NZxWdqHbG6IWYRwNBms6P6BuiZ-nuDiI4j4SE1-LXf2eYAiEtFyMlq7jazmKZjbThfXjv_7A8OQE.js urlProvider:network]] map[reflowTime:2.295 source:map[column:704 line:1331 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7IXxtAyPQ4tQwhPZghFabta6CDrC9UOnKt83K8bFOYAWX5t7ZgVWv8FRnWc_RghZQt77v8QrxHexsHi6G0lcS5xAv_03sE6NmmF4EGzH400hc7MnJGlnf6n2NZxWdqHbG6IWYRwNBms6P6BuiZ-nuDiI4j4SE1-LXf2eYAiEtFyMlq7jazmKZjbThfXjv_7A8OQE.js urlProvider:network]] map[reflowTime:1.617 source:map[column:2539 line:541 type:source-location url:https://static.xx.fbcdn.net/rsrc.php/v4iSVg4/yu/l/en_GB-j/JshSlPNui4y.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
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/650056388_3198423287011321_286326950236211...	64.7 KiB	59.4 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/675517533_1488187393103543_680524711961329...	58.2 KiB	52.8 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/675467368_2173147796772706_585421612117522...	54.0 KiB	48.5 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/675751778_1664967484839388_313908078535474...	38.0 KiB	33.6 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/673687735_873788189060005_2055009846444776...	37.0 KiB	32.7 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t51.71878-10/673047050_2892319074432762_42551270828013...	33.5 KiB	29.6 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t15.5256-10/674442191_1524590532338167_754178681043599...	32.2 KiB	28.4 KiB
Video thumbnail `div.html-div > div.html-div > div.x5yr21d > img.xz74otr`	/v/t51.82787-10/670915720_18587671906010852_4332118903654...	22.6 KiB	20.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-2-IMG

nodeLabel: Video thumbnail

path: 1,HTML,1,BODY,124,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,IMG

selector: div.html-div > div.html-div > div.x5yr21d > img.xz74otr

snippet: <img class="xz74otr x15mokao x1ga7v0g x16uus16 xbiv7yw x1ey2m1c xtijo5x x1o0tod xr1yuq…" alt="Video thumbnail" referrerpolicy="origin-when-cross-origin" src="https://scontent-sin2-1.xx.fbcdn.net/v/t15.5256-10/675467368_2173147796772…">

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.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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	Duration
/rsrc.php/v5/yF/l/0,cross/Ub3N3UJ4z_hSRcPYBIrKwmoii7yv5Xg...	270.0 KiB	688 ms

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
/v/t15.5256-10/650056388_3198423287011321_286326950236211...	1209600.0 s	64.8 KiB
/v/t15.5256-10/675517533_1488187393103543_680524711961329...	1209600.0 s	58.2 KiB
/v/t15.5256-10/675467368_2173147796772706_585421612117522...	1209600.0 s	54.0 KiB
/v/t15.5256-10/675751778_1664967484839388_313908078535474...	1209600.0 s	38.1 KiB
/v/t15.5256-10/673687735_873788189060005_2055009846444776...	1209600.0 s	37.1 KiB
/v/t51.71878-10/673047050_2892319074432762_42551270828013...	1209600.0 s	33.5 KiB
/v/t15.5256-10/674442191_1524590532338167_754178681043599...	1209600.0 s	32.2 KiB
/v/t51.82787-10/670915720_18587671906010852_4332118903654...	1209600.0 s	22.7 KiB
/v/t39.30808-1/391625642_122099371304085242_3470404008925...	1209600.0 s	4.3 KiB
/v/t39.30808-1/632202382_122107571655233167_6270774072512...	1209600.0 s	3.0 KiB
/v/t39.30808-1/291336675_2522061381263562_252168758140545...	1209600.0 s	3.0 KiB
/v/t39.30808-1/616780398_1496426519157892_211741373652143...	1209600.0 s	2.9 KiB
/v/t39.30808-1/373532353_868910824790704_6582964671934438...	1209600.0 s	2.8 KiB
/v/t39.30808-1/653706001_871539422594614_4239607834930150...	1209600.0 s	2.8 KiB
/v/t39.30808-1/481668914_1123169419820320_867289539373334...	1209600.0 s	2.7 KiB
/v/t39.30808-1/231242617_361982052231233_7457792347275166...	1209600.0 s	2.3 KiB

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: 501 ms

URL	Time Spent
fb.watch/	501 ms
www.facebook.com/watch/	0.0 ms

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

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: 210 ms 255.3 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/yF/l/0,cross/Ub3N3UJ4z_hSRcPYBIrKwmoii7yv5Xg...	269.9 KiB	255.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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 640 ms 738.5 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7I...	647.1 KiB	434.0 KiB
static.xx.fbcdn.net/rsrc.php/v4iSVg4/yu/l/en_GB-j/JshSlPNui4y.js	232.8 KiB	88.6 KiB
static.xx.fbcdn.net/rsrc.php/v4/yF/r/0gdcbeCC4AI.js	56.5 KiB	50.2 KiB
/rsrc.php/v4iT1Q4/y0/l/en_GB-j/X3EHhe2z3NNapUw4VP-PvzjncE...	66.1 KiB	39.6 KiB
static.xx.fbcdn.net/rsrc.php/v4/yV/r/ce-O1eEeZ9o.js	72.4 KiB	34.3 KiB
static.xx.fbcdn.net/rsrc.php/v4i2VD4/yQ/l/en_GB-j/sLOTs4dhB6z.js	26.8 KiB	24.9 KiB
static.xx.fbcdn.net/rsrc.php/v4/yO/r/GTyAdGuz8x-.js	24.6 KiB	23.5 KiB
static.xx.fbcdn.net/rsrc.php/v4ij3W4/yT/l/en_GB-j/HvJdohBMAYb.js	24.4 KiB	23.1 KiB
/rsrc.php/v4in404/yJ/l/en_GB-j/9sxasPF6Mr2LMusfBKLXXDRi7m...	39.8 KiB	20.5 KiB

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
The page has an unload handler in the main frame.	Actionable
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

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 86 user timings

●JavaScript execution time 0.9 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 5 long tasks found

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

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 300 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See more on Facebook Email address or phone number Password Log in Forgotten pa… `div.x1uvtmcs > div.__fb-light-mode > div.x1cy8zhl > div.x1n2onr6`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Create new account `div.html-div > div.x9f619 > span.x193iq5w > span.x1lliihq`

These are opportunities to improve the legibility of your content.

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

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

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

●Elements use only permitted ARIA attributes

●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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

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

○Heading elements appear in a sequentially-descending order

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

○Links are distinguishable without relying on color.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.xx.fbcdn.net/rsrc.php/v4/yV/r/ce-O1eEeZ9o.js line 238, col 362

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
static.xx.fbcdn.net/rsrc.php/v4/yV/r/ce-O1eEeZ9o.js line 78, col 566	`ErrorUtils caught an error: terminate stream because StartStreamFailure with msg : UNAUTHENTICATED [Caught in: Subscription error in preprocessResponse] Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object]`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/rsrc.php/v4iY5o4/yT/l/en_GB-j/eXuNl-hBb1XKhD2nLdyIYBws7I...
static.xx.fbcdn.net/rsrc.php/v4iSVg4/yu/l/en_GB-j/JshSlPNui4y.js

●Uses HTTPS

●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

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes

Results for https://fb.watch

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Usability (1)

Content (1)

Navigation (1)

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

Names and labels

Best practices

Best Practices

General

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best Practices

Browser Compatibility

General

SEO

Keyboard Shortcuts