Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize uat.revv.ekbana.net
Unsized images are causing 0.258 CLS score, making content jump and hurting user experience.
Add explicit width and height props to all Next.js Image components. Use the 'fill' prop with proper container sizing for responsive images. Implement placeholder='blur' with blurDataURL for smooth loading transitions to prevent layout shifts.
A score of 29 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.
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 severe performance issues with a score of only 29/100. The biggest problems are massive amounts of unused JavaScript (725 KiB wasted) and render-blocking CSS files that delay initial page rendering by nearly 2 seconds, causing the main content to take a devastating 14 seconds to appear. The site also suffers from significant layout shifts (0.26 CLS score) due to unsized images and experiences over 1 second of blocking time from excessive JavaScript execution. Removing unused code, optimizing CSS delivery, and properly sizing images could dramatically improve the score by 40+ points and transform the user experience from frustratingly slow to acceptably fast.
Why It Matters:
CSS files are blocking page rendering for 1.9 seconds, severely delaying LCP by preventing content from appearing.
How to Fix:
In your Next.js app, split critical CSS using the 'critical' package and inline it in the <head>. Move non-critical CSS to load asynchronously using next/dynamic or implement CSS code splitting. Consider using Next.js built-in CSS optimization by ensuring proper import order.
Why It Matters:
725 KiB of unused JavaScript is wasting 3.6 seconds of load time and blocking the main thread.
How to Fix:
Use Next.js dynamic imports with next/dynamic to code-split large vendor chunks. Analyze your bundle with @next/bundle-analyzer to identify unused dependencies. Configure tree-shaking in your webpack config and remove unused polyfills from your target browser configuration.
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
CSS files are blocking page rendering for 1.9 seconds, severely delaying LCP by preventing content from appearing.
Render-blocking CSS files delay first paint by 2 seconds, particularly the 29KB main stylesheet.
CLS score of 0.258 primarily caused by images without explicit dimensions shifting page layout.
725 KiB of unused JavaScript is wasting 3.6 seconds of load time and blocking the main thread.