LCP
Largest Contentful Paint
4.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize koditt.nl
Remove Unused JavaScript Code
High Impact+18 points estimated
Why It Matters
453 KiB of unused JavaScript is delaying LCP by 600ms and adding unnecessary execution time.
How to Fix
Enable tree-shaking in your Next.js build configuration. Remove unused Google Analytics code and defer GTM loading with next/script's 'afterInteractive' strategy. Use dynamic imports for heavy components that aren't immediately needed.
0Needs Improvement
What This Score Means
A score of 53 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
398ms
Needs Improvement
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 Next.js site has poor performance with a score of 53/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking 1.6 seconds, combined with severe layout thrashing that causes 653ms of forced reflows when the browser has to recalculate page geometry. The site is also loading 453 KiB of unused JavaScript code and using outdated JavaScript features that bloat the bundle size. Reducing JavaScript payloads, eliminating unused code, and fixing the layout issues that cause forced reflows could improve the score by 30+ points and dramatically reduce the 8.4-second load time.
Other Optimization Recommendations
Eliminate JavaScript Forced Reflows
High Impact+25 points estimatedWhy It Matters:
Forced reflows are blocking the main thread for 653ms and directly causing the 2.5-second element render delay in LCP.
How to Fix:
Refactor DOM queries in your Next.js components to batch style changes and avoid reading geometric properties after DOM modifications. Use CSS transforms instead of changing layout properties, and implement virtual scrolling if you're measuring element dimensions dynamically.
Optimize Image Sizing Strategy
Medium Impact+8 points estimatedWhy It Matters:
Your hero image is 80% larger than needed, wasting 15 KiB and slowing visual rendering.
How to Fix:
Configure Next.js Image component with proper responsive breakpoints using the 'sizes' prop. Set up multiple image variants in your CMS at 380px, 665px, and 1200px widths. Enable Next.js's automatic WebP conversion for better compression.
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 Next.js Speed Tests
Next.js Performance Resources
Add Preconnect Headers for External Origins
Missing preconnect hints to CMS and Cookiebot domains waste 300ms each on connection setup.
Fix Cookie Dialog Element Render
Cookie dialog causes 5.2 second element render delay, making it the LCP element instead of actual content.
Add Preconnect to External Origins
Missing preconnect to cms.koditt.dev delays LCP by 323ms due to late connection establishment.
Eliminate Unused JavaScript Bundle
455 KiB of unused JavaScript delays LCP by 450ms and blocks main thread execution.