t.co speed test — 20 Oct 2026

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

https://t.co/

20 October 2026 at 12:36 UTC · Free test · report pt_795ed9a03fb8
Grade
A
99/100
Performance100/100
Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)209 msmeasured from this server
Fully loaded473 msfirst byte + slowest asset
Requests3document + assets
Page weight1.8 KBcompressed transfer
HTML document1.3 KBgzip
ProtocolHTTP/3cloudflare envoy
Third-party504 Bother hosts

Where the first byte went

  • DNS lookup 42 ms 20%
  • TCP connect 24 ms 11%
  • Server wait 142 ms 68%

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 91% of 4,999 pages tested here209 ms against a median of 449 ms
Page weightlighter than 97% of 4,999 pages tested here1.8 KB against a median of 650.5 KB
Fully loadedfaster than 98% of 4,999 pages tested here473 ms against a median of 1.84 s
Requestssends fewer requests than 95% of 4,999 pages tested here3 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 209 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.8 KB over 3 request(s), which is lean.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 27% 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 220 ms, inside the 2.5 s Google calls good.

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

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 t.co
Mobile 390 × 844 · 11.7 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 paint220 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint220 msfirst content on screen
Browser page weight3.4 KB2 request(s), scripts included
Largest contentful paint220 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request
504 B 27%

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

Top issues

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

IMAGESabs.twimg.com/favicons/favicon.ico
264 ms
HTMLt.co/static/images/x.png
211 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://abs.twimg.com/favicons/favicon.ico 3rd partyimages200264 ms504 B
https://t.co/static/images/x.pnghtml404211 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.