LCP
Largest Contentful Paint
8.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Largest Contentful Paint Issue
How to optimize tailzaar.com
Fix Largest Contentful Paint Issue
High Impact+25 points estimated
Why It Matters
LCP is critically slow at 8.7 seconds, severely impacting user experience and Core Web Vitals score.
How to Fix
Add fetchpriority='high' to the hero image element (img.object-contain). Preconnect to api.tailzaar.com using <link rel='preconnect' href='https://api.tailzaar.com'>. Optimize hero image compression and consider using srcset for responsive delivery.
0Needs Improvement
What This Score Means
A score of 67 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
181ms
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/React site has poor performance with a score of 67/100, primarily due to an extremely slow Largest Contentful Paint of 8.7 seconds - well above the recommended 2.5 seconds. The biggest issue is the main hero image taking too long to load, which could be improved by adding fetchpriority="high" to the LCP image and establishing early connections to the api.tailzaar.com origin. Additionally, the site is loading 156KB of unused JavaScript code and has render-blocking CSS files that are delaying the initial page render by 170ms. Fixing these issues - particularly optimizing image loading and removing unused code - could improve the performance score by 15-25 points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
156KB of unused JavaScript is blocking page load and delaying LCP by 1.2 seconds.
How to Fix:
Use Next.js dynamic imports for code splitting: import dynamic from 'next/dynamic'. Analyze bundle with @next/bundle-analyzer to identify large chunks. Remove legacy JavaScript polyfills for modern features like Array.prototype.at and Object.hasOwn that have wide browser support.
Optimize Image Delivery Performance
Medium Impact+8 points estimatedWhy It Matters:
Images are oversized and poorly compressed, wasting 613KB of bandwidth and slowing page load.
How to Fix:
Configure Next.js Image component with proper sizes prop matching display dimensions. Increase compression quality from q=75 to q=60 for thumbnails. Use responsive images with multiple breakpoints to serve appropriately sized images for different screen sizes.
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.
Preconnect to Critical Third-Party Origins
Missing preconnect hints to staging-api.tailzaar.com waste 300ms on connection setup.
Update Build Target for Modern Browsers
Legacy JavaScript polyfills add 13 KiB of unnecessary code that delays LCP by 150ms.