www.sudinfo.be speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:08 UTC. Grade E (57/100), with the screenshots, the timings and the fixes that matter.

https://www.sudinfo.be/

20 October 2026 at 15:08 UTC · Free test · report pt_9fb5c81c05bf

Re-test this page Test your own site

Grade

57/100

Performance53/100

Structure62/100

8 audit(s) passed, 8 need work

First byte (TTFB)445 msmeasured from this server

Fully loaded5.59 sfirst byte + slowest asset

Requests26document + assets

Page weight9.87 MBcompressed transfer

HTML document158.7 KBgzip

ProtocolHTTP/3server not sent

Third-party9.72 MBother hosts

Where the first byte went

DNS lookup 80 ms 18%
TCP connect 25 ms 6%
Server wait 340 ms 76%

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

Page weightheavier than 97% of 4,999 pages tested here9.87 MB against a median of 650.3 KB

Fully loadedslower than 93% of 4,999 pages tested here5.59 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 445 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 9.87 MB over 26 request(s). Images files are 98% 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.
98% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 128 ms, inside the 2.5 s Google calls good.

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 www.sudinfo.be — **Desktop** 1366 × 768 · 24.2 KB · page is 768 px tall

Mobile screenshot of www.sudinfo.be — **Mobile** 390 × 844 · 7.8 KB · page is 2121 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 paint128 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint128 msfirst content on screen

Browser page weight457 B1 request(s), scripts included

Largest contentful paint128 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

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

Images 25 requests

9.72 MB 98%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 445 ms. Of that, 340 ms was the server thinking and 105 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.

Image delivery and format

high impact

10 image(s) over 200 KB and 15 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.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (3 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.

Total page weight

high impact

The page transfers 9.87 MB across 26 request(s), with the document itself at 158.7 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

1 third-party host(s) serve 9.72 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.