LCP
Largest Contentful Paint
9.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundle Size
How to optimize koditt.nl
Reduce Unused JavaScript Bundle Size
High Impact+25 points estimated
Why It Matters
480KB of unused JavaScript delays LCP by 2.6 seconds and blocks main thread execution.
How to Fix
Configure Next.js bundle analyzer to identify unused code. Enable tree-shaking in webpack config. Remove Google Tag Manager/Analytics if not essential or load asynchronously. Use dynamic imports for heavy components that aren't immediately visible.
0Poor
What This Score Means
A score of 35 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
443ms
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 severe performance problems with a critically low score of 35/100. The biggest issue is an extremely slow Time to Interactive of 42 seconds, caused by excessive JavaScript execution (3.2 seconds) and 469 KiB of unused JavaScript code from Google Tag Manager and other scripts. The site is also suffering from forced reflows that are blocking the main thread for over 1 second, creating a terrible user experience with 8.3 seconds of Total Blocking Time. Removing unused JavaScript, optimizing the Google Analytics implementation, and fixing the forced reflow issues could dramatically improve performance and reduce load times by several seconds.
Other Optimization Recommendations
Fix Cookie Dialog Element Render
High Impact+20 points estimatedWhy It Matters:
Cookie dialog causes 5.2 second element render delay, making it the LCP element instead of actual content.
How to Fix:
Move Cookiebot initialization to after page load using Next.js useEffect hook. Add CSS to prevent layout shift by reserving space. Consider server-side rendering the dialog or using a lighter cookie solution that doesn't block rendering.
Add Preconnect Headers for External Origins
Medium Impact+8 points estimatedWhy It Matters:
Missing preconnect hints to CMS and Cookiebot domains waste 300ms each on connection setup.
How to Fix:
Add preconnect links in Next.js Head component for cms.koditt.dev and consent.cookiebot.com. Use <link rel='preconnect' href='https://cms.koditt.dev' /> in your _document.js file. Limit to 4 total preconnect hints for optimal performance.
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.