Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize seva.happythoughts.in
The redirect chain is adding 770ms delay and directly impacting both LCP and FCP by 750ms each.
Update your Next.js configuration to serve the auth page directly without redirecting through the homepage. Check your rewrites/redirects in next.config.js and remove the unnecessary redirect from '/' to '/auth'. Configure your hosting provider to point directly to the intended destination.
A score of 69 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js/React site has poor performance with a score of 69/100, indicating significant issues that affect user experience. The biggest problem is an extremely slow Largest Contentful Paint of 7.3 seconds, primarily caused by multiple page redirects (costing 770ms) and render-blocking CSS files that delay initial page rendering by 600ms. The site is also loading 212 KiB of unused JavaScript and 25 KiB of unused CSS, while serving files with inefficient cache settings that waste 243 KiB on repeat visits. Fixing the redirect chain, deferring non-critical CSS/JavaScript, and implementing proper caching could improve the performance score by 30+ points and dramatically speed up page load times.
Why It Matters:
212KB of unused JavaScript is delaying LCP by 1.25 seconds and increasing bundle size unnecessarily.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your chunks. Remove unused Google Analytics features and implement tree-shaking properly. Consider code-splitting with dynamic imports for non-critical components and lazy-load the Google Tag Manager script after page interaction.
How to Fix:
Implement critical CSS extraction in your Next.js build process using tools like critters. Move non-critical CSS to load asynchronously after page render. Consider CSS-in-JS solutions like styled-components for component-specific styles to reduce unused CSS automatically.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Poor caching configuration forces users to re-download resources on repeat visits, missing opportunities for faster load times.
356KB of unused JavaScript is bloating your bundle size and slowing down page load without providing value.
CSS files are blocking initial page render and delaying FCP by 1 second, directly impacting user experience.
Render-blocking CSS delays First Contentful Paint by 900ms, preventing users from seeing content quickly.