Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize agileontheweb.com
Unnecessary polyfills add 11KB of unused code and delay LCP by 150ms for modern browsers.
Update your Next.js browserslist configuration to target only modern browsers. Remove polyfills for Array.prototype.at, Array.flat, and Object.hasOwn since they're widely supported. Use Next.js's built-in modern JavaScript output by setting experimental.esmExternals to true in next.config.js.
A score of 58 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/React site has poor performance with a score of 58/100, primarily due to severe layout stability issues. The biggest problem is massive layout shifts (CLS score of 1.96) caused by an unsized video element in the hero section that shifts content around as the page loads. Additionally, render-blocking CSS files are delaying initial page rendering by 450ms, and there's 27KB of unused JavaScript that could be removed. Fixing the video element sizing and deferring non-critical CSS could dramatically improve both visual stability and loading speed, potentially boosting the performance score by 30+ points.
Why It Matters:
Unsized video elements are causing a severe CLS score of 1.955, significantly harming user experience.
How to Fix:
Add explicit width and height attributes to the hero video element. Use CSS aspect-ratio property to maintain responsive behavior. Consider using a placeholder image with identical dimensions while the video loads to prevent layout jumps.
Why It Matters:
Two CSS files are blocking initial render and delaying LCP by 450ms.
How to Fix:
Inline critical CSS for above-the-fold content in your Next.js layout component. Use next/dynamic with ssr: false for non-critical styles. Consider splitting CSS using Next.js built-in CSS code splitting to load only necessary styles per page.
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 video elements are causing a severe CLS score of 1.955, significantly harming user experience.
JavaScript is causing 95ms of forced reflows, blocking the main thread and degrading INP.
76% of JavaScript in main chunk (27KB) is unused, creating unnecessary network overhead.
Two CSS files are blocking initial render and delaying LCP by 450ms.