www.mijnwoordenboek.nl speed test — 20 Oct 2026

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

https://www.mijnwoordenboek.nl/

20 October 2026 at 16:00 UTC · Free test · report pt_d9da93218caa
Grade
C
78/100
Performance86/100
Structure67/100

10 audit(s) passed, 6 need work

First byte (TTFB)616 msmeasured from this server
Fully loaded2.20 sfirst byte + slowest asset
Requests26document + assets
Page weight797.2 KBcompressed transfer
HTML document6.5 KBgzip
ProtocolHTTP/3server not sent
Third-party359.8 KBother hosts

Where the first byte went

  • DNS lookup 66 ms 11%
  • TCP connect 169 ms 27%
  • Server wait 381 ms 62%

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 64% of 4,999 pages tested here616 ms against a median of 448 ms
Page weightheavier than 56% of 4,999 pages tested here797.2 KB against a median of 650.3 KB
Fully loadedslower than 65% of 4,999 pages tested here2.20 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 616 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 797.2 KB over 26 request(s). Javascript files are 60% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 45% 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 1.56 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 56 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 www.mijnwoordenboek.nl
Mobile 390 × 844 · 21.9 KB · page is 2568 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 paint1.56 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time56 mslong tasks during load
First contentful paint1.56 sfirst content on screen
Browser page weight774.1 KB35 request(s), scripts included
Largest contentful paint1.56 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time56 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 7 requests
476.5 KB 60%
Css 6 requests
273.4 KB 34%
Images 11 requests
40.5 KB 5%
Other 1 request
263 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 616 ms. Of that, 381 ms was the server thinking and 235 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.

Compress text responses

high impact

6 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 382.7 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

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

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

Third-party weight

medium impact

3 third-party host(s) serve 359.8 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.

Waterfall

Slowest requests

CSSwww.mijnwoordenboek.nl/inc/bootstrap.css
1.59 s
OTHERwww.mijnwoordenboek.nl/site.webmanifest
1.56 s
IMAGESwww.mijnwoordenboek.nl/favicon-16x16.png
1.55 s
IMAGESwww.mijnwoordenboek.nl/favicon-32x32.png
1.55 s
IMAGESwww.mijnwoordenboek.nl/apple-touch-icon.png
1.54 s
JAVASCRIPTwww.mijnwoordenboek.nl/inc/jquery.mobile.customized.min.js
1.54 s
JAVASCRIPTwww.mijnwoordenboek.nl/inc/custom.js
1.53 s
JAVASCRIPTwww.mijnwoordenboek.nl/inc/jquery-1.7.2.min.js
1.52 s
JAVASCRIPTwww.mijnwoordenboek.nl/inc/jquery.mobilemenu.js
1.52 s
JAVASCRIPTwww.mijnwoordenboek.nl/inc/superfish.js
1.52 s

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://www.mijnwoordenboek.nl/inc/bootstrap.css?1css2001.59 s126.6 KB
https://www.mijnwoordenboek.nl/site.webmanifestother2001.56 s263 B
https://www.mijnwoordenboek.nl/favicon-16x16.pngimages2001.55 s457 B
https://www.mijnwoordenboek.nl/favicon-32x32.pngimages2001.55 s981 B
https://www.mijnwoordenboek.nl/apple-touch-icon.pngimages2001.54 s13.3 KB
https://www.mijnwoordenboek.nl/inc/jquery.mobile.customized.min.js?1javascript2001.54 s17.1 KB
https://www.mijnwoordenboek.nl/inc/custom.jsjavascript2001.53 s1000 B
https://www.mijnwoordenboek.nl/inc/jquery-1.7.2.min.js?1javascript2001.52 s92.6 KB
https://www.mijnwoordenboek.nl/inc/jquery.mobilemenu.js?1javascript2001.52 s2.0 KB
https://www.mijnwoordenboek.nl/inc/superfish.js?1javascript2001.52 s4.5 KB
https://www.mijnwoordenboek.nl/img/400100crosswordclues.gifimages2001.51 s4.4 KB
https://www.mijnwoordenboek.nl/img/400100encyclouk.gifimages2001.50 s2.6 KB
https://www.mijnwoordenboek.nl/img/400100enzyklo.gifimages2001.50 s2.2 KB
https://www.mijnwoordenboek.nl/img/400100encyclopediefr.gifimages2001.50 s5.4 KB
https://www.mijnwoordenboek.nl/img/400100encyclonl.gifimages2001.48 s2.4 KB
https://www.mijnwoordenboek.nl/img/400100woorden.gifimages2001.47 s3.0 KB
https://www.mijnwoordenboek.nl/img/400100mijnwoordenboek.gifimages2001.45 s3.1 KB
https://www.mijnwoordenboek.nl/img/logo.pngimages2001.44 s2.7 KB
https://www.mijnwoordenboek.nl/font-awesome/css/font-awesome-min.css?1css2001.43 s20.5 KB
https://www.mijnwoordenboek.nl/inc/style.css?11102021css2001.42 s104.4 KB
https://www.mijnwoordenboek.nl/inc/responsive.css?220625css2001.41 s21.4 KB
https://www.googletagmanager.com/gtag/js?id=G-W9PKW7380D 3rd partyjavascript2001.39 s178.2 KB
https://fonts.googleapis.com/css2?family=Source+Code+Pro:wght@300;400&display=swap 3rd partycss2001.39 s238 B
https://fonts.googleapis.com/css?family=Open+Sans:400,300 3rd partycss2001.39 s233 B
https://nextday-cdn.relevant-digital.com/static/tags/5f73221f17fc0ff36b00b58f.js 3rd partyjavascript2001.37 s181.1 KB
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.