LCP
Largest Contentful Paint
20.3s
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 waste 1,259 KB with oversized dimensions and outdated formats, directly impacting LCP performance.
How to Fix
Use Next.js Image component with proper width/height props for automatic optimization. Configure next.config.js with formats: ['image/webp', 'image/avif'] for modern formats. Resize the 896x1280 thumbnails to match 648x926 display dimensions.
0Poor
What This Score Means
A score of 40 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
623ms
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/React site has severe performance issues with a critically low score of 40/100. The biggest problem is excessive JavaScript execution taking 3.0 seconds to run, which is causing a devastating 20.3-second Largest Contentful Paint and making the page unusable for visitors. The site is loading nearly 5MB of resources including oversized images and contains 540KB of unused JavaScript code that should be removed or split into smaller chunks. Optimizing the JavaScript bundles, compressing images, and implementing code splitting could dramatically improve load times and user experience.
Other Optimization Recommendations
Reduce JavaScript Execution Time
High Impact+25 points estimatedWhy It Matters:
JavaScript execution takes 3 seconds blocking the main thread and causes 1.4s Total Blocking Time, severely impacting user interactions.
How to Fix:
Configure Next.js bundle analyzer to identify large chunks. Split the 742KB chunk using dynamic imports for route-based code splitting. Remove unused dependencies and consider lazy loading non-critical components with React.lazy().
Remove Legacy JavaScript Polyfills
Medium Impact+8 points estimatedWhy It Matters:
Unnecessary polyfills add 23KB of unused code that can be eliminated for modern browser support.
How to Fix:
Update Next.js browserslist config to target modern browsers (>0.3%, not dead). Configure Babel preset-env with browserslist integration to avoid transpiling Array.prototype.at, Object.hasOwn and other modern features. Remove manual polyfills from dependencies.
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
Eliminate Render-Blocking CSS Resources
Render-blocking CSS is delaying LCP by 1.95 seconds, preventing the page from displaying content quickly.
Fix Render Blocking Resources
Critical CSS files are blocking initial page render and delaying LCP by 200ms.
Reduce JavaScript Execution Time
JavaScript takes 10.5 seconds to execute, blocking the main thread and preventing user interactions for 4.3 seconds.
Eliminate Unused JavaScript Code
Removing 3,139 KiB of unused JavaScript will reduce network transfer time and improve LCP by 12 seconds.