LCP
Largest Contentful Paint
2.1s
Good
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Logo Image Performance
How to optimize bhajans.happythoughts.in
Optimize Logo Image Performance
Medium Impact+0.5 points estimated
Why It Matters
Your logo image wastes 56KB and lacks proper dimensions, affecting both loading speed and layout stability.
How to Fix
Convert logo.png to WebP or AVIF format for 30-50% size reduction. Resize the image from 431x409 to match display dimensions of 177x168. Add explicit width='177' height='168' attributes to the img tag to prevent layout shifts and improve CLS.
0Good
What This Score Means
A score of 98 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
81ms
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 excellent performance with a score of 98/100, but there are still some quick wins available. The biggest issue is render-blocking CSS that's delaying your page's initial paint by 150ms, which could be fixed by inlining critical styles or deferring non-essential CSS. Your logo image could be optimized by converting it to WebP format and properly sizing it for its display dimensions, saving about 55KB. Additionally, removing unused JavaScript polyfills for modern browser features like Array.flat and Object.hasOwn could save another 14KB and further improve load times.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+1 point estimatedWhy It Matters:
Render-blocking CSS is delaying LCP and FCP by 150ms, preventing users from seeing content immediately.
How to Fix:
In your Next.js app, move critical CSS inline or use next/dynamic for non-critical styles. Split your CSS chunks and load non-critical styles asynchronously using media='print' onload="this.media='all'" technique. Consider extracting above-the-fold styles into a separate critical CSS bundle.
Remove Unused JavaScript Polyfills
Medium Impact+0.5 points estimatedWhy It Matters:
Legacy JavaScript polyfills add 14KB of unnecessary code for modern browser features already supported.
How to Fix:
Update your Next.js browserslist configuration to target modern browsers (Chrome 91+, Firefox 90+). Configure Babel to exclude polyfills for Array.at, Array.flat, Object.fromEntries and other baseline features. Use next.config.js with experimental.browsersListForSwc to optimize bundle for your target browsers.
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 Time
2.2 seconds of JavaScript execution time is creating 580ms of Total Blocking Time, hurting user interactivity.
Reduce Unused JavaScript Payload
285KB of unused JavaScript is blocking the main thread and delaying LCP by 1.05 seconds.
Remove Legacy JavaScript Polyfills
Unnecessary polyfills add 40KB of code that modern browsers don't need, slowing down execution.
Optimize JavaScript Bundle Splitting
2.9 seconds of JavaScript execution time blocks the main thread and delays Time to Interactive by 11.2 seconds.