LCP
Largest Contentful Paint
14.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Redirect Chain
How to optimize nucleify.io
Eliminate Redirect Chain
High Impact+12 points estimated
Why It Matters
The redirect from /pl/home to /pl/home/ wastes 750ms and delays both FCP and LCP significantly.
How to Fix
Update your Nuxt router configuration to use trailing slashes consistently. Add a redirect rule in nuxt.config.ts using the redirect module or update internal links to point directly to /pl/home/. Configure your server to handle trailing slash redirects at the server level.
0Needs Improvement
What This Score Means
A score of 53 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
126ms
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 site has poor performance with a concerning score of 53/100. The biggest problem is a page redirect that's adding 750ms of unnecessary delay, combined with 171 KiB of unused JavaScript that's wasting another 750ms of load time. Your users are waiting over 14 seconds to see meaningful content (Largest Contentful Paint), which is far too slow for modern web standards. Fixing the redirect issue and removing unused JavaScript from your Nuxt bundles could save over 1.5 seconds and dramatically improve your Core Web Vitals scores.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
171KB of unused JavaScript delays LCP by 750ms and increases bundle parse time unnecessarily.
How to Fix:
Use Nuxt's built-in code splitting by converting large components to dynamic imports with defineAsyncComponent(). Enable tree-shaking in your build config and remove unused dependencies. Split large chunks like Cx1m70_d.js using dynamic imports for route-based code splitting.
Fix Forced Layout Reflows
Medium Impact+8 points estimatedWhy It Matters:
214ms of forced reflows block the main thread and degrade user interaction responsiveness.
How to Fix:
Batch DOM reads and writes by reading all geometric properties first, then making style changes. Use CSS transforms instead of changing layout properties. In your Nuxt components, move DOM measurements to requestAnimationFrame callbacks to avoid synchronous 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 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.