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 brand logo images are causing a CLS score of 0.271, creating jarring visual shifts.
Add explicit width and height attributes to all brand logo images in your components. Use Next.js Image component with proper dimensions for the LS2 and Dunlop logos. Create CSS aspect-ratio containers for dynamically sized images to reserve layout space before loading.
A score of 28 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 critical performance issues with a very poor score of 28/100. The biggest problem is massive JavaScript bloat - the page loads 725 KiB of unused JavaScript that's delaying page interactivity by 16.2 seconds and blocking critical rendering for nearly 2 seconds. The site is also suffering from severe layout shifts (CLS score of 0.271) caused by unsized images that move content around as they load, plus inefficient CSS delivery that's further slowing down the initial paint. Removing unused JavaScript, properly sizing images, and optimizing CSS delivery could dramatically improve this score by 40+ points and make the site actually usable for visitors.
Why It Matters:
Three CSS files are blocking initial render and delaying LCP by 1.95 seconds.
How to Fix:
In your Next.js app, move critical CSS inline using the _document.js file. Split non-critical CSS and load it asynchronously using dynamic imports or the loadCSS library. Consider using CSS-in-JS solutions like styled-components for component-specific styles to reduce bundle size.
Why It Matters:
725 KiB of unused JavaScript is significantly slowing page load and blocking the main thread.
How to Fix:
Use Next.js bundle analyzer to identify unused code in your vendor chunks. Implement dynamic imports for heavy libraries that aren't needed immediately. Remove or lazy-load the unused Stripe integration (3 unused preconnects detected). Enable tree-shaking in your webpack configuration to eliminate dead code.
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
725 KiB of unused JavaScript is significantly slowing page load and blocking the main thread.
Three CSS files are blocking initial render and delaying LCP by 1.95 seconds.
Multiple layout shifts (CLS: 0.27) are caused by unsized images and dynamic content loading, hurting user experience.
706 KiB of unused JavaScript is loaded unnecessarily, wasting 3.66 seconds and blocking user interactions.