LCP
Largest Contentful Paint
3.3s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Logo Image Delivery
How to optimize staging.bhajans.happythoughts.in
Optimize Logo Image Delivery
High Impact+6 points estimated
Why It Matters
The logo image is oversized by 51KB and uses an inefficient format, impacting perceived load time.
How to Fix
Resize logo.png from 431x409 to its display size of 177x168 pixels. Convert to WebP format to save 32KB. In Next.js, use the Image component with proper width/height props: <Image src='/logo.png' width={177} height={168} alt='Logo' />.
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
83ms
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 performs well overall with a score of 91/100, but has room for improvement in loading speed. The biggest issue is unused JavaScript code that's delaying your Largest Contentful Paint by 600ms, particularly from oversized JavaScript bundles where 95% of one file isn't being used. Additionally, your logo image is significantly oversized (displaying at 177x168 but loading at 431x409) and could be optimized with modern formats like WebP to save 56KB. Quick wins include code-splitting your JavaScript bundles, properly sizing and compressing your logo image, and setting explicit width/height attributes on images to prevent layout shifts.
Other Optimization Recommendations
Reduce Unused JavaScript Bundle Size
High Impact+8 points estimatedWhy It Matters:
156 KiB of unused JavaScript is blocking LCP by 600ms and wasting network resources.
How to Fix:
Analyze your Next.js bundle using @next/bundle-analyzer to identify unused code. Implement dynamic imports for components not needed on initial load. Configure webpack tree-shaking to remove dead code from fd62dca6b5b6608e.js which has 95% unused code.
Eliminate Render-Blocking CSS
Medium Impact+4 points estimatedWhy It Matters:
CSS file is blocking initial render and delaying both LCP and FCP by 150ms each.
How to Fix:
Move critical CSS inline in your Next.js _document.js file for above-the-fold content. Use next/dynamic with ssr: false for non-critical components. Configure next.config.js to optimize CSS loading with experimental.optimizeCss: true.
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 Unused JavaScript Code
156KB of unused JavaScript is delaying LCP by 900ms and blocking page interactivity.
Eliminate Render-Blocking CSS
CSS file is blocking initial render and delaying both LCP and FCP by 150ms each.