LCP
Largest Contentful Paint
11.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Unused JavaScript Bundle
How to optimize mghost.pl
Optimize Unused JavaScript Bundle
High Impact+20 points estimated
Why It Matters
358KB of unused JavaScript is adding 2.4 seconds to LCP and blocking main thread execution.
How to Fix
Enable Nuxt's tree-shaking by setting 'build.extractCSS: true' in nuxt.config.js. Implement dynamic imports for heavy components using Vue's defineAsyncComponent(). Move Google Analytics to a separate worker thread or use Nuxt's @nuxtjs/gtm module for better performance. Split vendor bundles using Nuxt's build.splitChunks configuration.
0Needs Improvement
What This Score Means
A score of 50 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
230ms
Needs Improvement
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 poor performance with a score of 50/100, indicating significant issues that hurt user experience. The biggest problem is render-blocking CSS files that are preventing the page from loading quickly, causing an extremely slow Largest Contentful Paint of 11.6 seconds and delaying first content visibility to 7.8 seconds. The site is also loading 358 KB of unused JavaScript and serving oversized images with poor caching, which compounds the loading delays. Fixing the render-blocking resources alone could improve loading times by over 1 second, while optimizing unused code and implementing proper image sizing could dramatically boost the performance score.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+25 points estimatedWhy It Matters:
Critical CSS files are blocking initial render for 1.2 seconds, severely delaying both FCP and LCP.
How to Fix:
Inline critical CSS in your Nuxt config using the 'css' property for above-the-fold styles. Use Nuxt's built-in code splitting by moving non-critical styles to component-level <style> blocks. Configure the build process to defer loading of unused CSS files like cart.y9TWX9T0.css and configure.CUv6LAjM.css which are 100% unused.
Implement Responsive Image Optimization
Medium Impact+8 points estimatedWhy It Matters:
The hero image is oversized by 41KB and has insufficient caching, contributing to poor LCP performance.
How to Fix:
Use Nuxt's @nuxt/image module to automatically generate responsive images with proper srcset. Configure image caching headers to extend beyond 60 seconds - set cache-control to 'public, max-age=31536000' for static images. Optimize the hero image dimensions to match its display size (364x364 instead of 700x700) in your image processing pipeline.
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
Implement Responsive Image Optimization
The hero image is oversized by 41KB and has insufficient caching, contributing to poor LCP performance.
Eliminate Render-Blocking CSS
Critical CSS files are blocking initial render for 1.2 seconds, severely delaying both FCP and LCP.
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.