ajax.systems speed test — 20 Oct 2026

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

https://ajax.systems/

20 October 2026 at 14:40 UTC · Free test · report pt_8aaf14c1bd66

Re-test this page Test your own site

Grade

93/100

Performance94/100

Structure91/100

15 audit(s) passed, 1 need work

First byte (TTFB)354 msmeasured from this server

Fully loaded2.06 sfirst byte + slowest asset

Requests26document + assets

Page weight51.8 KBcompressed transfer

HTML document41.1 KBgzip

ProtocolHTTP/3CloudFront

Where the first byte went

DNS lookup 87 ms 25%
TCP connect 47 ms 13%
Server wait 220 ms 62%

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 64% of 4,999 pages tested here354 ms against a median of 449 ms

Page weightlighter than 91% of 4,999 pages tested here51.8 KB against a median of 650.5 KB

Fully loadedslower than 59% of 4,999 pages tested here2.06 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 354 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 51.8 KB over 26 request(s).
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 532 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.
The main thread was blocked for 213 ms, so taps and scrolling wait while scripts run.

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.

Mobile screenshot of ajax.systems — **Mobile** 390 × 844 · 38.8 KB · page is 5385 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 paint532 msgood is under 2.5 s

Cumulative layout shift0.003under 0.1 is stable

Total blocking time213 mslong tasks during load

First contentful paint532 msfirst content on screen

Browser page weight2.23 MB108 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint532 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.003

Goodgood under 0.1, poor over 0.25

Total blocking time213 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request

9.9 KB 19%

Other 24 requests

768 B 1%

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

Top issues

Render-blocking resources

high impact

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