Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize mp2.frontend.dev.jewelprotech.com
491 KiB of unused JavaScript delays LCP by 900ms and blocks the main thread unnecessarily.
Use Nuxt's tree-shaking by importing only specific functions instead of entire libraries. Enable Nuxt's experimental payload extraction with 'experimental: { payloadExtraction: false }'. Remove or lazy-load Google Analytics until after user interaction. Split large vendor bundles using Nuxt's splitChunks configuration.
A score of 70 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Nuxt/Vue website has significant performance issues with a score of 70/100. The biggest problem is excessive unused JavaScript and CSS that's blocking the initial page render, causing your First Contentful Paint to take 2.7 seconds and Largest Contentful Paint to reach 4.7 seconds. The site is loading nearly 500KB of unused JavaScript and 55KB of unused CSS, which could save up to 1.2 seconds in loading time if optimized. Implementing code splitting, removing unused dependencies, and deferring non-critical resources would dramatically improve your Core Web Vitals and user experience.
Why It Matters:
Render-blocking CSS delays First Contentful Paint by 900ms and creates poor user experience.
How to Fix:
Move critical above-the-fold styles inline using Nuxt's 'css' configuration. Defer non-critical CSS files like Element UI vendor styles using 'preload' with media='print' onload='this.media="all"'. Use Nuxt's built-in CSS optimization with 'optimization.splitChunks.cacheGroups.styles'.
Why It Matters:
2.7 seconds of main thread work creates 270ms Total Blocking Time, preventing smooth user interactions.
How to Fix:
Implement Nuxt's server-side rendering more effectively by moving client-side logic to server middleware. Use Vue's 'async' components for heavy UI elements like modals and carousels. Break up large JavaScript tasks using 'nextTick()' or 'requestIdleCallback()' for non-critical operations.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Nuxt Speed Tests
Critical CSS is blocking FCP by 450ms, delaying initial page render.
The 74 KiB animated banner GIF can be reduced by 50% using modern video formats.
Removing 909 KiB of unused resources will improve LCP by 1.2 seconds and FCP by 1.15 seconds.
Missing image dimensions cause 0.158 CLS score, creating jarring content jumps during loading.