iconify.design speed test — 20 Oct 2026

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

https://iconify.design/

20 October 2026 at 16:17 UTC · Free test · report pt_2aec8e0e4276
Grade
A
90/100
Performance91/100
Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)535 msmeasured from this server
Fully loaded1.36 sfirst byte + slowest asset
Requests9document + assets
Page weight111.2 KBcompressed transfer
HTML document14.6 KBbr
ProtocolHTTP/3cloudflare
Third-party17.3 KBother hosts

Where the first byte went

  • DNS lookup 70 ms 13%
  • TCP connect 35 ms 7%
  • Server wait 431 ms 81%

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 here535 ms against a median of 448 ms
Page weightlighter than 87% of 4,999 pages tested here111.2 KB against a median of 650.5 KB
Fully loadedfaster than 79% of 4,999 pages tested here1.36 s against a median of 1.84 s
Requestssends fewer requests than 89% of 4,999 pages tested here9 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 535 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 111.2 KB over 9 request(s), which is lean. Fonts files are 60% 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.
  • The largest element painted at 1.10 s, 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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of iconify.design
Mobile 390 × 844 · 36.6 KB · page is 1786 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 paint1.10 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint600 msfirst content on screen
Browser page weight232.5 KB24 request(s), scripts included
Largest contentful paint1.10 s
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

Fonts 1 request
66.2 KB 60%
Images 4 requests
24.6 KB 22%
Javascript 2 requests
4.6 KB 4%
Css 1 request
1.2 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 535 ms. Of that, 431 ms was the server thinking and 105 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.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (3 script(s), 2 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.

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

JAVASCRIPTiconify.design/assets/app.B-CErQQL.js
826 ms
CSSiconify.design/assets/yt/lite-yt-embed.css
824 ms
IMAGESiconify.design/favicon.ico
787 ms
FONTSiconify.design/assets/inter-roman-latin.Di8DUHzh.woff2
749 ms
IMAGEScyberalien.github.io/static/sponsors.svg
609 ms
IMAGESiconify.design/apple-touch-icon.png
526 ms
JAVASCRIPTiconify.design/assets/yt/lite-yt-embed.js
491 ms
IMAGESiconify.design/favicon.svg
491 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://iconify.design/assets/app.B-CErQQL.jsjavascript200826 ms736 B
https://iconify.design/assets/yt/lite-yt-embed.csscss200824 ms1.2 KB
https://iconify.design/favicon.icoimages200787 ms1.8 KB
https://iconify.design/assets/inter-roman-latin.Di8DUHzh.woff2fonts200749 ms66.2 KB
https://cyberalien.github.io/static/sponsors.svg 3rd partyimages200609 ms17.3 KB
https://iconify.design/apple-touch-icon.pngimages200526 ms5.1 KB
https://iconify.design/assets/yt/lite-yt-embed.jsjavascript200491 ms3.9 KB
https://iconify.design/favicon.svgimages200491 ms304 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.