LCP
Largest Contentful Paint
10.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Image Dimensions and Caching
How to optimize moa.happythoughts.in
Add Image Dimensions and Caching
Medium Impact+8 points estimated
Why It Matters
Missing image dimensions cause layout shifts, and short cache lifetimes (5s) force unnecessary re-downloads affecting repeat visits.
How to Fix
Add explicit width='412' height='494' to your hero image element. Configure Next.js static asset caching to 1 year by setting headers in next.config.js. Use Next.js Image component which automatically includes dimensions.
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
114ms
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 57/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 10.5 seconds, primarily caused by a large, unoptimized hero image that's 73KB larger than necessary and lacks proper dimensions. The site is also severely hampered by render-blocking CSS and JavaScript files that delay initial page rendering by nearly 7 seconds, along with 74KB of unused JavaScript code. Quick wins include resizing and properly sizing the main image, setting cache headers longer than 5 seconds, and removing unused CSS/JavaScript, which together could improve the performance score by 30+ points and dramatically speed up page loading.
Other Optimization Recommendations
Optimize Hero Image Delivery
High Impact+18 points estimatedWhy It Matters:
The hero image is oversized (73KB waste) and lacks priority hints, directly impacting your 10.5s LCP.
How to Fix:
Add fetchpriority='high' to the hero image element. Use Next.js Image component with proper sizing - serve 412x494 instead of 1078x1292. Generate responsive srcSet with next/image for automatic optimization and WebP conversion.
Remove Unused JavaScript and CSS
High Impact+15 points estimatedWhy It Matters:
74KB of unused JavaScript and 33KB of unused CSS are blocking rendering and delaying LCP by 300ms combined.
How to Fix:
Configure Next.js bundle analyzer to identify unused code. Remove or defer Google Analytics until after page load. Use dynamic imports for non-critical components. Enable CSS tree-shaking in your build process.
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 LCP Element Loading
The LCP element has a 2.7 second resource load delay and lacks priority optimization.
Reduce JavaScript Bundle Size
1.9 seconds of JavaScript execution time blocks user interactions and increases Total Blocking Time by 500ms.
Eliminate Render-Blocking CSS Resources
Critical CSS blocks First Contentful Paint by 3.36 seconds, severely delaying page visibility.
Eliminate Render Blocking CSS
CSS files are blocking initial render and delaying FCP by 850ms.