sssinstagram.com/blocked speed test — 20 Oct 2026

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

https://sssinstagram.com/blocked

20 October 2026 at 16:12 UTC · Free test · report pt_94cfa0c58c60
Grade
A
91/100
Performance91/100
Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)531 msmeasured from this server
Fully loaded1.06 sfirst byte + slowest asset
Requests8document + assets
Page weight593 Bcompressed transfer
HTML document593 Bbr
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 71 ms 13%
  • TCP connect 40 ms 8%
  • Server wait 420 ms 79%

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 byteslower than 58% of 4,999 pages tested here531 ms against a median of 448 ms
Page weightlighter than 98% of 4,999 pages tested here593 B against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.06 s against a median of 1.84 s
Requestssends fewer requests than 90% of 4,999 pages tested here8 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 took 531 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 593 B over 8 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 328 ms, inside the 2.5 s Google calls good.

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.

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 paint328 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 paint328 msfirst content on screen
Browser page weight12.6 KB3 request(s), scripts included
Largest contentful paint328 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. 8 request(s) in total, 593 B across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 531 ms. Of that, 420 ms was the server thinking and 111 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.

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.

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

HTMLsssinstagram.com/blocked/favicon.ico
531 ms
HTMLsssinstagram.com/blocked/favicon/android-chrome-192x192…
498 ms
HTMLsssinstagram.com/blocked/favicon/favicon-32x32.png
486 ms
HTMLsssinstagram.com/blocked/favicon/favicon-16x16.png
485 ms
HTMLsssinstagram.com/blocked/favicon/apple-touch-icon.png
483 ms
HTMLsssinstagram.com/blocked/favicon/android-chrome-512x512…
483 ms
HTMLsssinstagram.com/blocked/favicon/favicon-48x48.png
462 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://sssinstagram.com/blocked/favicon.icohtml404531 ms0 B
https://sssinstagram.com/blocked/favicon/android-chrome-192x192.pnghtml404498 ms0 B
https://sssinstagram.com/blocked/favicon/favicon-32x32.pnghtml404486 ms0 B
https://sssinstagram.com/blocked/favicon/favicon-16x16.pnghtml404485 ms0 B
https://sssinstagram.com/blocked/favicon/apple-touch-icon.pnghtml404483 ms0 B
https://sssinstagram.com/blocked/favicon/android-chrome-512x512.pnghtml404483 ms0 B
https://sssinstagram.com/blocked/favicon/favicon-48x48.pnghtml404462 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.