LCP
Largest Contentful Paint
15.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Resource Load Delay Issue
How to optimize dev.happythoughts.in
Fix Resource Load Delay Issue
High Impact+35 points estimated
Why It Matters
Your LCP is delayed by 10.5 seconds due to resource load delay, making the page appear frozen to users.
How to Fix
Investigate and fix the resource loading bottleneck causing the 10.5-second delay in your Next.js app. Check for blocking requests, network issues, or server-side rendering problems. Consider implementing Next.js Image optimization with priority loading for your LCP image element.
0Poor
What This Score Means
A score of 48 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
267ms
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 site has poor performance with a score of 48/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 15.2 seconds, primarily caused by a massive 276KB logo image that's displayed at only 109x105 pixels but served at 2852x2696 resolution. The site is also loading 219KB of unused JavaScript code, including Google Analytics scripts and Next.js chunks that aren't being utilized, which blocks the main thread for 1.5 seconds and delays interactivity. Resizing and optimizing images, removing unused JavaScript, and implementing proper caching could dramatically improve the score by 30+ points and provide a much faster user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
219 KiB of unused JavaScript is blocking page rendering and delaying LCP by 950ms.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Remove unused Google Analytics features or defer GTM loading. Implement dynamic imports for large components that aren't immediately needed. Configure your build to exclude unused polyfills and dependencies.
Optimize Image Delivery Strategy
High Impact+12 points estimatedWhy It Matters:
Images are 275KB larger than needed and directly impact your LCP performance by 950ms.
How to Fix:
Use Next.js Image component with proper sizing for your logo (currently 2852x2696 displayed as 109x105). Enable responsive images with appropriate srcSet configurations. Compress the logo PNG and convert to WebP format using next-optimized-images or similar optimization.
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 Image Delivery Strategy
Images are 275KB larger than needed and directly impact your LCP performance by 950ms.
Eliminate Legacy JavaScript Polyfills
Legacy JavaScript polyfills add 22 KiB of unnecessary code that delays LCP by 150ms for modern browsers.
Fix Critical Resource Load Delay
LCP is delayed by 10.4 seconds due to resource load delay, making the largest contentful paint occur at 13.3 seconds.
Optimize JavaScript Bundle Size and Execution
JavaScript execution takes 1.8 seconds and blocks the main thread for 2.9 seconds, severely impacting TBT and user interactions.