LCP
Largest Contentful Paint
5.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Preconnect for CMS Origin
How to optimize koditt.nl
Add Preconnect for CMS Origin
Medium Impact+8 points estimated
Why It Matters
Missing preconnect to cms.koditt.dev costs 321ms in LCP performance due to connection setup delays.
How to Fix
Add <link rel='preconnect' href='https://cms.koditt.dev'> to your Next.js _document.js Head component. Also add <link rel='dns-prefetch' href='https://cms.koditt.dev'> as fallback for older browsers.
0Poor
What This Score Means
A score of 37 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
463ms
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 issues with a critically low score of 37/100. The biggest problem is excessive JavaScript execution time, which takes 24.1 seconds for the page to become fully interactive and blocks user interactions for 3.5 seconds. The site is loading 268 KiB of unused JavaScript code and suffering from forced reflows that cause layout thrashing. Reducing JavaScript bundle sizes, removing unused code, and optimizing the React components could improve the score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
268 KiB of unused JavaScript is blocking the main thread and delaying LCP by 300ms.
How to Fix:
Use Next.js dynamic imports to code-split components that aren't immediately needed. Analyze the three largest chunks (0zk_9ift81y8s.js, 0byoph_9e~gjc.js, 0nibsyc31cdcm.js) with webpack-bundle-analyzer. Remove or defer unused third-party libraries until user interaction.
Fix Forced Reflow Issues
High Impact+20 points estimatedWhy It Matters:
763ms of forced reflows are causing severe main thread blocking and contributing to the 3.5s Total Blocking Time.
How to Fix:
Batch DOM reads and writes in your React components to avoid layout thrashing. Use React's useLayoutEffect instead of useEffect for DOM measurements. Cache element dimensions and avoid reading offsetWidth/offsetHeight in render loops.
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
Remove Unused Code and Modernize JavaScript
335 KiB of unused JavaScript and 57 KiB of legacy polyfills unnecessarily increase bundle size.
Implement Efficient Caching Strategy
Poor cache lifetimes waste 242 KiB on repeat visits, directly impacting LCP by 150ms.
Optimize Third-Party JavaScript Loading
Third-party scripts consume 2.2s execution time and block main thread with 1,055ms Total Blocking Time.
Fix Forced Reflow Issues
72ms of forced reflows are blocking the main thread and degrading user interaction responsiveness.