www.threads.com speed test — 20 Oct 2026

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

https://www.threads.com/

20 October 2026 at 12:25 UTC · Free test · report pt_ba2ce88d3280
Grade
B
89/100
Performance95/100
Structure79/100

11 audit(s) passed, 5 need work

First byte (TTFB)402 msmeasured from this server
Fully loaded1.03 sfirst byte + slowest asset
Requests11document + assets
Page weight259.1 KBcompressed transfer
HTML document102.4 KBzstd
ProtocolHTTP/3server not sent
Third-party156.3 KBother hosts

Where the first byte went

  • DNS lookup 48 ms 12%
  • TCP connect 85 ms 21%
  • Server wait 269 ms 67%

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 56% of 4,999 pages tested here402 ms against a median of 449 ms
Page weightlighter than 75% of 4,999 pages tested here259.1 KB against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.03 s against a median of 1.84 s
Requestssends fewer requests than 87% of 4,999 pages tested here11 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 402 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 259.1 KB over 11 request(s), which is lean. Css files are 40% 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.
  • 60% 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 2.09 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 36 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Mobile screenshot of www.threads.com
Mobile 390 × 844 · 139.5 KB · page is 4480 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 paint2.09 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time36 mslong tasks during load
First contentful paint1.67 sfirst content on screen
Browser page weight7.89 MB49 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint2.09 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time36 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 1 request
104.3 KB 40%
Images 8 requests
51.9 KB 20%
Other 1 request
506 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 402 ms. Of that, 269 ms was the server thinking and 133 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

10 render-blocking resource(s) in the document head (9 script(s), 1 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.threads.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.

HTML document size

medium impact

The document transfers 102.4 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.

Waterfall

Slowest requests

CSSstatic.cdninstagram.com/rsrc.php/v5/yz/l/0,cross/sd3qISRmbC_zC…
632 ms
IMAGESstatic.cdninstagram.com/rsrc.php/y1/r/nPOGBtES96E.webp
607 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yU/r/EvAz2IpMIRe.webp
583 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yc/r/-Y7SdpqJSl0.webp
556 ms
OTHERwww.threads.com/data/manifest.json
555 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yP/r/0Qa-AOmHi0c.ico
531 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yG/r/Q7LVlwLasp7.webp
530 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yn/r/fFvbm7ecCaM.webp
528 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yj/r/Z-TsZPmCWZr.webp
528 ms
IMAGESstatic.cdninstagram.com/rsrc.php/yn/r/7SwW_oOu6u4.webp
526 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.cdninstagram.com/rsrc.php/v5/yz/l/0,cross/sd3qISRmbC_zCNj4xt7H1RfgQe914iiBfONMKn3YhINqU49pVNahkCk.css 3rd partycss200632 ms104.3 KB
https://static.cdninstagram.com/rsrc.php/y1/r/nPOGBtES96E.webp 3rd partyimages200607 ms2.5 KB
https://static.cdninstagram.com/rsrc.php/yU/r/EvAz2IpMIRe.webp 3rd partyimages200583 ms1.4 KB
https://static.cdninstagram.com/rsrc.php/yc/r/-Y7SdpqJSl0.webp 3rd partyimages200556 ms1.1 KB
https://www.threads.com/data/manifest.jsonother200555 ms506 B
https://static.cdninstagram.com/rsrc.php/yP/r/0Qa-AOmHi0c.ico 3rd partyimages200531 ms31.3 KB
https://static.cdninstagram.com/rsrc.php/yG/r/Q7LVlwLasp7.webp 3rd partyimages200530 ms3.7 KB
https://static.cdninstagram.com/rsrc.php/yn/r/fFvbm7ecCaM.webp 3rd partyimages200528 ms5.8 KB
https://static.cdninstagram.com/rsrc.php/yj/r/Z-TsZPmCWZr.webp 3rd partyimages200528 ms3.2 KB
https://static.cdninstagram.com/rsrc.php/yn/r/7SwW_oOu6u4.webp 3rd partyimages200526 ms3.0 KB
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.