www.datagrail.io speed test — 20 Oct 2026

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

https://www.datagrail.io/

20 October 2026 at 14:50 UTC · Free test · report pt_c6360fe03c84

Re-test this page Test your own site

Grade

95/100

Performance99/100

Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)252 msmeasured from this server

Fully loaded1.44 sfirst byte + slowest asset

Requests26document + assets

Page weight352.6 KBcompressed transfer

HTML document49.1 KBbr

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 64 ms 25%
TCP connect 34 ms 13%
Server wait 154 ms 61%

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

Page weightlighter than 68% of 4,999 pages tested here352.6 KB against a median of 650.5 KB

Fully loadedfaster than 74% of 4,999 pages tested here1.44 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 252 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 352.6 KB over 26 request(s). Images files are 86% of it, so resize and recompress the largest images before anything else.
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 556 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.051), so nothing jumps under the reader's cursor.
The main thread was blocked for 286 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 www.datagrail.io — **Mobile** 390 × 844 · 72.4 KB · page is 6000 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 paint556 msgood is under 2.5 s

Cumulative layout shift0.051under 0.1 is stable

Total blocking time286 mslong tasks during load

First contentful paint556 msfirst content on screen

Browser page weight3.43 MB112 request(s), scripts included

Failed requests7blocked or unreachable

Largest contentful paint556 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.051

Goodgood under 0.1, poor over 0.25

Total blocking time286 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

303.5 KB 86%

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

Top issues

Render-blocking resources

high impact

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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.