LCP
Largest Contentful Paint
4.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Bundle
How to optimize koditt.nl
Eliminate Unused JavaScript Bundle
High Impact+18 points estimated
Why It Matters
455 KiB of unused JavaScript delays LCP by 450ms and blocks main thread execution.
How to Fix
Configure Next.js to use dynamic imports for components not needed on initial load. Remove or defer Google Tag Manager and Analytics scripts until after page interaction. Use Next.js built-in bundle analyzer to identify and tree-shake unused code from your chunks.
0Needs Improvement
What This Score Means
A score of 56 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
416ms
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/WordPress site has poor performance with a score of 56/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (455 KiB) from tracking scripts and large bundles, which is causing a very slow Time to Interactive of 10.9 seconds and blocking the main thread for 8.4 seconds. The site is also suffering from forced reflows that waste over 500ms of processing time, legacy JavaScript polyfills that aren't needed for modern browsers, and inefficient caching of logo images. Removing unused JavaScript, updating the build process to avoid unnecessary polyfills, and fixing the DOM manipulation issues could improve the performance score by 30+ points and dramatically reduce loading times.
Other Optimization Recommendations
Fix Forced Reflow Issues
High Impact+12 points estimatedWhy It Matters:
521ms of forced reflows block the main thread and prevent smooth user interactions.
How to Fix:
Batch DOM reads and writes in your React components using useLayoutEffect sparingly. Avoid reading layout properties like offsetWidth after DOM changes. Use CSS transforms instead of changing layout properties for animations in your Next.js components.
Add Preconnect to External Origins
Medium Impact+8 points estimatedWhy It Matters:
Missing preconnect to cms.koditt.dev delays LCP by 323ms due to late connection establishment.
How to Fix:
Add <link rel='preconnect' href='https://cms.koditt.dev'> to your Next.js Head component. Include DNS prefetch for Google services. Limit preconnect hints to critical origins only to avoid connection overhead.
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.
Add Preconnect for CMS Origin
Missing preconnect to cms.koditt.dev costs 321ms in LCP performance due to connection setup delays.