icedq.com speed test — 2 Nov 2026

Measured from the wfix.shop server on 2 November 2026 at 08:19 UTC. Grade A (94/100), with the screenshots, the timings and the fixes that matter.

https://icedq.com/

2 November 2026 at 08:19 UTC · Pro test · report pt_0bec512bcc3f

Re-test this page Test your own site

Grade

94/100

Performance92/100

Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)266 msmeasured from this server

Fully loaded3.09 sfirst byte + slowest asset

Requests26document + assets

Page weight479.4 KBcompressed transfer

HTML document65.0 KBbr

ProtocolHTTP/3cloudflare

Third-party414.4 KBother hosts

Where the first byte went

DNS lookup 49 ms 18%
TCP connect 44 ms 17%
Server wait 173 ms 65%

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 81% of 4,999 pages tested here266 ms against a median of 449 ms

Page weightlighter than 60% of 4,999 pages tested here479.4 KB against a median of 651.0 KB

Fully loadedslower than 83% of 4,999 pages tested here3.09 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 266 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 479.4 KB over 26 request(s). Fonts files are 44% of it, so subset the fonts and stop preloading the weights you do not render.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
86% 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 228 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 192 ms in total, which is not enough to feel.

Fix first: Third-party weight - Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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 icedq.com — **Desktop** 1366 × 768 · 128.9 KB · page is 3805 px tall

Mobile screenshot of icedq.com — **Mobile** 390 × 844 · 62.5 KB · page is 6000 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 paint228 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time192 mslong tasks during load

First contentful paint228 msfirst content on screen

Browser page weight3.81 MB124 request(s), scripts included

Failed requests5blocked or unreachable

Largest contentful paint228 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time192 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 11 requests

208.6 KB 44%

Css 7 requests

198.1 KB 41%

Images 3 requests

5.5 KB 1%

Other 3 requests

2.3 KB 0%

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

Top issues

Third-party weight

medium impact

1 third-party host(s) serve 414.4 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.