LCP
Largest Contentful Paint
3.4s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Inline Critical CSS Bundle
How to optimize landing.dev.opencals.com
Inline Critical CSS Bundle
High Impact+8 points estimated
Why It Matters
Render-blocking CSS delays LCP and FCP by 100ms each, preventing critical content from displaying.
How to Fix
Use Next.js built-in CSS optimization by moving critical styles to a separate file. Enable experimental.optimizeCss in next.config.js. Consider inlining above-the-fold styles using next-critical-css plugin.
0Needs Improvement
What This Score Means
A score of 78 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
452ms
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 moderate performance issues with a score of 78/100. The biggest problem is excessive JavaScript execution time (2.9 seconds), which is blocking the main thread and causing a 500ms delay in user interactions. The site is loading 133 KiB of unused JavaScript code, particularly in React components, which could be eliminated through code splitting and lazy loading. Optimizing these JavaScript issues and addressing the render-blocking CSS could improve loading times by several hundred milliseconds and significantly enhance the user experience.
Other Optimization Recommendations
Reduce Unused JavaScript Bundles
High Impact+12 points estimatedWhy It Matters:
133 KiB of unused JavaScript delays LCP by 150ms and blocks the main thread for 2.9 seconds.
How to Fix:
Configure Next.js dynamic imports for unused chunks like e606befc9e7f8831.js. Use webpack-bundle-analyzer to identify dead code. Enable tree shaking in next.config.js with experimental.optimizePackageImports for better code splitting.
Fix Forced Reflow Issues
Medium Impact+6 points estimatedWhy It Matters:
JavaScript queries of geometric properties after DOM changes cause 63ms of unnecessary layout work.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing. Use React's useLayoutEffect instead of useEffect for DOM measurements. Cache geometric properties and use ResizeObserver for efficient dimension tracking.
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
Optimize JavaScript Execution Performance
7.6 seconds of JavaScript execution time creates 2.3 seconds of blocking time, preventing user interactions.
Modernize JavaScript Build Target
Legacy JavaScript polyfills add 13 KiB and 150ms to LCP for features modern browsers support natively.
Remove Unused JavaScript Code
140 KiB of unused JavaScript delays LCP by 950ms and blocks user interactions.
Fix Forced Reflow Issues
DOM queries after style changes cause 206ms of forced reflows, degrading rendering performance.