LCP
Largest Contentful Paint
3.9s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Execution Time
How to optimize nucleify.io
Optimize JavaScript Execution Time
High Impact+15 points estimated
Why It Matters
Script evaluation takes 980ms of main thread time, blocking user interactions and delaying TTI to 4.6 seconds.
How to Fix
Use Nuxt's code splitting with dynamic imports for heavy components. Move non-critical JavaScript to web workers using Nuxt's worker plugin. Implement server-side rendering optimization by reducing hydration payload with selective hydration using <ClientOnly> wrapper.
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
180ms
Good
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 Nuxt/Vue website has decent performance with a score of 80/100, but there's significant room for improvement in Core Web Vitals. The biggest problem is excessive JavaScript processing that's blocking the main thread for 2.6 seconds, causing your Largest Contentful Paint to lag at 3.9 seconds and delaying user interactions until 4.6 seconds. The site is loading 171 KiB of unused JavaScript code, with some files being nearly 98% unnecessary, which could save 600ms in loading time if removed. Reducing JavaScript bundle sizes, removing unused code, and fixing forced reflows caused by layout queries would dramatically improve your site's responsiveness and user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
Unused JavaScript wastes 171KB of bandwidth and delays LCP by 600ms while blocking main thread execution.
How to Fix:
Use Nuxt's bundle analyzer to identify dead code in your chunks. Configure tree-shaking in nuxt.config.js with build.optimization settings. Split large components using dynamic imports with defineAsyncComponent() for Vue components that aren't immediately needed.
Eliminate Forced Layout Reflows
Medium Impact+8 points estimatedWhy It Matters:
Forced reflows cause 82ms of unnecessary layout calculations, degrading user experience and blocking main thread.
How to Fix:
Batch DOM reads and writes in your Vue components by using nextTick() for DOM queries. Replace direct style property access with CSS classes in your Nuxt components. Use Vue's reactive refs instead of accessing offsetWidth/offsetHeight directly in component methods.
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 Nuxt Speed Tests
Nuxt Performance Resources
Fix Forced Reflow Issues
Forced reflows cause 91ms of layout thrashing, degrading user experience and potentially affecting CLS scores.
Reduce Main Thread Blocking Time
JavaScript execution blocks the main thread for 2.2 seconds, preventing user interactions and delaying page responsiveness.
Eliminate Unused JavaScript Code
Unused JavaScript accounts for 273 KiB of wasted bytes, delaying LCP by 1.35 seconds and blocking page rendering.
Eliminate Forced Layout Reflows
Forced reflows cause 82ms of unnecessary layout calculations, degrading user experience and blocking main thread.