Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize scan.co.uk
The 601KB hero image lacks priority hints and proper optimization, contributing to the 14-second LCP.
Add fetchpriority='high' to the LCP hero image element. Compress the comp-hardware-bg-5090.webp image to reduce size by 255KB using modern compression tools. Implement responsive images with srcset for different viewport sizes. Preload the hero image in HTML head using <link rel='preload' as='image'>.
A score of 50 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 website has poor performance with a score of 50/100 and suffers from extremely slow loading times. The biggest problem is render-blocking CSS files that delay First Contentful Paint by 3.5 seconds and cause the page to take 14 seconds to become fully interactive. The site is also bloated with 161 KB of unused CSS (90% waste), 334 KB of unused JavaScript, and unnecessarily large images that could be compressed by 396 KB. Fixing the render-blocking resources, removing unused code, and optimizing images could improve the performance score by 30+ points and dramatically reduce loading times from 14 seconds to under 5 seconds.
Why It Matters:
Render blocking CSS is delaying First Contentful Paint by 3.5 seconds, severely impacting user experience.
How to Fix:
Inline critical CSS directly in the HTML head for above-the-fold content. Defer non-critical CSS using media='print' onload technique or loadCSS library. Split the 182KB main CSS bundle into smaller, page-specific files. Remove unused CSS rules that account for 90% of the main stylesheet.
Why It Matters:
334KB of unused JavaScript is blocking the main thread and delaying LCP by 1.5 seconds.
How to Fix:
Audit Google Analytics and GTM implementations to remove duplicate tracking code. Use webpack bundle analyzer to identify unused code in vendors.js. Implement code splitting to load only necessary JavaScript per page. Defer third-party scripts like Facebook Pixel until after page load using async/defer attributes.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.