LCP
Largest Contentful Paint
15.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Critical Image Delivery
How to optimize dev.happythoughts.in
Optimize Critical Image Delivery
High Impact+18 points estimated
Why It Matters
The main logo (275KB) and LCP image cause a 950ms delay to Largest Contentful Paint, severely impacting user experience.
How to Fix
Resize the logo from 2852x2696 to actual display size (109x105) using Next.js Image component with proper width/height props. Implement responsive images for the event card image using Next.js Image with optimized srcSet. Enable WebP format in next.config.js with formats: ['image/webp', 'image/avif'].
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
198ms
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 serious performance issues with a poor score of 49/100. The biggest problem is an extremely slow Largest Contentful Paint of 15.2 seconds, caused primarily by a massive 275KB logo image that's displayed at only 109x105 pixels and suffers from a 4.7-second resource load delay. The site is also bloated with 196KB of unused JavaScript from Google Analytics and other scripts that aren't needed immediately. Resizing and properly optimizing images, removing unused JavaScript, and implementing better caching strategies could dramatically improve the score by 30+ points and make the site usable for visitors.
Other Optimization Recommendations
Eliminate Unused JavaScript Bundles
High Impact+15 points estimatedWhy It Matters:
196KB of unused JavaScript creates 920ms delay and blocks the main thread, preventing user interactions.
How to Fix:
Configure Next.js bundle analyzer to identify unused code in chunks. Remove or lazy-load the 95% unused code in 2655324f1ab61a54.js and b772289a746aa74b.js chunks. Defer Google Analytics loading using next/script with strategy='afterInteractive' instead of direct gtag implementation.
Fix Resource Load Delays
Medium Impact+12 points estimatedWhy It Matters:
4.67 second resource load delay dominates the LCP breakdown, indicating inefficient resource prioritization.
How to Fix:
Add resource hints in next/head for critical assets using <link rel='preload'>. Configure proper cache headers for static assets - set logo.png to 1 year instead of 4 hours. Implement Next.js priority prop on the LCP image element to prioritize its loading over other resources.
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
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.
Remove Unused CSS Rules
28 KiB of unused CSS from Ant Design components is wasting bandwidth and slowing initial paint.