babesource.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 16:09 UTC. Grade C (79/100), with the screenshots, the timings and the fixes that matter.

https://babesource.com/

20 October 2026 at 16:09 UTC · Free test · report pt_bed93acae4b4

Re-test this page Test your own site

Grade

79/100

Performance78/100

Structure80/100

13 audit(s) passed, 3 need work

First byte (TTFB)920 msmeasured from this server

Fully loaded2.18 sfirst byte + slowest asset

Requests26document + assets

Page weight81.7 KBcompressed transfer

HTML document49.8 KBgzip

ProtocolHTTP/3nginx

Where the first byte went

DNS lookup 138 ms 15%
TCP connect 94 ms 10%
Server wait 688 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 byteslower than 82% of 4,999 pages tested here920 ms against a median of 448 ms

Page weightlighter than 89% of 4,999 pages tested here81.7 KB against a median of 650.5 KB

Fully loadedslower than 64% of 4,999 pages tested here2.18 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 took 920 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 81.7 KB over 26 request(s). Images files are 39% of it, so resize and recompress the largest images before anything else.
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 took 3.51 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout shift is 0.115 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 47 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.

Mobile screenshot of babesource.com — **Mobile** 390 × 844 · 333.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 paint3.51 sgood is under 2.5 s

Cumulative layout shift0.115under 0.1 is stable

Total blocking time47 mslong tasks during load

First contentful paint3.44 sfirst content on screen

Browser page weight3.10 MB153 request(s), scripts included

Largest contentful paint3.51 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.115

Needs improvementgood under 0.1, poor over 0.25

Total blocking time47 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

31.9 KB 39%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 920 ms. Of that, 688 ms was the server thinking and 232 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.

Render-blocking resources

high impact

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

Cache static assets

medium impact

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