Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize stijnvansprang.nl
3.5 seconds of JavaScript execution time blocks the main thread and causes 17.97 second Total Blocking Time.
Remove or defer the large model-viewer.min.js library (245KB) that has 36% unused code. Use code splitting to load only necessary parts. Consider replacing with a lighter 3D viewer or loading it only when the model is interacted with.
A score of 20 falls in the "Poor" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This WordPress site has severe performance issues with a critically low score of 20/100. The biggest problem is massive layout shift (0.329 CLS score) caused by unsized images and web fonts loading, making the page visually unstable as content jumps around during loading. The site is also severely bogged down by a heavy 3D model viewer JavaScript library that blocks the main thread for over 41 seconds and contains 88KB of unused code. Fixing the image sizing issues, optimizing or removing the 3D model viewer, and cleaning up the 63KB of unused CSS could dramatically improve both the user experience and Core Web Vitals scores.
Why It Matters:
Layout shifts of 0.329 severely hurt user experience and CLS scores, primarily caused by web font loading.
How to Fix:
Add font-display: swap to all custom fonts in your CSS. Preload critical fonts using <link rel='preload'> tags in WordPress header. Use font metric overrides or size-adjust CSS to match fallback fonts and prevent shifts during loading.
Why It Matters:
CSS and JavaScript files block initial page rendering, delaying First Contentful Paint by 450ms.
How to Fix:
Inline critical CSS directly in your WordPress theme's header.php file. Defer non-critical CSS using media='print' then switching to 'all' on load. Move jQuery and other scripts to footer or use async/defer attributes in your theme's functions.php.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.