LCP
Largest Contentful Paint
17.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Massive Image Payloads
How to optimize super86.cc
Optimize Massive Image Payloads
High Impact+25 points estimated
Why It Matters
The 2.8MB notification banner image alone causes 5.4 second LCP delay and consumes excessive bandwidth.
How to Fix
Compress the notification_us.png from 2.8MB to under 200KB using TinyPNG or ImageOptim. In your Nuxt config, add @nuxtjs/imagemin module for automatic compression. Convert large images to WebP format and implement responsive images with nuxt/image module using sizes and srcset attributes.
0Poor
What This Score Means
A score of 42 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
257ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.03
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Nuxt/Vue website has severe performance issues with a score of only 42/100, indicating a poor user experience. The biggest problem is an extremely slow Largest Contentful Paint of 17.1 seconds, primarily caused by a massive 2.8MB notification image that's blocking the page render and eating up bandwidth. The site is also loaded with 419KB of unused JavaScript and 231KB of unused CSS that could be eliminated, plus render-blocking stylesheets that delay the initial paint by over a second. Optimizing or removing that huge notification image, cleaning up unused code, and implementing proper caching could dramatically improve the score by 40+ points and transform the user experience from unusable to acceptable.
Other Optimization Recommendations
Eliminate Unused CSS and JavaScript
High Impact+18 points estimatedWhy It Matters:
650KB of unused code blocks rendering for 2.7 seconds and wastes 419KB of JavaScript execution time.
How to Fix:
Enable CSS tree-shaking in your Nuxt build config by setting css: { extract: { ignoreOrder: true } }. Remove unused Vant UI components - only import specific components you need instead of the entire library. Use webpack-bundle-analyzer to identify and eliminate unused JavaScript chunks in your Vue components.
Fix LCP Image Discovery Issues
High Impact+12 points estimatedWhy It Matters:
The LCP image isn't discoverable in initial HTML and lacks priority hints, delaying first paint by 8.5 seconds.
How to Fix:
Add explicit width='241' height='196' attributes to your lock.webp image in the Vue template. Use Nuxt's nuxt-img component with priority='true' and preload='true' for above-the-fold images. Move critical images from lazy-loaded components to the initial server-rendered HTML.
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 LCP Image Discovery Issues
The LCP image isn't discoverable in initial HTML and lacks priority hints, delaying first paint by 8.5 seconds.
Eliminate Unused CSS and JavaScript
650KB of unused code blocks rendering for 2.7 seconds and wastes 419KB of JavaScript execution time.
Implement Efficient Asset Caching
66 KiB of static assets have no cache headers, missing opportunities to improve repeat visit performance and LCP by 500ms.
Minimize Main Thread Blocking Time
8.3 seconds of main thread work creates 1,910ms Total Blocking Time, severely impacting user interaction responsiveness.