btttag.com speed test — 20 Oct 2026

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

https://btttag.com/

20 October 2026 at 15:36 UTC · Free test · report pt_a1f05f4fbaca
Grade
A
98/100
Performance98/100
Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)263 msmeasured from this server
Fully loaded263 msfirst byte + slowest asset
Requests1document + assets
Page weight352 Bcompressed transfer
HTML document352 Bgzip
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 93 ms 35%
  • TCP connect 16 ms 6%
  • Server wait 154 ms 59%

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 82% of 4,999 pages tested here263 ms against a median of 449 ms
Page weightlighter than 99% of 4,999 pages tested here352 B against a median of 650.5 KB
Fully loadedfaster than 100% of 4,999 pages tested here263 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 263 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 352 B over 1 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.
  • The largest element painted at 600 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.005), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 4 ms in total, which is not enough to feel.

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.

Desktop screenshot of btttag.com
Desktop 1366 × 768 · 230.4 KB · page is 768 px tall
Mobile screenshot of btttag.com
Mobile 390 × 844 · 69.4 KB · page is 844 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 paint600 msgood is under 2.5 s
Cumulative layout shift0.005under 0.1 is stable
Total blocking time4 mslong tasks during load
First contentful paint600 msfirst content on screen
Browser page weight923.7 KB47 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint600 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.005
Goodgood under 0.1, poor over 0.25
Total blocking time4 ms
Goodgood under 200 ms, poor over 600 ms

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.

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.