Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize devanhaar.com
Large images are severely delaying LCP by delivering oversized files in inefficient formats, causing an 85-second LCP.
Convert the 11.7MB elevate.png to WebP format and create responsive versions using Next.js Image component with proper sizing. Implement priority loading for hero images with priority={true}. Use fill and sizes props to serve appropriately sized images for each viewport.
A score of 56 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 significant performance issues with a poor score of 56/100, indicating serious user experience problems. The biggest issue is extremely slow loading times, with your Largest Contentful Paint taking a shocking 85.3 seconds and First Contentful Paint at 5.1 seconds - both far exceeding acceptable limits. The primary culprits are massive, unoptimized images (over 31MB total payload) that need modern formats like WebP and proper sizing, along with render-blocking CSS files that are delaying initial page display. Quick wins include optimizing your large PNG images, removing 91KB of unused JavaScript, implementing better caching for your Supabase images, and deferring non-critical CSS to dramatically improve load times.
Why It Matters:
CSS files are blocking initial render and delaying both FCP and LCP by 150ms in the critical path.
How to Fix:
Extract critical CSS for above-the-fold content and inline it in the document head. Use Next.js dynamic imports to defer non-critical CSS. Configure your build process to automatically identify and inline critical styles using tools like critical or critters.
Why It Matters:
91KB of unused JavaScript is delaying LCP by 450ms and wasting bandwidth with unnecessary code execution.
How to Fix:
Use Next.js dynamic imports to code-split large components and defer Instagram embed loading until needed. Remove legacy JavaScript polyfills by updating your Next.js target to modern browsers. Analyze bundle with @next/bundle-analyzer to identify and eliminate unused dependencies.
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
2.0 seconds of JavaScript execution time blocks user interactions and increases Total Blocking Time by 150ms.
284KB of unused JavaScript wastes bandwidth and delays LCP by 150ms while blocking the main thread.
Render-blocking CSS delays LCP by 600ms and FCP by 600ms, significantly impacting perceived load speed.
Analysis for seva.happythoughts.in