LCP
Largest Contentful Paint
20.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery and Format
How to optimize khoji.connect.happythoughts.in
Optimize Image Delivery and Format
High Impact+18 points estimated
Why It Matters
Images waste 1,259 KiB and the main LCP image (839KB PNG) is oversized and unoptimized, directly impacting the 20.4s LCP score.
How to Fix
Configure Next.js Image component with priority flag for LCP images and responsive sizing. Convert PNG images to WebP/AVIF using next-optimized-images or similar. Resize event thumbnails to match display dimensions (648x926 instead of 896x1280).
0Poor
What This Score Means
A score of 44 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
353ms
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 44/100. The biggest problem is excessive JavaScript execution taking 2.4 seconds, which severely impacts user interactivity and causes a devastating 20+ second load time for the main content. The site is bloated with unused JavaScript (540 KB could be removed), oversized images that aren't optimized for modern formats, and unnecessary CSS that's slowing down the page. Reducing JavaScript bundle sizes, optimizing images to WebP/AVIF format, and removing unused code could improve the score by 30+ points and make the site usable for visitors.
Other Optimization Recommendations
Reduce JavaScript Execution Time
High Impact+25 points estimatedWhy It Matters:
JavaScript execution takes 2.4 seconds and causes 900ms of blocking time, severely delaying user interactions and contributing to the poor Total Blocking Time score.
How to Fix:
Use Next.js dynamic imports to code-split large chunks like 07ikq4anad1-l.js (1.4MB). Implement React.lazy() for non-critical components. Configure webpack bundle analyzer to identify and remove unused dependencies from your Next.js build.
Remove Unused CSS and JavaScript
Medium Impact+12 points estimatedWhy It Matters:
540KB of unused JavaScript and 50KB of unused CSS create unnecessary network overhead and parsing time, contributing to poor LCP performance.
How to Fix:
Use Next.js tree-shaking by ensuring proper ES6 imports. Remove unused Ant Design components and CSS by configuring babel-plugin-import. Implement CSS purging with tools like PurgeCSS in your Next.js build process.
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.