LCP
Largest Contentful Paint
11.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Multiple Page Redirects
How to optimize id.preview..febbac5b.1341.4f9a.93d5.ea71608f56bb.lovable.app
Eliminate Multiple Page Redirects
High Impact+25 points estimated
Why It Matters
Multiple redirects add 780ms delay before page content even begins loading.
How to Fix
Update the redirect chain from id-preview--febbac5b-1341-4f9a-93d5-ea71608f56bb.lovable.app/auth to directly point to the final destination. In Next.js, configure proper redirects in next.config.js using the redirects() function to avoid redirect chains.
0Poor
What This Score Means
A score of 46 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
323ms
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 Next.js site has poor performance with a score of 46/100, primarily due to excessive JavaScript causing severe loading delays. The biggest problem is outdated JavaScript code (75KB of legacy polyfills) that's unnecessarily slowing down your Largest Contentful Paint by 11.6 seconds - nearly triple the recommended time. Multiple page redirects add another 780ms delay, while 616KB of unused JavaScript from tracking scripts (Google Analytics, Facebook Pixel, TikTok) further bloats the page. Modernizing your JavaScript build process to remove unnecessary polyfills and reducing third-party scripts could improve your score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Remove Legacy JavaScript Polyfills
High Impact+20 points estimatedWhy It Matters:
75 KiB of unnecessary polyfills for modern browsers slow LCP by 400ms.
How to Fix:
Update your build configuration to target modern browsers only. In Next.js, set target: 'es2017' in next.config.js and remove @babel/plugin-transform-regenerator, @babel/plugin-transform-classes, and other legacy transforms. Use browserslist to specify modern browser support.
Reduce Unused JavaScript Bundle Size
High Impact+18 points estimatedWhy It Matters:
616 KiB of unused JavaScript wastes network bandwidth and delays page interactivity.
How to Fix:
Implement dynamic imports for Google Analytics, Facebook Pixel, and TikTok tracking scripts to load them only when needed. Use Next.js dynamic imports with ssr: false for client-side only scripts. Enable tree-shaking by using ES modules and avoiding default imports from large libraries.
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 Next.js Speed Tests
Next.js Performance Resources
Reduce Unused JavaScript Bundle Size
616 KiB of unused JavaScript wastes network bandwidth and delays page interactivity.
Remove Legacy JavaScript Polyfills
75 KiB of unnecessary polyfills for modern browsers slow LCP by 400ms.
Optimize JavaScript Bundle Minification
549 KiB of unminified JavaScript is causing excessive parsing time and blocking user interactions.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial page render for 1.77 seconds, directly delaying both FCP and LCP.