www.ntppool.org/en speed test — 20 Oct 2026

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

https://www.ntppool.org/en/

20 October 2026 at 13:26 UTC · Free test · report pt_7f1ead05295f
Grade
A
96/100
Performance97/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)163 msmeasured from this server
Fully loaded2.19 sfirst byte + slowest asset
Requests6document + assets
Page weight63.2 KBcompressed transfer
HTML document6.6 KBbr
ProtocolHTTP/3Combust/Plack (Perl)
Third-party535 Bother hosts

Where the first byte went

  • DNS lookup 54 ms 33%
  • TCP connect 23 ms 14%
  • Server wait 87 ms 53%

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 97% of 4,999 pages tested here163 ms against a median of 449 ms
Page weightlighter than 90% of 4,999 pages tested here63.2 KB against a median of 650.5 KB
Fully loadedslower than 64% of 4,999 pages tested here2.19 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 server answered in 163 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 63.2 KB over 6 request(s), which is lean. Css files are 49% of it, so split the stylesheet so the first screen does not download the whole site.
  • 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 724 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.007), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 112 ms in total, which is not enough to feel.

Fix first: Avoid extra redirects - 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.

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 paint724 msgood is under 2.5 s
Cumulative layout shift0.007under 0.1 is stable
Total blocking time112 mslong tasks during load
First contentful paint476 msfirst content on screen
Browser page weight198.2 KB21 request(s), scripts included
Largest contentful paint724 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.007
Goodgood under 0.1, poor over 0.25
Total blocking time112 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 1 request
30.9 KB 49%
Javascript 2 requests
24.7 KB 39%
Images 2 requests
1.1 KB 2%

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

Top issues

Avoid extra redirects

medium impact

2 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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Waterfall

Slowest requests

IMAGESwww.ntppool.org/en/static/images/favicon.v717cb32e.ico
2.03 s
JAVASCRIPTwww.mapper.ntppool.org/mapper.js
341 ms
CSSwww.ntppool.org/en/static/build/style.v8cTAoGMz.css
338 ms
JAVASCRIPTwww.ntppool.org/en/static/build/app.vB-3x43EV.js
306 ms
IMAGESwww.ntppool.org/en/static/images/feed-icon16x16.vafa1f…
301 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://www.ntppool.org/en/static/images/favicon.v717cb32e.icoimages2002.03 s384 B
https://www.mapper.ntppool.org/mapper.js 3rd partyjavascript200341 ms535 B
https://www.ntppool.org/en/static/build/style.v8cTAoGMz.csscss200338 ms30.9 KB
https://www.ntppool.org/en/static/build/app.vB-3x43EV.jsjavascript200306 ms24.2 KB
https://www.ntppool.org/en/static/images/feed-icon16x16.vafa1ff4e.pngimages200301 ms709 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.