LCP
Largest Contentful Paint
6.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS Resources
How to optimize shantitravel.git.optimization.120326.shantitravels.projects.vercel.app
Eliminate Render-Blocking CSS Resources
High Impact+25 points estimated
Why It Matters
CSS files are blocking initial render and delaying First Contentful Paint by 900ms.
How to Fix
Use Next.js built-in CSS optimization by importing only critical CSS in _app.js. Split non-critical CSS into separate components and load them asynchronously. Consider inlining critical above-the-fold CSS using next/head for immediate rendering.
0Poor
What This Score Means
A score of 40 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
1914ms
Poor
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 severe performance issues with a score of 40/100. The biggest problem is render-blocking CSS files that are preventing the page from loading quickly, delaying First Contentful Paint by 890ms and contributing to an extremely slow Largest Contentful Paint of 6.9 seconds. The site is also suffering from excessive JavaScript execution time (3.4 seconds) and forced reflows that are blocking user interactions for over 1.3 seconds. Deferring non-critical CSS, reducing unused JavaScript (100KB can be removed), and optimizing the main thread work could improve the score by 30+ points and dramatically enhance user experience, especially on mobile devices.
Other Optimization Recommendations
Reduce JavaScript Execution Time
High Impact+20 points estimatedWhy It Matters:
JavaScript execution takes 3.4 seconds and causes 1.3 seconds of Total Blocking Time, preventing user interactions.
How to Fix:
Code-split your Next.js application using dynamic imports for non-critical components. Remove unused JavaScript by analyzing bundle with @next/bundle-analyzer. Defer heavy JavaScript operations using React.lazy() and Suspense for better performance.
Optimize LCP Image Loading
High Impact+15 points estimatedWhy It Matters:
The hero image has 3.5 seconds of resource load delay, significantly impacting Largest Contentful Paint.
How to Fix:
Use Next.js Image component with priority prop for the hero image to preload it. Optimize image compression and serve responsive sizes using Next.js automatic image optimization. Consider using a CDN with better caching strategies for faster image delivery.
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
Fix Layout Shift Issues
CLS score of 0.123 caused by carousel and cookie banner shifting content during load.
Reduce JavaScript Bundle Size
Unused JavaScript totals 1.6MB and blocks main thread for 4.7 seconds, causing 630ms input delay.
Optimize Large Image Assets
Images consume over 22MB with the largest being 4.5MB, severely impacting LCP at 8.3 seconds.
Fix Critical Element Render Delay
The LCP element (H1 heading) has a massive 4.3 second render delay, severely impacting page load performance.