LCP
Largest Contentful Paint
13.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Legacy JavaScript Polyfills
How to optimize dev.happythoughts.in
Eliminate Legacy JavaScript Polyfills
Medium Impact+8 points estimated
Why It Matters
Legacy JavaScript polyfills add 22 KiB of unnecessary code that delays LCP by 150ms for modern browsers.
How to Fix
Update Next.js browserslist configuration to target modern browsers and remove polyfills for Array.prototype.at, Object.hasOwn, and other baseline features. Configure webpack to output ES2020+ syntax. Use next.config.js to set target: 'server' and modern: true for differential serving.
0Poor
What This Score Means
A score of 44 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
343ms
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 severe performance issues with a poor score of 44/100. The biggest problem is excessive JavaScript execution time (1.8 seconds) combined with massive resource load delays causing the Largest Contentful Paint to take an alarming 13.3 seconds. The site is loading 147 KB of unused JavaScript code and inefficient image delivery, with Google Tag Manager being a major contributor to the slowdown. Reducing JavaScript bundle sizes, removing unused code, and optimizing images could improve the score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Optimize JavaScript Bundle Size and Execution
High Impact+25 points estimatedWhy It Matters:
JavaScript execution takes 1.8 seconds and blocks the main thread for 2.9 seconds, severely impacting TBT and user interactions.
How to Fix:
Remove unused JavaScript (147 KiB savings identified) by implementing code splitting with Next.js dynamic imports. Defer Google Analytics loading using next/script with strategy='afterInteractive'. Optimize the main bundle chunk (9e9ed20ed48678f9.js) by removing dead code and splitting large components.
Fix Critical Resource Load Delay
High Impact+20 points estimatedWhy It Matters:
LCP is delayed by 10.4 seconds due to resource load delay, making the largest contentful paint occur at 13.3 seconds.
How to Fix:
Implement resource hints using Next.js preload for critical images. Optimize the LCP image (event card thumbnail) by resizing from 750x1071 to match display dimensions 648x926. Use next/image priority prop for above-the-fold images and consider moving critical images to a faster CDN.
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
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.
Fix Element Render Delay
The LCP element has a massive 5.27 second render delay, causing the worst possible LCP score.