LCP
Largest Contentful Paint
19.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Code
How to optimize khoji.connect.happythoughts.in
Next.js SiteScore: 47/100Analyzed February 2026
Eliminate Unused JavaScript Code
High Impact+25 points estimated
Why It Matters
570 KiB of unused JavaScript delays LCP by 2.9 seconds and blocks the main thread.
How to Fix
Use Next.js dynamic imports with React.lazy() to code-split large chunks. Implement tree-shaking by updating webpack config to remove dead code. Use Next.js bundle analyzer to identify and remove unused dependencies from chunks like 16c570dc9f985bcb.js and 99b40b6b86110dda.js.
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
300ms
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 severe performance issues with a very poor score of 47/100. The biggest problem is extremely slow loading times - it takes a devastating 19 seconds for the main content to appear (Largest Contentful Paint) and over 21 seconds to become interactive, which will frustrate most users who typically abandon sites after 3 seconds. The primary culprits are massive amounts of unused JavaScript (570 KB that could be removed), oversized images that are much larger than needed (445 KB savings potential), and inefficient caching that forces users to re-download resources unnecessarily. Fixing the unused JavaScript and properly sizing images could potentially cut loading times in half and dramatically improve the user experience.
Other Optimization Recommendations
Optimize Image Sizes and Delivery
High Impact+15 points estimatedWhy It Matters:
Oversized images waste 445 KiB and the 277KB logo significantly impacts loading performance.
How to Fix:
Replace large images with Next.js Image component for automatic optimization. Resize the logo from 2852x2696 to actual display size of 123x123 pixels. Use responsive images with srcSet for event thumbnails to serve appropriately sized images based on viewport.
Update JavaScript Build Target
Medium Impact+8 points estimatedWhy It Matters:
Legacy JavaScript polyfills add unnecessary 32 KiB for modern browsers that support ES6+ natively.
How to Fix:
Update Next.js config target to 'es2017' or newer in next.config.js. Configure Babel to exclude polyfills for Array.prototype.at, Object.hasOwn, and other modern features. Use browserslist to target only browsers that need your app's support level.
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 Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
Frequently Asked Questions
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