ash-digital-library.netlify.app speed test — 14 Nov 2026

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

https://ash-digital-library.netlify.app/

14 November 2026 at 20:09 UTC · Pro test · report pt_62e59f3420f7
Grade
A
91/100
Performance89/100
Structure95/100

15 audit(s) passed, 1 need work

First byte (TTFB)620 msmeasured from this server
Fully loaded620 msfirst byte + slowest asset
Requests1document + assets
Page weight10.2 KBcompressed transfer
HTML document10.2 KBbr
ProtocolHTTP/3Netlify

Where the first byte went

  • DNS lookup 55 ms 9%
  • TCP connect 108 ms 17%
  • Server wait 457 ms 74%

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 byteslower than 65% of 4,999 pages tested here620 ms against a median of 448 ms
Page weightlighter than 95% of 4,999 pages tested here10.2 KB against a median of 652.0 KB
Fully loadedfaster than 97% of 4,999 pages tested here620 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 took 620 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 10.2 KB over 1 request(s), which is lean.
  • 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 600 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.048), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 12 ms in total, which is not enough to feel.

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.

Desktop screenshot of ash-digital-library.netlify.app
Desktop 1366 × 768 · 321.5 KB · page is 768 px tall
Mobile screenshot of ash-digital-library.netlify.app
Mobile 390 × 844 · 132.8 KB · page is 871 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 paint600 msgood is under 2.5 s
Cumulative layout shift0.048under 0.1 is stable
Total blocking time12 mslong tasks during load
First contentful paint600 msfirst content on screen
Browser page weight8.99 MB31 request(s), scripts included
Largest contentful paint600 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.048
Goodgood under 0.1, poor over 0.25
Total blocking time12 ms
Goodgood under 200 ms, poor over 600 ms

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 620 ms. Of that, 457 ms was the server thinking and 163 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.

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.