LCP
Largest Contentful Paint
31.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Bundle
How to optimize pay.hotmart.com
Nuxt SiteScore: 29/100Analyzed February 2026
Eliminate Unused JavaScript Bundle
High Impact+45 points estimated
Why It Matters
Unused JavaScript accounts for 2,250 KiB and delays LCP by 16.5 seconds, severely impacting user experience.
How to Fix
Implement Nuxt's code splitting with dynamic imports for non-critical components. Use Webpack Bundle Analyzer to identify unused modules in DVuz4S0k.js. Configure tree-shaking in nuxt.config.js with 'build.optimization.splitChunks' to separate vendor code and load only needed chunks per route.
0Poor
What This Score Means
A score of 29 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
575ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Nuxt/Vue site has severe performance issues with a critically low score of 29/100. The biggest problem is massive amounts of unused JavaScript (2,250 KiB of wasted code) that's blocking the page from loading efficiently, causing an extremely slow Largest Contentful Paint of 31 seconds and making the site unusable for visitors. The site is loading multiple versions of the same large JavaScript bundle and suffering from poor caching strategies, particularly with Facebook tracking scripts. Removing unused JavaScript code, implementing proper code splitting, and setting up efficient caching could dramatically improve the score by 40+ points and make the site actually functional for users.
Other Optimization Recommendations
Optimize Cache Headers Configuration
High Impact+25 points estimatedWhy It Matters:
Poor caching wastes 388 KiB on repeat visits and adds 1.4 seconds to LCP for returning users.
How to Fix:
Set long-term cache headers (1 year) for static assets like fbevents.js and product images in your server configuration. Configure Nuxt's static asset versioning with 'generate.fallback' to enable aggressive caching. Implement service worker caching for critical resources using @nuxtjs/pwa module.
Preconnect Critical Third-Party Origins
Medium Impact+15 points estimatedWhy It Matters:
Missing preconnect hints delay resource loading by up to 545ms, directly impacting LCP performance.
How to Fix:
Add preconnect hints in your Nuxt layout for critical origins: api-ip.hotmart.com, launcher.hotmart.com, and identification.hotmart.com. Use Nuxt's head() method or @nuxtjs/google-analytics to implement early connections. Limit to 4 origins maximum to avoid performance degradation.
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 Proper Caching Strategy
Static assets have only 60-second cache lifetime, missing 2MB of potential cache savings and forcing unnecessary re-downloads.
Reduce Unused JavaScript Payloads
2.7MB of unused JavaScript is blocking rendering and adding 16 seconds to LCP, with moment.js locale files being 93% unused.
Remove Page Redirects Chain
Multiple redirects are adding 25.7 seconds to your page load time, severely impacting both LCP and FCP.
Implement Efficient Resource Caching
654 KiB of resources with poor cache policies are forcing unnecessary re-downloads on repeat visits.
Frequently Asked Questions
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