Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize staging.nationalnumbers.co.uk
Non-optimized viewport causes 300ms tap delays, significantly hurting mobile user interaction responsiveness.
Add proper viewport meta tag to HTML head: <meta name='viewport' content='width=device-width, initial-scale=1'>. Remove any fixed viewport widths or disable user scaling that might trigger mobile browser delays. Test touch interactions to ensure immediate response on mobile devices.
A score of 100 falls in the "Good" 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 achieves an excellent performance score of 100/100, indicating fast loading times and optimal user experience. However, there are still two minor optimization opportunities that could enhance repeat visitor performance: improving cache settings could save 8 KiB of data by extending cache lifetimes for JavaScript files, and optimizing the mobile viewport could eliminate potential 300ms tap delays on mobile devices. While these issues don't currently impact Core Web Vitals metrics, addressing the caching configuration would be the most beneficial next step for maintaining peak performance as the site grows.
Why It Matters:
Inefficient cache lifetimes waste 8 KiB on repeat visits and slow down returning users.
How to Fix:
Set cache headers for Cloudflare Zaraz script to at least 1 hour (3600 seconds) instead of no-cache. Configure your web server or CDN to cache static JavaScript resources with appropriate max-age headers. Add Cache-Control headers with longer lifetimes for third-party scripts that don't change frequently.
Why It Matters:
Cloudflare Zaraz and beacon scripts could potentially impact Core Web Vitals if they grow in size.
How to Fix:
Regularly audit Cloudflare Zaraz configuration to remove unused tracking tools. Consider loading analytics scripts asynchronously or with defer attribute to prevent render blocking. Monitor script sizes and loading patterns to catch performance regressions early.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Poor cache policies waste 14KB on repeat visits and slow down returning user experience.
DNS lookup to Sentry is adding 70ms delay to LCP and creating network dependency bottleneck.
102 KiB of unused JavaScript is delaying LCP by 400ms and blocking critical page rendering.
The 601KB hero image lacks priority hints and proper optimization, contributing to the 14-second LCP.
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.