LCP
Largest Contentful Paint
2.8s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Code
How to optimize bhajans.happythoughts.in
Eliminate Unused JavaScript Code
High Impact+3 points estimated
Why It Matters
156KB of unused JavaScript is delaying LCP by 900ms and blocking page interactivity.
How to Fix
Use Next.js bundle analyzer to identify unused code in chunks. Implement dynamic imports for components that aren't immediately needed. Split large chunks using Next.js code splitting and only load JavaScript when required.
0Good
What This Score Means
A score of 91 falls in the "Good" 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
92ms
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 good performance with a score of 91/100, but there's significant room for improvement in loading speed. The biggest issue is excessive unused JavaScript (156 KiB of wasted code) that's slowing down your Largest Contentful Paint, combined with render-blocking CSS that delays initial page rendering by 150ms. Your site is also serving an oversized logo image that could be 55 KiB smaller with proper compression and modern formats like WebP. Cleaning up the unused JavaScript code and optimizing image delivery would make the most meaningful impact on user experience, particularly for the Speed Index which is currently at a slow 6.0 seconds.
Other Optimization Recommendations
Fix Render Blocking CSS
High Impact+2 points estimatedWhy It Matters:
CSS file is blocking initial page render and delaying both LCP and FCP by 150ms.
How to Fix:
Use Next.js built-in CSS optimization by importing critical CSS inline. Move non-critical styles to load after first paint using dynamic imports. Ensure CSS chunks are properly code-split by route in your Next.js build configuration.
Optimize Logo Image Delivery
Medium Impact+1 point estimatedWhy It Matters:
Logo image is oversized, unoptimized, and lacks proper dimensions causing layout shifts.
How to Fix:
Use Next.js Image component with explicit width and height props. Convert logo.png to WebP format and serve appropriately sized version (177x168 instead of 431x409). Set proper cache headers for the logo asset to improve repeat visit performance.
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 Logo Image Delivery
Logo image is oversized, unoptimized, and lacks proper dimensions causing layout shifts.
Fix Render Blocking CSS
CSS file is blocking initial page render and delaying both LCP and FCP by 150ms.
Eliminate Render-Blocking CSS
CSS file is blocking initial render and delaying both LCP and FCP by 150ms each.
Optimize Logo Image Delivery
The logo image is oversized by 51KB and uses an inefficient format, impacting perceived load time.