ifconfig.co speed test — 20 Oct 2026

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

https://ifconfig.co/

20 October 2026 at 14:08 UTC · Free test · report pt_2877afd0b6da
Grade
A
94/100
Performance95/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)395 msmeasured from this server
Fully loaded843 msfirst byte + slowest asset
Requests5document + assets
Page weight11.7 KBcompressed transfer
HTML document6.6 KBzstd
ProtocolHTTP/3cloudflare
Third-party5.1 KBother hosts

Where the first byte went

  • DNS lookup 77 ms 19%
  • TCP connect 38 ms 10%
  • Server wait 279 ms 71%

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 57% of 4,999 pages tested here395 ms against a median of 449 ms
Page weightlighter than 95% of 4,999 pages tested here11.7 KB against a median of 650.5 KB
Fully loadedfaster than 94% of 4,999 pages tested here843 ms against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 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 395 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 11.7 KB over 5 request(s), which is lean. Css files are 37% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 43% 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 976 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.065), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 58 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - 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.

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 ifconfig.co
Desktop 1366 × 768 · 95.8 KB · page is 1467 px tall
Mobile screenshot of ifconfig.co
Mobile 390 × 844 · 46.8 KB · page is 3075 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 paint976 msgood is under 2.5 s
Cumulative layout shift0.065under 0.1 is stable
Total blocking time58 mslong tasks during load
First contentful paint640 msfirst content on screen
Browser page weight409.4 KB15 request(s), scripts included
Largest contentful paint976 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.065
Goodgood under 0.1, poor over 0.25
Total blocking time58 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 3 requests
4.3 KB 37%
Html 1 request
806 B 7%

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

Top issues

Render-blocking resources

high impact

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

CSSfonts.googleapis.com/css2
448 ms
CSScdnjs.cloudflare.com/ajax/libs/pure/1.0.0/grids-responsive-…
330 ms
CSScdnjs.cloudflare.com/ajax/libs/pure/1.0.0/pure-min.css
313 ms
HTMLwww.openstreetmap.org/export/embed.html
260 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://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,400;0,700;1,400&display=swap 3rd partycss200448 ms297 B
https://cdnjs.cloudflare.com/ajax/libs/pure/1.0.0/grids-responsive-min.css 3rd partycss200330 ms742 B
https://cdnjs.cloudflare.com/ajax/libs/pure/1.0.0/pure-min.css 3rd partycss200313 ms3.3 KB
https://www.openstreetmap.org/export/embed.html?bbox=-97.872%2C37.701%2C-97.772%2C37.800999999999995&layer=mapnik&marker=37.751%2C-97.822 3rd partyhtml200260 ms806 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.