LCP
Largest Contentful Paint
18.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Proper Browser Caching
How to optimize khoji.connect.happythoughts.in
Implement Proper Browser Caching
Medium Impact+8 points estimated
Why It Matters
Poor cache policies force re-downloading 855 KiB on repeat visits, slowing return user experience.
How to Fix
Configure next.config.js headers for static assets with 1-year cache lifetime. Set CDN cache headers for images to 31536000 seconds. Use Next.js automatic static optimization and enable immutable cache headers for _next/static files.
0Poor
What This Score Means
A score of 49 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
275ms
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 site has poor performance with a score of 49/100 and extremely slow loading times. The biggest problem is oversized, unoptimized images that are causing an 18.6-second Largest Contentful Paint - one event thumbnail alone is wasting 738KB by using PNG instead of WebP format and serving images much larger than their display size. The site is also loading 559KB of unused JavaScript and 50KB of unused CSS, while poor caching policies are forcing users to re-download large assets on every visit. Optimizing images to modern formats like WebP, implementing proper responsive images, and removing unused code could dramatically improve the score by 30+ points and reduce load times by over 10 seconds.
Other Optimization Recommendations
Optimize Image Delivery and Format
High Impact+25 points estimatedWhy It Matters:
Images waste 1,484 KiB and severely impact LCP with the largest image being 18x larger than needed.
How to Fix:
Implement Next.js Image component with responsive sizing and WebP/AVIF formats. Use next/image with proper width/height props and sizes attribute. Configure next.config.js with image optimization domains and formats: ['image/webp', 'image/avif'].
Reduce Unused JavaScript Bundles
High Impact+20 points estimatedWhy It Matters:
559 KiB of unused JavaScript delays LCP by 2.8 seconds and blocks main thread execution.
How to Fix:
Enable Next.js tree shaking and dynamic imports for large components. Use next/dynamic for code splitting heavy libraries. Analyze bundle with @next/bundle-analyzer to identify and remove unused dependencies. Move Google Analytics to _app.js with proper async loading.
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 Critical CSS Rendering
Render-blocking CSS files delay FCP by 750ms and contribute to the poor initial paint performance.
Reduce Unused JavaScript Bundle Size
756 KiB of unused JavaScript delays LCP by 3.9 seconds and wastes 3.9 seconds of load time.
Eliminate Redirect and Optimize Server Response
The redirect from commissions.gg to www.commissions.gg wastes 780ms and delays both FCP and LCP by 800ms each.
Eliminate Element Render Delay
LCP element has 3.2 second render delay causing the poor 7-second LCP score.