LCP
Largest Contentful Paint
10.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Resource Preconnections and Caching
How to optimize ambarsthan.happythoughts.in
Add Resource Preconnections and Caching
Medium Impact+12 points estimated
Why It Matters
Network delays from external origins and poor cache policies waste 900ms on LCP and force resource re-downloads.
How to Fix
Add <link rel='preconnect' href='https://api.happythoughts.in'> and <link rel='preconnect' href='https://cdn.happythoughts.in'> to Next.js Head component. Configure next.config.js headers to set Cache-Control: public, max-age=31536000 for static assets. Implement proper CDN caching for images.
0Needs Improvement
What This Score Means
A score of 66 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
138ms
Good
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 66/100, struggling particularly with slow loading times. The biggest problem is oversized and unoptimized images that are wasting over 1.6MB of data - these images are using outdated PNG formats instead of modern WebP/AVIF and are twice as large as needed for their display size. The site also suffers from render-blocking CSS files that delay initial page rendering by 300ms and unused JavaScript that's adding unnecessary bloat. Converting images to modern formats, implementing proper responsive sizing, and removing unused code could dramatically improve the painfully slow 10.3-second Largest Contentful Paint and boost the overall performance score significantly.
Other Optimization Recommendations
Optimize Images with Modern Formats
High Impact+25 points estimatedWhy It Matters:
Image optimization can save 1,615 KiB and significantly improve LCP since images are the largest resources on your page.
How to Fix:
Convert PNG images to WebP/AVIF format using Next.js Image component with quality={75}. Implement responsive sizing with srcSet to serve appropriately sized images (current images are 2x larger than needed). Use next/image with priority={true} for above-the-fold images and add fetchpriority='high' to the LCP image.
Eliminate Unused JavaScript and Polyfills
High Impact+18 points estimatedWhy It Matters:
Unused JavaScript wastes 203 KiB and delays LCP by 1.05 seconds while legacy polyfills add unnecessary overhead for modern browsers.
How to Fix:
Configure Next.js target to 'es2017' or higher in next.config.js to remove unnecessary polyfills. Implement dynamic imports for Google Analytics and non-critical components. Use Next.js bundle analyzer to identify and remove unused code from chunks.
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.