LCP
Largest Contentful Paint
10.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Element Render Delay
How to optimize dev.happythoughts.in
Fix Element Render Delay
High Impact+25 points estimated
Why It Matters
The LCP element has a massive 5.27 second render delay, causing the worst possible LCP score.
How to Fix
Move critical CSS for the 'Explore Our Programs' section inline in the HTML head. Preload the event card data or implement server-side rendering for this content. Remove any JavaScript dependencies blocking the rendering of this above-the-fold content.
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
230ms
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/React website has poor performance with a score of 48/100, indicating significant speed issues that affect user experience. The biggest problem is excessive JavaScript that's blocking the page from becoming interactive, with Time to Interactive taking 13.1 seconds and the site loading 147 KiB of unused JavaScript code. The Largest Contentful Paint is also severely delayed at 10.4 seconds due to render delays and inefficient resource loading. Immediate improvements should focus on removing unused JavaScript code (especially from Google Analytics), eliminating 28 KiB of unused CSS, and optimizing image delivery to reduce load times by several seconds.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
Unused JavaScript is consuming 147 KiB and delaying LCP by 600ms, significantly impacting page load performance.
How to Fix:
Use Next.js bundle analyzer (@next/bundle-analyzer) to identify unused code chunks. Implement code splitting with dynamic imports for components not needed on initial load. Remove unused Google Analytics features and consider switching to a lighter analytics solution like Plausible.
Remove Unused CSS Rules
Medium Impact+8 points estimatedWhy It Matters:
28 KiB of unused CSS from Ant Design components is wasting bandwidth and slowing initial paint.
How to Fix:
Configure Ant Design with tree shaking in your Next.js build to only include used components. Use PurgeCSS or built-in CSS purging to remove unused styles. Consider switching from full Ant Design imports to individual component imports.
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.
Fix Resource Load Delay Issue
Your LCP is delayed by 10.5 seconds due to resource load delay, making the page appear frozen to users.
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.