igram.world/blocked speed test — 20 Oct 2026

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

https://igram.world/blocked

20 October 2026 at 16:24 UTC · Free test · report pt_eb65d2195d1c
Grade
A
96/100
Performance98/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)261 msmeasured from this server
Fully loaded502 msfirst byte + slowest asset
Requests2document + assets
Page weight563 Bcompressed transfer
HTML document563 Bbr
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 76 ms 29%
  • TCP connect 29 ms 11%
  • Server wait 157 ms 60%

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 here261 ms against a median of 449 ms
Page weightlighter than 98% of 4,999 pages tested here563 B against a median of 650.5 KB
Fully loadedfaster than 98% of 4,999 pages tested here502 ms against a median of 1.84 s
Requestssends fewer requests than 96% of 4,999 pages tested here2 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 261 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 563 B over 2 request(s), which is lean.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 232 ms, inside the 2.5 s Google calls good.

Fix first: Avoid extra redirects - 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.

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 igram.world
Desktop 1366 × 768 · 10.4 KB · page is 768 px tall
Mobile screenshot of igram.world
Mobile 390 × 844 · 8.5 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 paint232 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 paint232 msfirst content on screen
Browser page weight11.9 KB3 request(s), scripts included
Largest contentful paint232 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

Transfer size, compressed as sent. 2 request(s) in total, 563 B across all of them.

Top issues

Avoid extra redirects

medium impact

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

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

HTMLigram.world/blocked/favicon.ico
241 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://igram.world/blocked/favicon.icohtml302241 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.