LCP
Largest Contentful Paint
4.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Forced Reflow Performance
How to optimize koditt.nl
Optimize Forced Reflow Performance
High Impact+18 points estimated
Why It Matters
639ms of forced reflows block the main thread and prevent user interactions during page load.
How to Fix
Batch DOM reads and writes in your React components using useLayoutEffect instead of useEffect for layout measurements. Cache geometric calculations instead of repeatedly querying offsetWidth/height. Use CSS transforms instead of changing layout properties for animations.
0Needs Improvement
What This Score Means
A score of 63 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
383ms
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 website has poor performance with a score of 63/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking 5.8 seconds of main-thread work, which is blocking user interactions and causing a slow Time to Interactive of 6.5 seconds. The site is loading nearly 500KB of unused JavaScript code that could be removed or deferred, and there are performance-killing "forced reflows" where the browser has to repeatedly recalculate page layouts. Reducing the JavaScript bundle size, eliminating unused code, and fixing the layout thrashing could dramatically improve loading speed and user responsiveness.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
497 KiB of unused JavaScript delays LCP by 900ms and blocks user interactions for 550ms.
How to Fix:
Use Next.js dynamic imports to code-split large components. Remove unused Google Analytics tracking code or defer it with next/script strategy='afterInteractive'. Configure webpack-bundle-analyzer to identify and eliminate dead code in your Next.js build process.
Fix Unused Preconnect Hints
Medium Impact+8 points estimatedWhy It Matters:
Unnecessary preconnect hints to Cookiebot waste browser resources and slow down critical resource loading.
How to Fix:
Remove the preconnect links to consent.cookiebot.com and consentcdn.cookiebot.com from your Next.js Head component since they're not being used. Add preconnect to your WordPress CMS domain (cms.koditt.dev) instead to speed up image loading.
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
Eliminate Legacy JavaScript Polyfills
Unnecessary polyfills add 14KB and delay LCP by 150ms for modern browsers.
Optimize JavaScript Execution Performance
JavaScript execution blocks the main thread for 2.8 seconds, creating a 770ms potential input delay.
Remove Unused JavaScript Code
Unused JavaScript wastes 11MB of bandwidth and delays LCP by 55.8 seconds while blocking interactions.
Optimize JavaScript Bundle Splitting
Large JavaScript bundles are causing 1.6s execution time and 200ms blocking time, severely impacting interactivity.