Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize nationalnumbers.co.uk
The Termly resource blocker is blocking initial render and delaying LCP by 1,050ms.
Move the Termly script to load asynchronously by adding async attribute or defer loading until after page interactive. Consider implementing cookie consent functionality with a lighter-weight solution or load Termly conditionally only when needed.
A score of 60 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 National Numbers website has poor performance with a score of 60/100, primarily due to severe render-blocking issues caused by the Termly resource blocker script, which is delaying page loading by over 1 second. The site's Largest Contentful Paint takes a painfully slow 8.2 seconds, making visitors wait far too long to see meaningful content. The biggest wins would come from fixing the render-blocking JavaScript (estimated 1,050ms savings), removing 305 KiB of unused JavaScript code, and implementing proper browser caching which could save another 152 KiB. These optimizations alone could potentially improve the performance score by 30+ points and dramatically reduce loading times for users.
Why It Matters:
305 KiB of unused JavaScript is delaying LCP by 1.8 seconds and blocking user interactions.
How to Fix:
Remove or defer unused portions of Google Tag Manager, Termly script, and other third-party scripts. Implement code splitting to load only essential JavaScript initially. Use dynamic imports for non-critical functionality that can load after page interactive.
Why It Matters:
Poor caching is wasting 152 KiB on repeat visits and slowing FCP by 750ms.
How to Fix:
Increase cache lifetime for Termly and Trustpilot scripts to at least 1 year (31536000 seconds). Configure your CDN or server to set proper Cache-Control headers. Implement versioning for static assets to enable aggressive caching.
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.