LCP
Largest Contentful Paint
19.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery and Sizing
How to optimize khoji.connect.happythoughts.in
Optimize Image Delivery and Sizing
High Impact+20 points estimated
Why It Matters
Images are oversized for their display dimensions, wasting 545 KiB and slowing page load.
How to Fix
Replace <img> tags with Next.js Image component for automatic optimization. Use responsive image sizing with sizes prop based on viewport breakpoints. Convert PNG logo to WebP format and generate multiple sizes. Set up proper image CDN caching with longer cache lifetimes (1 year minimum).
0Needs Improvement
What This Score Means
A score of 52 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
533ms
Poor
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 52/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 19.1 seconds, primarily caused by 570 KiB of unused JavaScript code that's unnecessarily blocking page rendering. The site is also loading oversized images (545 KiB wasted) and executing too much JavaScript (1.3 seconds), which prevents users from interacting with the page for over 21 seconds. Removing unused JavaScript code, optimizing image sizes, and implementing code splitting could dramatically improve load times and boost the performance score by 30+ points.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
570 KiB of unused JavaScript is blocking rendering and delaying LCP by 3 seconds.
How to Fix:
Use Next.js dynamic imports to code-split components that aren't needed immediately. Analyze webpack-bundle-analyzer to identify unused dependencies. Enable tree-shaking by ensuring all imports use ES6 modules syntax. Consider lazy loading non-critical components with React.lazy().
Reduce JavaScript Execution Time
High Impact+18 points estimatedWhy It Matters:
1.3 seconds of JavaScript execution time is blocking the main thread and preventing user interactions.
How to Fix:
Split large JavaScript chunks using Next.js automatic code splitting with dynamic imports. Move heavy computations to Web Workers or defer them until after page load. Optimize the largest script (87192c9e968bf768.js) by breaking it into smaller, route-specific chunks using Next.js pages-based splitting.
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
Reduce JavaScript Execution Time
1.3 seconds of JavaScript execution time is blocking the main thread and preventing user interactions.
Modernize JavaScript Build Target
Your bundle includes 13KB of unnecessary polyfills for modern browser features, adding extra parsing and execution overhead.
Optimize LCP Image Loading
Your LCP image has a 1.7-second resource load delay and 979ms render delay, contributing to a poor 6.2-second LCP score.
Reduce JavaScript Execution Time
JavaScript execution takes 2.3 seconds and blocks the main thread for 1.3 seconds, severely impacting Total Blocking Time and user interactivity.