LCP
Largest Contentful Paint
12.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Render-blocking CSS Resources
How to optimize ambarsthan.happythoughts.in
Fix Render-blocking CSS Resources
Medium Impact+8 points estimated
Why It Matters
CSS chunks block First Contentful Paint for 300ms preventing initial page render.
How to Fix
Move critical CSS inline using Next.js styled-jsx or extract above-the-fold styles. Defer non-critical CSS using media='print' onload='media=all' technique. Optimize CSS delivery by reducing chunk sizes and combining smaller stylesheets.
0Needs Improvement
What This Score Means
A score of 64 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
119ms
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 website has poor performance with a score of 64/100, indicating significant issues that affect user experience. The biggest problem is extremely slow Largest Contentful Paint at 12.2 seconds, primarily caused by large, unoptimized PNG images (over 1.5MB could be saved by converting to WebP/AVIF format and properly sizing them). The site also suffers from render-blocking CSS files that delay initial page display, unused JavaScript code wasting 203KB of bandwidth, and inefficient caching that forces users to re-download the same large images on repeat visits. Addressing the image optimization alone could improve load times by over 3 seconds and dramatically boost the performance score.
Other Optimization Recommendations
Optimize and Modernize Image Delivery
High Impact+25 points estimatedWhy It Matters:
Images waste 1,532 KiB and delay LCP by 3.1 seconds with poor compression and format.
How to Fix:
Convert PNG images to WebP/AVIF using Next.js Image component with format optimization. Implement responsive images with proper srcSet for mobile displays. Add fetchpriority='high' to the LCP image (Slide 1) and ensure it's discoverable in initial HTML without JavaScript.
Eliminate Unused JavaScript and Polyfills
High Impact+18 points estimatedWhy It Matters:
203 KiB of unused JavaScript delays LCP by 450ms and blocks critical rendering.
How to Fix:
Update Next.js target to 'es2022' in next.config.js to remove unnecessary polyfills (Array.at, Object.hasOwn). Use dynamic imports for Google Analytics and defer non-critical JavaScript. Run webpack-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 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.