www.facebook.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:27 UTC. Grade A (90/100), with the screenshots, the timings and the fixes that matter.

https://www.facebook.com/

20 October 2026 at 12:27 UTC · Free test · report pt_d20878fe8e1b
Grade
A
90/100
Performance97/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)295 msmeasured from this server
Fully loaded676 msfirst byte + slowest asset
Requests5document + assets
Page weight384.4 KBcompressed transfer
HTML document80.3 KBzstd
ProtocolHTTP/3server not sent
Third-party304.1 KBother hosts

Where the first byte went

  • DNS lookup 43 ms 15%
  • TCP connect 44 ms 15%
  • Server wait 207 ms 70%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 75% of 4,999 pages tested here295 ms against a median of 449 ms
Page weightlighter than 66% of 4,999 pages tested here384.4 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here676 ms against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 295 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 384.4 KB over 5 request(s), which is lean. Css files are 73% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 79% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.90 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 240 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of www.facebook.com
Desktop 1366 × 768 · 281.2 KB · page is 868 px tall
Mobile screenshot of www.facebook.com
Mobile 390 × 844 · 15.1 KB · page is 2121 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.90 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time240 mslong tasks during load
First contentful paint952 msfirst content on screen
Browser page weight1.96 MB26 request(s), scripts included
Largest contentful paint1.90 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time240 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 1 request
280.6 KB 73%
Images 2 requests
23.5 KB 6%

Transfer size, compressed as sent. 5 request(s) in total, 384.4 KB across all of them.

Top issues

Render-blocking resources

high impact

11 render-blocking resource(s) in the document head (9 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

TLS certificate validity

high impact

The certificate for www.facebook.com has 7 day(s) left.

Fix: Renew automatically (certbot with a working renewal timer) and alert on the certificate, not on the renew command, so a silent failure is caught weeks before a browser warning.

Third-party weight

medium impact

1 third-party host(s) serve 304.1 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Waterfall

Slowest requests

IMAGESstatic.xx.fbcdn.net/rsrc.php/y1/r/ay1hV6OlegS.ico
381 ms
IMAGESstatic.xx.fbcdn.net/rsrc.php/yc/r/78KLk3JFzeg.webp
333 ms
CSSstatic.xx.fbcdn.net/rsrc.php/v5/yf/l/0,cross/ZcR4BF_zMZZlj…
316 ms
HTMLwww.facebook.com/&
245 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://static.xx.fbcdn.net/rsrc.php/y1/r/ay1hV6OlegS.ico 3rd partyimages200381 ms19.9 KB
https://static.xx.fbcdn.net/rsrc.php/yc/r/78KLk3JFzeg.webp 3rd partyimages200333 ms3.6 KB
https://static.xx.fbcdn.net/rsrc.php/v5/yf/l/0,cross/ZcR4BF_zMZZlj67fHbHf4Wxgo-3469oiGssSOK1ciB2RT9DWDYPz6DhfgQe914iiBfONMKn3YhINqU49pVNahkCk.css 3rd partycss200316 ms280.6 KB
https://www.facebook.com/'https://static.xx.fbcdn.net/rsrc.php/yc/r/78KLk3JFzeg.webp'html302245 ms0 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.