registrar-servers.com speed test — 20 Oct 2026

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

https://registrar-servers.com/

20 October 2026 at 12:34 UTC · Free test · report pt_9f2f113403d4
Grade
A
93/100
Performance100/100
Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)184 msmeasured from this server
Fully loaded553 msfirst byte + slowest asset
Requests5document + assets
Page weight36.5 KBcompressed transfer
HTML document703 Bgzip
ProtocolHTTP/3namecheap-web

Where the first byte went

  • DNS lookup 75 ms 41%
  • TCP connect 18 ms 10%
  • Server wait 91 ms 49%

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 95% of 4,999 pages tested here184 ms against a median of 449 ms
Page weightlighter than 92% of 4,999 pages tested here36.5 KB against a median of 650.5 KB
Fully loadedfaster than 98% of 4,999 pages tested here553 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 server answered in 184 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 36.5 KB over 5 request(s), which is lean. Images files are 71% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 180 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.027), so nothing jumps under the reader's cursor.

Fix first: Compress text responses - Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

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 registrar-servers.com
Desktop 1366 × 768 · 28.4 KB · page is 768 px tall
Mobile screenshot of registrar-servers.com
Mobile 390 × 844 · 24.5 KB · page is 844 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 paint180 msgood is under 2.5 s
Cumulative layout shift0.027under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint168 msfirst content on screen
Browser page weight96.2 KB6 request(s), scripts included
Largest contentful paint180 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.027
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

Images 3 requests
25.9 KB 71%
Css 1 request
9.9 KB 27%

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

Top issues

Compress text responses

high impact

1 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 9.9 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

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

Cache static assets

medium impact

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

Waterfall

Slowest requests

IMAGESregistrar-servers.com/assets/img/nc-icon/favicon.ico
369 ms
CSSregistrar-servers.com/assets/css/style.css
352 ms
IMAGESregistrar-servers.com/assets/img/redirect-rocket.png
347 ms
IMAGESregistrar-servers.com/assets/img/logos/namecheap-hd.png
347 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://registrar-servers.com/assets/img/nc-icon/favicon.icoimages200369 ms8.2 KB
https://registrar-servers.com/assets/css/style.csscss200352 ms9.9 KB
https://registrar-servers.com/assets/img/redirect-rocket.pngimages200347 ms9.5 KB
https://registrar-servers.com/assets/img/logos/namecheap-hd.pngimages200347 ms8.3 KB
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.