LCP
Largest Contentful Paint
3.2s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Hero Image Loading Performance
How to optimize snoesje.sot.design
Optimize Hero Image Loading Performance
High Impact+12 points estimated
Why It Matters
The LCP image takes 5.3 seconds to load, causing significant delays in perceived page performance.
How to Fix
Compress the hero image using WordPress plugins like ShortPixel or Smush. Convert to WebP format for better compression. Consider using a CDN like Cloudflare Images for automatic optimization. Ensure the image is properly sized for mobile devices to reduce transfer time.
0Needs Improvement
What This Score Means
A score of 83 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
54ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has good performance with a score of 83/100, but there's room for improvement in loading speed. The biggest issue is the slow Speed Index at 7.0 seconds, indicating that page content takes too long to become visually complete for users. The main problems stem from a large hero image that takes over 5 seconds to load (affecting Largest Contentful Paint at 3.2 seconds) and several images missing explicit width/height dimensions that cause layout shifts. Quick wins include optimizing the hero image file size, adding proper image dimensions to prevent layout shifts, and extending cache lifetimes for Cloudflare scripts to improve repeat visitor experience.
Other Optimization Recommendations
Add Explicit Image Dimensions
Medium Impact+8 points estimatedWhy It Matters:
Unsized SVG images cause layout shifts as they load, negatively impacting user experience and CLS scores.
How to Fix:
Add width and height attributes to all SVG images in your WordPress theme files. For the kleinschalig.svg, betrokken.svg, and flexibel.svg images, define explicit dimensions in the img tags. Use CSS aspect-ratio property as a fallback for responsive sizing while maintaining layout stability.
Extend Cloudflare Cache Lifetimes
Low Impact+3 points estimatedWhy It Matters:
Short cache lifetimes force unnecessary re-downloads of static assets, slowing repeat visits.
How to Fix:
In your Cloudflare dashboard, increase cache TTL for static assets to at least 30 days. Set page rules for /cdn-cgi/scripts/* paths to cache for longer periods. Configure WordPress to add proper cache headers for theme assets through your hosting provider or caching plugin like WP Rocket.
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
Reduce Unused JavaScript Payload
Google Analytics and GTM are loading 138KB of unused code, slowing down page processing.
Defer Render Blocking Resources
GDPR compliance scripts are blocking initial page render and delaying content visibility.
Optimize Oversized Hero Image
The main image is 27KB larger than needed and directly delays LCP by 150ms.
Fix JavaScript Layout Thrashing
Forced reflows in your theme's script.js and Swiper library are causing 41ms of unnecessary layout calculations.