LCP
Largest Contentful Paint
23.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Compress and Convert Images
How to optimize vrlearninglab.nl
Compress and Convert Images
High Impact+18 points estimated
Why It Matters
Images waste 1.6MB of bandwidth with the hero image alone being 96% larger than necessary for display.
How to Fix
Install ShortPixel or Imagify WordPress plugin for automatic WebP conversion. Resize the hero image from 768x1152 to actual display size of 581x656. Enable responsive images with proper srcset attributes for different screen sizes.
0Poor
What This Score Means
A score of 26 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
299ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.21
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has severe performance issues with a score of only 26/100. The biggest problem is extremely slow loading times, with the Largest Contentful Paint taking a devastating 23.4 seconds and First Contentful Paint at 4.1 seconds - both far exceeding acceptable standards. The primary culprits are massive unoptimized images (particularly a 1.6MB PNG that could be reduced by 1.5MB through modern formats like WebP and proper sizing), render-blocking CSS and JavaScript files that delay initial page rendering, and excessive unused code from plugins and third-party scripts. Immediately optimizing images, deferring non-critical resources, and cleaning up unused CSS/JavaScript could potentially improve the score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Optimize LCP Image Discovery
High Impact+25 points estimatedWhy It Matters:
The largest contentful paint element takes 23.4 seconds to load due to poor resource discovery and render delays.
How to Fix:
Add fetchpriority='high' to your main hero image. Ensure the LCP image is directly referenced in HTML, not loaded via JavaScript. Remove lazy loading from above-the-fold images and preload the LCP image with <link rel='preload' as='image'>.
Eliminate Render Blocking Resources
High Impact+20 points estimatedWhy It Matters:
CSS and font files are blocking initial page render for 3.8 seconds, severely delaying First Contentful Paint.
How to Fix:
Install WP Rocket or Autoptimize to inline critical CSS. Move non-critical CSS to load after page render using media='print' onload technique. Self-host Google Fonts or use font-display: swap to prevent render blocking.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More WordPress Speed Tests
WordPress Performance Resources
Eliminate Render Blocking Resources
CSS and font files are blocking initial page render for 3.8 seconds, severely delaying First Contentful Paint.
Optimize LCP Image Discovery
The largest contentful paint element takes 23.4 seconds to load due to poor resource discovery and render delays.
Implement Proper Image Dimensions
Images without explicit dimensions cause layout shifts and prevent browser optimization during page load.
Eliminate Unused JavaScript Code
Excessive JavaScript execution blocks the main thread for 5.8 seconds, causing 1,040ms Total Blocking Time.