LCP
Largest Contentful Paint
18.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Legacy JavaScript Polyfills
How to optimize khoji.connect.happythoughts.in
Remove Legacy JavaScript Polyfills
Medium Impact+8 points estimated
Why It Matters
33KB of unnecessary polyfills slow down modern browsers that already support these features natively.
How to Fix
Update your Next.js browserslist configuration to target modern browsers (ES2020+). Remove Babel transforms for Array.flat, Object.fromEntries, and other baseline features. Configure webpack to exclude polyfills for supported browsers using @babel/preset-env with proper targets.
0Poor
What This Score Means
A score of 47 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
288ms
Needs Improvement
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 site has severe performance issues with a score of 47/100. The biggest problem is an extremely slow Largest Contentful Paint of 18.6 seconds, caused primarily by excessive JavaScript execution (3.4 seconds of main-thread work) and a massive 1.3MB font file that's blocking the page render. The site is also loading 583KB of unused JavaScript and serving oversized images, including a 276KB logo that's displayed at only 70x70 pixels. Optimizing the font loading strategy, removing unused code, and properly sizing images could dramatically improve load times and bring the site into acceptable performance ranges.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
597 KB of unused JavaScript delays LCP by 2.5 seconds and blocks the main thread unnecessarily.
How to Fix:
Use Next.js dynamic imports with React.lazy() for component code-splitting. Enable tree-shaking by ensuring imports use named exports instead of default exports. Run webpack-bundle-analyzer to identify and remove unused dependencies from your bundle.
Optimize Image Delivery Strategy
High Impact+15 points estimatedWhy It Matters:
The 277KB logo image is 20x larger than needed and contributes to the 18.6s LCP time.
How to Fix:
Use Next.js Image component with responsive sizing for automatic optimization. Resize the logo to actual display dimensions (123x123) instead of 2852x2696. Implement WebP format with fallbacks and add proper srcset attributes for different screen densities.
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 Image Delivery Strategy
The 277KB logo image is 20x larger than needed and contributes to the 18.6s LCP time.
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.