Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize builder.io
The LCP image uses lazy loading and lacks priority hints, causing a 4.26 second resource load delay.
Remove loading='lazy' from the hero image and add fetchpriority='high'. Add a preload link in the HTML head for the LCP image. Ensure the image request is discoverable in the initial HTML without JavaScript execution.
A score of 19 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 website has severe performance issues with an extremely poor score of 19/100. The biggest problem is that the main LCP image is lazy-loaded and takes over 16 seconds to appear, causing a terrible user experience where visitors see nothing meaningful for far too long. The site is also plagued by 197KB of unused JavaScript code, render-blocking cookie consent scripts that delay page rendering by 650ms, and excessive layout shifts from the cookie banner that disrupts the page as it loads. Removing lazy loading from the main hero image, deferring non-critical JavaScript, and optimizing the cookie consent implementation could dramatically improve the score by 30-40 points and provide users with a much faster, more stable browsing experience.
Why It Matters:
197 KiB of unused JavaScript blocks the main thread and delays LCP by 1.05 seconds.
How to Fix:
Use webpack-bundle-analyzer to identify unused code in your main bundle. Remove unused cookie consent features and implement tree shaking. Split large bundles using dynamic imports and load only necessary code for initial render.
Why It Matters:
The OneTrust cookie banner causes 0.181 CLS score through unexpected layout movements.
How to Fix:
Reserve space for the cookie banner with CSS to prevent layout shifts. Load the cookie consent script asynchronously after critical content renders. Consider using a less intrusive cookie notice design that doesn't push content.
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 Generic Speed Tests
Unoptimized viewport causes 300ms tap delays, negatively affecting user interaction responsiveness.
First network request latency of 300ms delays both LCP and FCP, slowing initial page render.
The redirect chain delays LCP and FCP by 800ms, significantly impacting user experience.
The main hero image is oversized and poorly compressed, wasting 80KB and delaying LCP by 600ms.