LCP
Largest Contentful Paint
11.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Large Image Assets
How to optimize staging.app.tailzaar.com
Optimize Large Image Assets
High Impact+25 points estimated
Why It Matters
The 1MB gradient image and hero image are causing an 11.9s LCP and represent 42% of total page weight.
How to Fix
Compress ic_gradient.png (1MB) and hero_en_sm.png (276KB) using next/image with quality={75}. Convert to WebP format using Next.js automatic optimization. Add priority={true} to the hero image and fetchpriority='high' attribute to make it discoverable immediately.
0Needs Improvement
What This Score Means
A score of 64 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
168ms
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 64/100, primarily due to extremely slow loading times that make users wait nearly 12 seconds before the page becomes interactive. The biggest issue is an enormous 1MB gradient image (ic_gradient.png) that's bloating the total page size to over 3MB, combined with excessive unused JavaScript that's wasting 159KB of bandwidth. The site would benefit dramatically from compressing or replacing that large gradient image, removing unused code, and implementing proper caching for API documents, which could easily improve the score by 25+ points and cut loading times in half.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
159KB of unused JavaScript is delaying LCP by 750ms and blocking page interactivity.
How to Fix:
Use Next.js dynamic imports to code-split large chunks like 0zcrz0mqu33pw.js (76KB unused). Implement React.lazy() for components not needed on initial render. Configure Next.js bundle analyzer to identify and remove dead code from your build.
Implement Resource Caching Strategy
Medium Impact+12 points estimatedWhy It Matters:
API document downloads have zero cache lifetime, wasting 317KB on repeat visits and slowing subsequent loads.
How to Fix:
Add Cache-Control headers to your staging-api responses with max-age=86400 for document downloads. Configure Next.js to cache static assets with proper headers. Add preconnect link to staging-api.tailzaar.com in your Next.js _document.js to save 300ms on first API calls.
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.