Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize stijnvansprang.nl
99.4% of the 20KB FontAwesome CSS file is unused, contributing unnecessary bloat to your page load.
Replace FontAwesome with individual SVG icons for only the icons you use. Alternatively, use a FontAwesome subset generator to include only required icons. Consider switching to WordPress's built-in Dashicons for basic UI elements.
A score of 70 falls in the "Needs Improvement" 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 poor performance with a score of 70/100, showing concerning load times of 4.4 seconds for both First Contentful Paint and a 5.2-second Largest Contentful Paint. The biggest issue is inefficient caching, which could save 174 KiB and improve loading times by up to 800ms - critical files like jQuery and tracking scripts have no cache lifetime set. Additional quick wins include removing 20 KiB of unused FontAwesome CSS (99% unused), deferring render-blocking stylesheets that are delaying initial paint by 820ms, and optimizing font loading with proper font-display settings. Addressing these caching and CSS optimization issues could easily boost the performance score into the 80s and significantly improve user experience.
Why It Matters:
Missing cache headers force 174 KiB of resources to re-download on every visit, delaying LCP by 800ms and FCP by 650ms.
How to Fix:
Add cache headers via your WordPress hosting panel or .htaccess file for static assets. Set 1-year expiry for jQuery, fonts, and JavaScript files. Configure your CDN or hosting provider to automatically cache WordPress assets with proper headers.
Why It Matters:
Multiple CSS files are blocking initial page render, delaying both LCP and FCP by 800ms.
How to Fix:
Use a WordPress optimization plugin like WP Rocket or Autoptimize to defer non-critical CSS. Inline critical above-the-fold styles directly in the HTML head. Load WooCommerce and plugin CSS files asynchronously using loadCSS or similar technique.
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.