C — https://Facebook.com | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility › Form Accessibility

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

Accessibility › 404 Error Page

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2FFacebook.com)](https://beavercheck.com/results/f9b3dd11-8dc3-4698-b020-f3065da9800a)

HTML

<a href="https://beavercheck.com/results/f9b3dd11-8dc3-4698-b020-f3065da9800a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FFacebook.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓

UN New York

Full audit

76ms

DNS 3ms · TLS 3ms

ES Madrid

205ms

DNS 24ms · TLS 23ms

US Santa Clara

74ms

DNS 4ms · TLS 3ms

SG Singapore

227ms

DNS 2ms · TLS 4ms

NL Amsterdam

36ms

DNS 3ms · TLS 4ms

BR Sao Paulo

174ms

DNS 3ms · TLS 10ms

CDN: No CDN · Avg TTFB: 132ms · Cache: No cache headers

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

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.

6.02 s

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

7.94 s

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

432 ms

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

0.022

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

6.02 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

URL	Est Savings
z-m-static.xx.fbcdn.net/rsrc.php/yQ/r/-pkMfchyeAZ.woff2	30 ms
z-m-static.xx.fbcdn.net/rsrc.php/y2/r/6YirsaXqsap.woff2	10 ms

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.

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

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.

URL	Transfer Size	Duration
z-m-static.xx.fbcdn.net/rsrc.php/v4/y7/r/xtQcZ7ngAFd.js	70.5 KiB	3.0 s
z-m-static.xx.fbcdn.net/rsrc.php/v5/yU/l/0,cross/8LmiXDyZ1wv.css	412 B	796 ms
z-m-static.xx.fbcdn.net/rsrc.php/v5/yz/l/0,cross/b8bT8K6wJb8.css	912 B	796 ms
z-m-static.xx.fbcdn.net/rsrc.php/v5/yn/l/0,cross/MAcSbRsyo3E.css	7.4 KiB	959 ms
z-m-static.xx.fbcdn.net/rsrc.php/v5/yX/l/0,cross/xNRLBTJ11-F.css	1.2 KiB	796 ms
z-m-static.xx.fbcdn.net/rsrc.php/v5/yw/l/0,cross/NdI56imvkTb.css	961 B	796 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 1.6 s

URL	Time Spent
facebook.com/	812 ms
m.facebook.com/?wtsid=rdr_0s3dPBkkfoyXUEr51	790 ms
/ig/login_via/app/?lid=1ZyaSLfke7IbvuoCx&bn=Y29tLmFuZHJva...	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.

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.

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.

Estimated savings: 1.3 s 231.7 KiB

URL	Transfer Size	Est Savings
z-m-static.xx.fbcdn.net/rsrc.php/v4/yR/r/g2ZaHD-GDwx.js	189.5 KiB	92.4 KiB
z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js	91.3 KiB	67.5 KiB
z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js	52.2 KiB	38.4 KiB
z-m-static.xx.fbcdn.net/rsrc.php/v4/y7/r/xtQcZ7ngAFd.js	70.3 KiB	33.4 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.

URL	Total CPU Time	Script Evaluation	Script Parse
z-m-static.xx.fbcdn.net/rsrc.php/v4/yR/r/g2ZaHD-GDwx.js	654 ms	457 ms	112 ms
/ig/login_via/app/?lid=1ZyaSLfke7IbvuoCx&bn=Y29tLmFuZHJva...	519 ms	272 ms	59 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4/y7/r/xtQcZ7ngAFd.js	467 ms	335 ms	75 ms
Unattributable	348 ms	27 ms	0.0 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4/yN/r/PTIcotwBK8l.js	91 ms	83 ms	6.4 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4iLl54/yI/l/en_US-j/PGkgmDG_Xd0.js	83 ms	72 ms	7.0 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js	61 ms	13 ms	27 ms
z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js	56 ms	7.6 ms	46 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

Category	Time Spent
Script Evaluation	1.3 s
Other	415 ms
Script Parsing & Compilation	351 ms
Style & Layout	158 ms
Parse HTML & CSS	70 ms
Rendering	29 ms
Garbage Collection	24 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

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 that use WebAuthetication API are not eligible for 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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
Facebook from Meta `div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1`	z-m-static.xx.fbcdn.net/rsrc.php/yU/r/0gFm6_6mwp0.webp
div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1 `div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1`	z-m-static.xx.fbcdn.net/rsrc.php/yh/r/iXKRnkL1VeD.webp
div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1 `div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1`	z-m-static.xx.fbcdn.net/rsrc.php/yS/r/kHeVcteEMil.webp
div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1 `div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1`	z-m-static.xx.fbcdn.net/rsrc.php/ys/r/lBaBOo8QfeT.webp

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 904 KiB

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 12 long tasks found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

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

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Failing Elements
Facebook from Meta `div.wbloks_1 > div.wbloks_1 > div.wbloks_1 > img.wbloks_1`

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

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

Failing Elements
div#root > div._7om2 > div._4g34 > iframe#sem_pixel_iframe `div#root > div._7om2 > div._4g34 > iframe#sem_pixel_iframe`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Failing Elements
html.wbloks_11 `html.wbloks_11`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

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

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

●`[role]` 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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

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

○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

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

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

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	z-m-static.xx.fbcdn.net/rsrc.php/v4/y7/r/xtQcZ7ngAFd.js line 276, col 794

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

Source Description

Source	Description
z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js line 72, col 4235	`TypeError: Cannot read properties of undefined (reading 'getElementsByTagName') at Object.F [as scry] (https://z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js:73:4236) at Object.ue [as scrollToHeader] (https://z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js:86:4465) at u (https://z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js:12:253) at e (https://z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js:12:482)`

z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js line 72, col 4235

TypeError: Cannot read properties of undefined (reading 'getElementsByTagName')
    at Object.F [as scry] (https://z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js:73:4236)
    at Object.ue [as scrollToHeader] (https://z-m-static.xx.fbcdn.net/rsrc.php/v4iczx4/yi/l/en_US-j/f2S8cvI5JnB.js:86:4465)
    at u (https://z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js:12:253)
    at e (https://z-m-static.xx.fbcdn.net/rsrc.php/v4/yo/r/1c5BvaDlz8l.js:12:482)

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.

URL
z-m-static.xx.fbcdn.net/rsrc.php/v4/yR/r/g2ZaHD-GDwx.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

●Properly defines charset

●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

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.

○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

●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

100

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

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

2.50 s

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

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

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

lhId: page-0-IMG

nodeLabel: div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn

path: 1,HTML,1,BODY,62,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,3,IMG

selector: div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn

snippet: <img class="xr4gsrn xa83c8o x3oym20 x1i84rja x1is6hmk x1pwz1hh x12fhftt x19kjcj4 x1u2x…" alt="" referrerpolicy="origin-when-cross-origin" src="https://static.xx.fbcdn.net/rsrc.php/y0/r/U45qBJmWVHU.webp">

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.

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

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.

URL	Transfer Size	Duration
/rsrc.php/v5/yF/l/0,cross/fj7QDCd-Vcdo2mChyuSNQIoii7yv5Xg...	268.3 KiB	445 ms

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

URL	Est Savings
static.xx.fbcdn.net/rsrc.php/yQ/r/-pkMfchyeAZ.woff2	10 ms
static.xx.fbcdn.net/rsrc.php/yl/r/9AJbVCy4-G1.woff2	5.0 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn `div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn`	static.xx.fbcdn.net/rsrc.php/y0/r/U45qBJmWVHU.webp	177.2 KiB	141.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.

Estimated savings: 212 ms

URL	Time Spent
facebook.com/	212 ms
www.facebook.com/	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.

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.

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.

Estimated savings: 140 ms 300.2 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/yF/l/0,cross/fj7QDCd-Vcdo2mChyuSNQIoii7yv5Xg...	268.1 KiB	258.6 KiB
static.xx.fbcdn.net/rsrc.php/v5/yn/l/0,cross/cFZJE8drElvg8T_6-Yirbb.css	30.8 KiB	29.8 KiB
:root, .__fb-light-mode:root, .__fb-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,…	17.8 KiB	11.8 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.

Estimated savings: 720 ms 857.0 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v4iSJ94/yk/l/en_US-j/UXWe6ta71gPqq23lXnK5fQoXp1...	237.7 KiB	161.3 KiB
static.xx.fbcdn.net/rsrc.php/v4iYeD4/y6/l/en_US-j/cab2CGxVJ7W.js	228.6 KiB	110.6 KiB
/rsrc.php/v4ipTm4/yP/l/en_US-j/QfCA_ELSQ5VAjEdhn01I-R1X1f...	124.7 KiB	96.8 KiB
static.xx.fbcdn.net/rsrc.php/v4iWlL4/yL/l/en_US-j/WcAF9pLKoVt.js	93.7 KiB	86.8 KiB
static.xx.fbcdn.net/rsrc.php/v4/yU/r/DcrX2w7W64E.js	76.3 KiB	76.2 KiB
static.xx.fbcdn.net/rsrc.php/v4ie444/y7/l/en_US-j/fjWsYWETEN5.js	65.9 KiB	59.8 KiB
static.xx.fbcdn.net/rsrc.php/v4iQnF4/yb/l/en_US-j/8nWC-okWq-s.js	100.4 KiB	56.0 KiB
static.xx.fbcdn.net/rsrc.php/v4iDQn4/yS/l/en_US-j/eS845CZGYn2.js	54.9 KiB	46.9 KiB
static.xx.fbcdn.net/rsrc.php/v4i1NA4/yw/l/en_US-j/Ju1IKP5Z_Ru.js	49.3 KiB	39.7 KiB
static.xx.fbcdn.net/rsrc.php/v4/ym/r/D86XEw3a--O.js	74.0 KiB	38.8 KiB
static.xx.fbcdn.net/rsrc.php/v4i44x4/yZ/l/en_US-j/lSJtwZwvbAy.js	49.0 KiB	35.9 KiB
static.xx.fbcdn.net/rsrc.php/v4i2VD4/yX/l/en_US-j/fFEyKe9uV59.js	26.8 KiB	25.2 KiB
/rsrc.php/v4iZoy4/y1/l/en_US-j/n5HPHhoxPjLZVLXDePzCsmodxK...	42.3 KiB	23.0 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

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 that use WebAuthetication API are not eligible for back/forward cache.	Pending browser support
Chrome Password Manager was present upon navigating away.	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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn `div.x9f619 > div.x9f619 > div.x9f619 > img.xr4gsrn`	static.xx.fbcdn.net/rsrc.php/y0/r/U45qBJmWVHU.webp

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 82 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 2 long tasks found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

100

Accessibility

○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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○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

○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

○Heading elements appear in a sequentially-descending order

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

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

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

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

General

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

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.xx.fbcdn.net/rsrc.php/v4/ym/r/D86XEw3a--O.js line 251, col 362

URL
static.xx.fbcdn.net/rsrc.php/v4iYeD4/y6/l/en_US-j/cab2CGxVJ7W.js
static.xx.fbcdn.net/rsrc.php/v4iWlL4/yL/l/en_US-j/WcAF9pLKoVt.js
/rsrc.php/v4iSJ94/yk/l/en_US-j/UXWe6ta71gPqq23lXnK5fQoXp1...

●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 browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

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

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`

Browse & Analyze

Learn

Results for https://Facebook.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Internationalization and localization

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

Browser Compatibility

General

SEO

Content Best Practices

Keyboard Shortcuts