LCP
Largest Contentful Paint
9.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update Build Target for Modern Browsers
How to optimize staging.app.tailzaar.com
Update Build Target for Modern Browsers
Medium Impact+8 points estimated
Why It Matters
Legacy JavaScript polyfills add 13 KiB of unnecessary code that delays LCP by 150ms.
How to Fix
Update your Next.js browserslist config to target modern browsers only (last 2 versions). Set your Babel preset to use ES2020+ features like Array.at, Object.hasOwn, and String.trimStart natively. Remove core-js polyfills from your build configuration.
0Needs Improvement
What This Score Means
A score of 66 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
154ms
Good
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 66/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 9.9 seconds, primarily caused by a background image that isn't discoverable in the initial HTML and lacks proper optimization. The site is also bloated with 159 KiB of unused JavaScript that could be removed or deferred, and images are oversized and poorly compressed, wasting an additional 138 KiB of bandwidth. Fixing the LCP image discovery, removing unused code, and optimizing images could dramatically improve load times and boost the performance score by 30+ points.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
159 KiB of unused JavaScript is delaying LCP by 800ms and blocking page interactivity.
How to Fix:
Analyze your Next.js bundle with webpack-bundle-analyzer to identify unused code. Implement dynamic imports for non-critical components using React.lazy() and Suspense. Split large chunks by routes and defer loading of admin/dashboard components until needed.
Preconnect to Critical Third-Party Origins
Medium Impact+12 points estimatedWhy It Matters:
Missing preconnect hints to staging-api.tailzaar.com waste 300ms on connection setup.
How to Fix:
Add <link rel='preconnect' href='https://staging-api.tailzaar.com'> to your Next.js _document.js Head component. Implement priority hints for your LCP background image by converting from CSS background to <Image> component with priority prop. Add fetchpriority='high' to critical images.
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
Optimize Image Delivery Performance
Images are oversized and poorly compressed, wasting 613KB of bandwidth and slowing page load.
Eliminate Unused JavaScript Code
156KB of unused JavaScript is blocking page load and delaying LCP by 1.2 seconds.
Fix Largest Contentful Paint Issue
LCP is critically slow at 8.7 seconds, severely impacting user experience and Core Web Vitals score.
Preconnect to Critical Third-Party Origins
Missing preconnect hints to staging-api.tailzaar.com waste 300ms on connection setup.