LCP
Largest Contentful Paint
30.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Code
How to optimize pay.hotmart.com
Nuxt SiteScore: 35/100Analyzed February 2026
Eliminate Unused JavaScript Code
High Impact+25 points estimated
Why It Matters
2,251 KiB of unused JavaScript is blocking rendering and delaying LCP by 16+ seconds.
How to Fix
Use Nuxt's tree-shaking by enabling build.analyze to identify unused code. Split large bundles with dynamic imports using defineAsyncComponent(). Remove duplicate DVuz4S0k.js files from different domains. Configure webpack-bundle-analyzer to audit bundle composition.
0Poor
What This Score Means
A score of 35 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
293ms
Needs Improvement
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 35/100. The biggest problem is massive JavaScript bloat - the site loads over 2.2MB of unused JavaScript code that takes nearly 4 seconds to parse and execute, causing your First Contentful Paint to crawl at 5.7 seconds and Largest Contentful Paint to reach an abysmal 30.8 seconds. The site is downloading the same large JavaScript files multiple times and using outdated code that modern browsers don't need. Removing unused JavaScript, eliminating duplicate files, and modernizing the codebase could dramatically improve performance by over 16 seconds and transform the user experience from unusable to acceptable.
Other Optimization Recommendations
Optimize Main Thread JavaScript Processing
High Impact+20 points estimatedWhy It Matters:
5.7 seconds of main thread blocking creates 1,220ms Total Blocking Time, severely impacting user interactions.
How to Fix:
Implement code splitting in nuxt.config.js with splitChunks optimization. Use Vue's defineAsyncComponent for heavy components. Move non-critical JavaScript to web workers. Defer Facebook Pixel and tracking scripts until after page load using Nuxt's useHead with defer: true.
Fix Element Render Delay
High Impact+18 points estimatedWhy It Matters:
4.39 seconds of element render delay is the primary cause of your 30.8s LCP score.
How to Fix:
Remove render-blocking CSS by inlining critical styles in nuxt.config.js using @nuxtjs/critters. Preconnect to external origins (identification.hotmart.com, launcher.hotmart.com) using link rel='preconnect'. Set explicit width='80' height='80' on product images to prevent layout shifts.
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