LCP
Largest Contentful Paint
20.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript
How to optimize khoji.connect.happythoughts.in
Eliminate Unused JavaScript
High Impact+18 points estimated
Why It Matters
540 KiB of unused JavaScript delays LCP by 3.35 seconds and blocks critical rendering.
How to Fix
Enable tree-shaking in Next.js by importing only used components (import { Button } from 'antd' instead of entire library). Use dynamic imports for heavy components with next/dynamic. Remove unused Google Tag Manager scripts or load them after page interaction.
0Poor
What This Score Means
A score of 38 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
481ms
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/React website has severe performance issues with a critically low score of 38/100. The biggest problem is extremely slow loading times, with the Largest Contentful Paint taking a devastating 20.4 seconds and the page not becoming interactive for over 24 seconds. The site is weighed down by 540 KiB of unused JavaScript code (89% waste in some files), oversized images that could be reduced by 1,259 KiB through modern formats and proper sizing, and JavaScript execution blocking the main thread for nearly 6 seconds. Removing unused code, optimizing images with WebP/AVIF formats and responsive sizing, and reducing JavaScript bundle sizes would dramatically improve performance and user experience.
Other Optimization Recommendations
Optimize and Compress Images
High Impact+12 points estimatedWhy It Matters:
Large, unoptimized images waste 1,259 KiB and delay LCP with oversized dimensions and legacy formats.
How to Fix:
Convert PNG images to WebP/AVIF format using Next.js Image component with quality={75}. Implement responsive images with proper sizes prop. Resize the logo from 2852x2696 to appropriate dimensions like 140x140 for 2x displays.
Fix Forced Reflow Issues
Medium Impact+8 points estimatedWhy It Matters:
JavaScript queries geometric properties after DOM changes, causing 74ms of forced reflows that block user interactions.
How to Fix:
Batch DOM reads and writes by reading all layout properties first, then making style changes. Use CSS transforms instead of changing layout properties. Implement virtual scrolling for long lists in React components.
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.