LCP
Largest Contentful Paint
8.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Render-Blocking CSS Resources
How to optimize landing.dev.opencals.com
Fix Render-Blocking CSS Resources
High Impact+15 points estimated
Why It Matters
CSS files are blocking initial page render and delaying both FCP and LCP by 300ms.
How to Fix
Move critical CSS inline in your Next.js _document.js file for above-the-fold content. Use next/dynamic with ssr: false for non-critical components. Defer loading of the 8d8d0ec3b669f778.css file or split it into critical and non-critical parts using CSS-in-JS solutions like styled-components.
0Needs Improvement
What This Score Means
A score of 51 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
528ms
Poor
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/React site has poor performance with a score of 51/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking over 3 seconds, which is blocking the main thread and causing your Largest Contentful Paint to reach a very slow 8.3 seconds. Your site is loading 133 KiB of unused JavaScript code that could be eliminated, and render-blocking CSS is further delaying page display by 320ms. Reducing your JavaScript bundle size, removing unused code, and deferring non-critical scripts could improve your score by 30+ points and make the site much more responsive for users.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
133 KiB of unused JavaScript is delaying LCP by 900ms and blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks. Implement dynamic imports for heavy components that aren't immediately needed. Remove or lazy load the 99.9% unused code in e606befc9e7f8831.js chunk. Use tree shaking to eliminate dead code from your build.
Reduce JavaScript Execution Time
High Impact+20 points estimatedWhy It Matters:
3.1 seconds of JavaScript execution is blocking the main thread and creating 790ms of Total Blocking Time.
How to Fix:
Break up long-running tasks in d308e9b8ce2ef91c.js using React.lazy() and Suspense for code splitting. Implement time-slicing for heavy computations using scheduler.postTask() or setTimeout. Move Microsoft Clarity script to load after page interaction to reduce forced reflows.
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.