LCP
Largest Contentful Paint
18.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Sizes and Formats
How to optimize khoji.connect.happythoughts.in
Optimize Image Sizes and Formats
High Impact+15 points estimated
Why It Matters
Oversized images waste 448 KiB and your logo alone is 2852x2696 but displayed at 70x70 pixels.
How to Fix
Use Next.js Image component with proper width/height props for automatic optimization. Serve appropriately sized images using responsive srcSet. Convert images to WebP format and implement lazy loading for below-the-fold content.
0Needs Improvement
What This Score Means
A score of 54 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
240ms
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 site has poor performance with a score of 54/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 18.9 seconds, primarily caused by oversized JavaScript bundles that are taking 1.5 seconds to execute and blocking the main thread for 2.6 seconds. The site is shipping 570 KB of unused JavaScript code and using outdated JavaScript polyfills that aren't needed for modern browsers, which could save 32 KB and improve loading by 200ms. Additionally, images are massively oversized (a 2852x2696 logo displayed at just 123x123 pixels) and could be optimized to save 448 KB, while better caching could save another 345 KB on repeat visits.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
570 KiB of unused JavaScript is delaying LCP by 2.85 seconds and blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks. Enable tree-shaking by importing only specific functions instead of entire libraries. Split large chunks using dynamic imports with React.lazy() for route-based code splitting.
Update JavaScript Build Target
Medium Impact+8 points estimatedWhy It Matters:
Legacy JavaScript polyfills add unnecessary 32 KiB and 200ms to LCP for modern browsers.
How to Fix:
Update Next.js configuration to target modern browsers by setting 'browserslist' to exclude IE and older browsers. Remove Babel transforms for Array.prototype.at, Object.hasOwn, and other modern features. Configure build to output ES2020+ syntax.
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
Remove Unused JavaScript Code
570 KiB of unused JavaScript is delaying LCP by 2.85 seconds and blocking user interactions.
Enable Advanced Image Compression
Current WebP images can be compressed further without quality loss, reducing transfer time.
Implement Responsive Image Optimization
Logo images are 2-3x larger than needed, wasting 26 KiB and slowing perceived performance.
Remove Unused JavaScript Code
40 KiB of unused JavaScript delays LCP by 150ms and wastes bandwidth on every page load.