iqm.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:37 UTC. Grade C (71/100), with the screenshots, the timings and the fixes that matter.

https://iqm.com/

20 October 2026 at 13:37 UTC · Free test · report pt_e5cf7df2091c

Re-test this page Test your own site

Grade

71/100

Performance74/100

Structure67/100

11 audit(s) passed, 5 need work

First byte (TTFB)313 msmeasured from this server

Fully loaded5.31 sfirst byte + slowest asset

Requests26document + assets

Page weight1.83 MBcompressed transfer

HTML document31.4 KBgzip

ProtocolHTTP/2Apache

Where the first byte went

DNS lookup 57 ms 18%
TCP connect 73 ms 23%
Server wait 183 ms 58%

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

Page weightheavier than 79% of 4,999 pages tested here1.83 MB against a median of 650.3 KB

Fully loadedslower than 90% of 4,999 pages tested here5.31 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 313 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.83 MB over 26 request(s). Images files are 98% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element took 3.06 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 108 ms in total, which is not enough to feel.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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 iqm.com — **Mobile** 390 × 844 · 111.7 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 paint3.06 sgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time108 mslong tasks during load

First contentful paint1.59 sfirst content on screen

Browser page weight8.85 MB236 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint3.06 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time108 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

1.80 MB 98%

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

Top issues

Image delivery and format

high impact

4 image(s) over 200 KB and 2 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

60 render-blocking resource(s) in the document head (4 script(s), 56 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 1.83 MB across 26 request(s), with the document itself at 31.4 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

23 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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.