Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize tsy.happythoughts.in
189 KiB of unused JavaScript delays LCP by 1.1 seconds and blocks the main thread.
Enable Next.js tree shaking by using ES6 imports instead of entire libraries. Configure webpack bundle analyzer to identify unused code in your chunks. Split the large fd7e7cb90071b1c8.js chunk using dynamic imports for non-critical features. Move Google Analytics to use Next.js Script component with strategy='afterInteractive'.
A score of 75 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 site has poor performance with a score of 75/100, but faces critical loading issues. The biggest problem is a redirect chain that's adding nearly 800ms of delay, combined with extremely slow Largest Contentful Paint at 7.2 seconds - well above Google's recommended 2.5 seconds. The site is also bloated with 189 KiB of unused JavaScript and has inefficient caching, particularly for the logo image which has almost no cache lifetime. Fixing the redirect issue, optimizing the logo caching, and removing unused code could dramatically improve loading times and boost the performance score by 15-20 points.
Why It Matters:
Redirects delay both LCP and FCP by 750ms, significantly impacting user experience.
How to Fix:
Update your Next.js deployment configuration to serve the auth page directly without redirecting through the root. If using Vercel, check your vercel.json rewrites. If using custom server, update your routing logic to avoid the redirect chain from / to /auth.
Why It Matters:
Poor cache configuration wastes 245 KiB on repeat visits, especially the 243KB logo file.
How to Fix:
Configure your Next.js static asset caching by setting proper Cache-Control headers for the Logo.svg (1 year max-age). Use next/image component instead of regular img tag for optimized caching. Set up CDN caching rules for your static assets and enable immutable caching for hashed assets.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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.