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
CLS score of 0.258 primarily caused by images without explicit dimensions shifting page layout.
Add explicit width and height props to all Next.js Image components, especially the Dunlop logo causing major shifts. Use Next.js Image component's fill prop with proper aspect ratio containers. Reserve space for dynamically loaded content with CSS min-height.
A score of 37 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/React website has severe performance issues with a score of only 37/100. The biggest problem is an extremely slow Largest Contentful Paint of 14.3 seconds, caused primarily by excessive unused JavaScript (725 KiB of wasted code) and render-blocking CSS files that delay initial page rendering by nearly 2 seconds. The site also suffers from significant layout shifts as images load without proper sizing, creating a jarring user experience. Removing unused JavaScript, optimizing CSS delivery, and properly sizing images could dramatically improve the score by 30+ points and reduce load times by over 10 seconds.
Why It Matters:
725 KiB of unused JavaScript is delaying LCP by 3.6 seconds and blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused vendor chunks. Implement dynamic imports for heavy libraries like the 99% unused vendors-9a8ad48e chunk. Configure webpack to split bundles by route and load components only when needed.
Why It Matters:
Render-blocking CSS files delay first paint by 2 seconds, particularly the 29KB main stylesheet.
How to Fix:
Split critical above-the-fold CSS using Next.js CSS-in-JS or extract critical styles inline. Use next/dynamic with ssr: false for non-critical components. Implement CSS code splitting by loading route-specific styles asynchronously.
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
Unsized images are causing 0.258 CLS score, making content jump and hurting user experience.
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.
725 KiB of unused JavaScript is wasting 3.6 seconds of load time and blocking the main thread.