LCP
Largest Contentful Paint
11.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Main Thread Blocking Time
How to optimize eververse.ai
Next.js SiteScore: 39/100Analyzed February 2026
Reduce Main Thread Blocking Time
High Impact+20 points estimated
Why It Matters
JavaScript execution blocks the main thread for 10.5 seconds, creating 4.34 seconds of total blocking time.
How to Fix
Break up long-running tasks in your Next.js components using React's time-slicing with startTransition() or useDeferredValue(). Move heavy computations to Web Workers. Optimize the large JavaScript bundles identified in bootup-time audit by reducing bundle sizes and deferring non-essential scripts.
0Poor
What This Score Means
A score of 39 falls in the "Poor" 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
668ms
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 severe performance issues with a critically low score of 39/100. The biggest problem is an enormous amount of unused JavaScript (1,636 KiB) that's blocking the page from becoming interactive, causing the Largest Contentful Paint to take a painful 11.9 seconds and Total Blocking Time to reach 4.3 seconds. The site is loading massive vendor libraries like Excalidraw (857 KB) that are barely being used, while legacy JavaScript polyfills and render-blocking CSS files are further slowing down the initial page load. Removing unused code, code-splitting JavaScript bundles, and optimizing the build process could dramatically improve performance by over 30 points and reduce load times by several seconds.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
1,636 KiB of unused JavaScript is blocking LCP by 2.85 seconds and preventing user interactions.
How to Fix:
Use Next.js dynamic imports to code-split the massive Excalidraw bundle (857KB unused). Implement lazy loading for the drawing component only when users need it. Run 'npx next bundle-analyzer' to identify other unused chunks and split them appropriately.
Eliminate Render-Blocking CSS Resources
High Impact+18 points estimatedWhy It Matters:
Two CSS files are delaying initial page render and LCP by 490ms in the critical path.
How to Fix:
Inline critical above-the-fold CSS directly in your Next.js page components using styled-jsx or CSS-in-JS. Use Next.js dynamic imports with 'ssr: false' for non-critical styles. Move remaining CSS to load after first paint using media='print' onload technique.
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 Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
Frequently Asked Questions
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