LCP
Largest Contentful Paint
3.6s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize nexus.thinklance.app
Remove Unused JavaScript Code
Medium Impact+8 points estimated
Why It Matters
114 KiB of unused JavaScript is increasing bundle size and delaying LCP by 300ms.
How to Fix
Configure Next.js bundle analyzer to identify dead code in your chunks. Remove unused Google Analytics features and implement gtag with selective imports. Use Next.js tree-shaking by ensuring proper ES6 imports and enabling the experimental 'esmExternals' config option.
0Needs Improvement
What This Score Means
A score of 80 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
87ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has concerning performance issues with a score of 80/100, but several critical problems are hiding behind that score. The biggest issue is an extremely slow element render delay of over 8 seconds, which is causing your Speed Index to hit a poor 13 seconds and making the page feel unresponsive to users. Your site is also loading 114 KB of unused JavaScript (including Google Analytics and React components) and has render-blocking CSS files that are delaying initial page display by nearly a second. Removing unused code, deferring non-critical JavaScript, and optimizing your CSS delivery could dramatically improve load times and user experience.
Other Optimization Recommendations
Fix Element Render Delay
High Impact+15 points estimatedWhy It Matters:
Your LCP element has an extreme 8.2 second render delay, severely impacting user experience and Core Web Vitals.
How to Fix:
Move critical CSS inline or use Next.js styled-jsx to prevent render-blocking. Ensure the LCP text element renders immediately after HTML loads. Consider server-side rendering the hero section content to eliminate client-side delays.
Eliminate Render-Blocking Resources
High Impact+12 points estimatedWhy It Matters:
CSS and JavaScript files are blocking initial render, delaying LCP by 900ms and preventing fast page loads.
How to Fix:
Use Next.js dynamic imports for non-critical CSS chunks. Move the Cloudflare email-decode script to load asynchronously with next/script component and strategy='afterInteractive'. Inline critical CSS for above-the-fold content using Next.js CSS-in-JS solutions.
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
Implement Font Display Optimization
Custom fonts block text rendering for 1.6 seconds causing invisible text during page load.
Optimize Hero Image Loading
LCP image takes 9.7 seconds to load due to lazy loading and oversized dimensions.
Fix Unsized Image Layout Shifts
Unsized images cause 0.428 CLS score with major layout shifts affecting user experience.
Eliminate Render-Blocking Resources
CSS and JavaScript files are blocking initial render, delaying LCP by 900ms and preventing fast page loads.