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 Sizes and Formats
How to optimize khoji.connect.staging.happythoughts.in
Optimize Image Sizes and Formats
High Impact+25 points estimated
Why It Matters
Oversized images are causing 493 KiB of waste and directly impact your 19.1s LCP score.
How to Fix
Configure Next.js Image component with proper responsive breakpoints for the logo (currently 2852x2696 for 123x123 display) and event thumbnails. Use Next.js built-in image optimization with formats=['webp', 'avif'] and sizes prop. Set priority={true} for above-the-fold images to preload them.
0Needs Improvement
What This Score Means
A score of 57 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
549ms
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 57/100, indicating significant user experience issues. The biggest problem is extremely slow content loading, with your Largest Contentful Paint taking 19.1 seconds and Speed Index at 12.5 seconds - far beyond acceptable limits. Your site is bloated with 3.8MB of resources, including oversized images (especially a 1.3MB logo file) and 570KB of unused JavaScript code that's unnecessarily transpiled with outdated polyfills. The most impactful fixes would be optimizing and properly sizing images, removing unused JavaScript, and updating your build configuration to eliminate legacy browser support code, which could improve load times by several seconds.
Other Optimization Recommendations
Eliminate Unused JavaScript Bundles
High Impact+20 points estimatedWhy It Matters:
570 KiB of unused JavaScript is blocking rendering and adding 2.9 seconds to load time.
How to Fix:
Enable Next.js bundle analyzer to identify dead code in chunks eb88397e2b11df3c.js (89% unused) and e60d9267ba893252.js (99% unused). Use dynamic imports for heavy components and implement code splitting with Next.js lazy() and Suspense. Configure webpack to exclude unused polyfills in next.config.js.
Update Build Target Configuration
Medium Impact+8 points estimatedWhy It Matters:
Legacy JavaScript polyfills add 31 KiB and 300ms to LCP while targeting outdated browsers.
How to Fix:
Update next.config.js with target: 'es2020' and configure .browserslistrc to exclude browsers older than 2 years. Remove Babel transforms for Array.prototype.at, Object.hasOwn, and other modern features now supported in 95%+ of browsers. This eliminates unnecessary polyfills and reduces bundle size.
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 CSS Rules
291KB of unused CSS is blocking first paint and adding 750ms delay to FCP.
Optimize LCP Video Element
The hero video has 2+ second render delay and lacks fetchpriority optimization, severely impacting LCP of 18.2 seconds.
Eliminate Unused JavaScript Code
2.8MB of unused JavaScript is blocking the main thread for 12.2 seconds and delaying LCP by 3.6 seconds.
Implement Efficient Resource Caching
Poor cache lifetimes are costing 1,718 KiB in repeat downloads and adding 300ms to both LCP and FCP.