LCP
Largest Contentful Paint
3.1s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Defer Render-Blocking CSS
How to optimize bhajans.happythoughts.in
Defer Render-Blocking CSS
High Impact+6 points estimated
Why It Matters
CSS file is blocking initial render and delaying both LCP and FCP by 150ms.
How to Fix
Move the 0t0fvh_tzx82b.css file to load asynchronously using Next.js dynamic imports or rel='preload' with onload handler. Inline critical CSS for above-the-fold content directly in the HTML head. Use Next.js built-in CSS optimization features in next.config.js.
0Needs Improvement
What This Score Means
A score of 89 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
78ms
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 website has good performance with a score of 89/100, but there's still room for improvement. The biggest issue is excessive unused JavaScript code that's delaying your Largest Contentful Paint by 750ms and wasting 159KB of bandwidth - nearly 96% of one JavaScript file isn't being used. Additionally, render-blocking CSS is slowing down initial page rendering by 150ms, and your logo image could be optimized to save 55KB by using modern formats like WebP and properly sizing it. Removing unused JavaScript code and deferring non-critical CSS would provide the most significant performance gains for your users.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
159 KiB of unused JavaScript is delaying LCP by 750ms and blocking critical rendering.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Implement dynamic imports for non-critical components using React.lazy(). Configure webpack-bundle-analyzer to split chunks more efficiently and remove the 95% unused code in 06g244pea4~aa.js.
Optimize Logo Image Delivery
Medium Impact+4 points estimatedWhy It Matters:
Logo image is oversized by 50KB and lacks proper dimensions, affecting both loading speed and CLS.
How to Fix:
Resize logo.png from 431x409 to actual display size of 177x168 pixels. Convert to WebP format to save 31KB. Add explicit width='177' height='168' attributes to the img tag to prevent layout shift during loading.
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 JavaScript Execution and Reflows
2.0 seconds of JavaScript execution time and forced reflows are causing 980ms of main thread blocking.
Remove Unused CSS and JavaScript
898KB of unused JavaScript and 98KB of unused CSS are unnecessarily inflating bundle sizes.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial render and delaying LCP by 1.6 seconds.
Eliminate Render Blocking CSS
The CSS chunk is blocking initial page render and delaying both LCP and FCP by 150ms.