vu.nl/nl speed test — 20 Oct 2026

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

https://vu.nl/nl

20 October 2026 at 15:09 UTC · Free test · report pt_1708f3cba6b0
Grade
B
82/100
Performance85/100
Structure77/100

11 audit(s) passed, 5 need work

First byte (TTFB)730 msmeasured from this server
Fully loaded1.61 sfirst byte + slowest asset
Requests12document + assets
Page weight354.3 KBcompressed transfer
HTML document10.8 KBbr
ProtocolHTTP/3server not sent
Third-party343.3 KBother hosts

Where the first byte went

  • DNS lookup 55 ms 8%
  • TCP connect 181 ms 25%
  • Server wait 494 ms 68%

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 72% of 4,999 pages tested here730 ms against a median of 448 ms
Page weightlighter than 68% of 4,999 pages tested here354.3 KB against a median of 650.5 KB
Fully loadedfaster than 63% of 4,999 pages tested here1.61 s against a median of 1.84 s
Requestssends fewer requests than 86% of 4,999 pages tested here12 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 730 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 354.3 KB over 12 request(s), which is lean. Images files are 97% 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.
  • 97% 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 2.03 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.058), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 136 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 vu.nl
Desktop 1366 × 768 · 81.7 KB · page is 4013 px tall
Mobile screenshot of vu.nl
Mobile 390 × 844 · 223.9 KB · page is 5549 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 paint2.03 sgood is under 2.5 s
Cumulative layout shift0.058under 0.1 is stable
Total blocking time136 mslong tasks during load
First contentful paint2.03 sfirst content on screen
Browser page weight6.29 MB40 request(s), scripts included
Largest contentful paint2.03 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.058
Goodgood under 0.1, poor over 0.25
Total blocking time136 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request
343.1 KB 97%
Html 2 requests
341 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 730 ms. Of that, 494 ms was the server thinking and 236 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

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

Render-blocking resources

high impact

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

Third-party weight

medium impact

2 third-party host(s) serve 343.3 KB 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.

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.

Waterfall

Slowest requests

JAVASCRIPTvu.nl/nl/assets/js/webcomponents/header.js
878 ms
CSSvu.nl/nl/css/site.css
765 ms
JAVASCRIPTvu.nl/nl/widgets/v1/js/vendors.min.js
753 ms
HTMLvu.nl/nl/favicon.ico
743 ms
CSSvu.nl/nl/assets/css/site.min.css
739 ms
JAVASCRIPTvu.nl/nl/widgets/v1/js/widgets.js
693 ms
JAVASCRIPTvu.nl/nl/assets/js/webcomponents/footer.js
669 ms
JAVASCRIPTvu.nl/nl/assets/js/site.min.js
663 ms
CSSvu.nl/nl/VU.Content.Web.styles.css
630 ms
IMAGESassets-eu-01.kc-usercontent.com/ff31ad68-341e-015e-fb52-24df7a00ecea/c…
511 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://vu.nl/nl/assets/js/webcomponents/header.js?v=eafe8c34javascript405878 ms0 B
https://vu.nl/nl/css/site.css?v=WgB-QY70v3uNTbOktJm4SEDUWnz8QLT7zE8b1ZGhFq4css405765 ms0 B
https://vu.nl/nl/widgets/v1/js/vendors.min.js?v=eafe8c34javascript405753 ms0 B
https://vu.nl/nl/favicon.icohtml404743 ms153 B
https://vu.nl/nl/assets/css/site.min.css?v=eafe8c34css405739 ms0 B
https://vu.nl/nl/widgets/v1/js/widgets.js?v=eafe8c34javascript405693 ms0 B
https://vu.nl/nl/assets/js/webcomponents/footer.js?v=eafe8c34javascript405669 ms0 B
https://vu.nl/nl/assets/js/site.min.js?v=eafe8c34javascript405663 ms0 B
https://vu.nl/nl/VU.Content.Web.styles.css?v=2wOKx4anEnCXKdKPOMW_3C_bxybMZ2Rpfca9huwqd20css405630 ms0 B
https://assets-eu-01.kc-usercontent.com:443/ff31ad68-341e-015e-fb52-24df7a00ecea/c57abf57-4301-4c2b-92f6-9bbc9c04d165/PeVa_Vu_Bachelordag_nov-5_-5925_1MB.jpg?w=2200&h=720&fit=clip&rect=0,0,2200,720 3rd partyimages200511 ms343.1 KB
https://www.googletagmanager.com/ns.html?id=GTM-KCTGHZ&gtm_auth=WWjmCWcPCcDb_mzcoezkGA&gtm_preview=env-2&gtm_cookies_win=x 3rd partyhtml200511 ms188 B
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.