www.reserved.com/special/store?nolang=true speed test — 20 Oct 2026

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

https://www.reserved.com/special/store/?nolang=true

20 October 2026 at 14:54 UTC · Free test · report pt_04c408c714b6

Re-test this page Test your own site

Grade

93/100

Performance94/100

Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)425 msmeasured from this server

Fully loaded1.52 sfirst byte + slowest asset

Requests10document + assets

Page weight2.2 KBcompressed transfer

HTML document2.2 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 80 ms 19%
TCP connect 26 ms 6%
Server wait 319 ms 75%

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

Page weightlighter than 97% of 4,999 pages tested here2.2 KB against a median of 650.5 KB

Fully loadedfaster than 69% of 4,999 pages tested here1.52 s against a median of 1.84 s

Requestssends fewer requests than 88% of 4,999 pages tested here10 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 425 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 2.2 KB over 10 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 1.18 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.reserved.com — **Mobile** 390 × 844 · 31.4 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 paint1.18 sgood is under 2.5 s

Cumulative layout shift0.003under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint852 msfirst content on screen

Browser page weight590.1 KB14 request(s), scripts included

Largest contentful paint1.18 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.003

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

Html 8 requests

7 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 425 ms. Of that, 319 ms was the server thinking and 106 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Avoid extra redirects

medium impact

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