www.unixtools.org speed test — 20 Oct 2026

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

https://www.unixtools.org/

20 October 2026 at 14:49 UTC · Free test · report pt_c2b1b5e737e2
Grade
A
96/100
Performance96/100
Structure95/100

14 audit(s) passed, 2 need work

First byte (TTFB)345 msmeasured from this server
Fully loaded590 msfirst byte + slowest asset
Requests2document + assets
Page weight5.9 KBcompressed transfer
HTML document4.7 KBgzip
ProtocolHTTP/3AmazonS3

Where the first byte went

  • DNS lookup 70 ms 20%
  • TCP connect 54 ms 16%
  • Server wait 221 ms 64%

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 66% of 4,999 pages tested here345 ms against a median of 449 ms
Page weightlighter than 96% of 4,999 pages tested here5.9 KB against a median of 650.5 KB
Fully loadedfaster than 97% of 4,999 pages tested here590 ms against a median of 1.84 s
Requestssends fewer requests than 96% of 4,999 pages tested here2 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 345 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 5.9 KB over 2 request(s), which is lean.
  • 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 232 ms, inside the 2.5 s Google calls good.

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

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 www.unixtools.org
Mobile 390 × 844 · 184.2 KB · page is 4550 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 paint232 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint232 msfirst content on screen
Browser page weight5.5 KB1 request(s), scripts included
Largest contentful paint232 ms
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

Images 1 request
1.2 KB 20%

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

Top issues

Cache static assets

medium impact

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

Avoid extra redirects

medium impact

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

Waterfall

Slowest requests

IMAGESwww.unixtools.org/icons/favicon.png
245 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.unixtools.org/icons/favicon.pngimages200245 ms1.2 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.