Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize staging.freshairfitness.co.uk
222 KiB of unused JavaScript and 53 KiB of unused CSS block rendering and delay LCP by 450ms total.
Remove unused Bootstrap CSS classes or use PurgeCSS to strip unused styles. Defer Google Tag Manager and Font Awesome loading until after page load. Use WP Asset CleanUp to conditionally load scripts only where needed.
A score of 65 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 WordPress site has poor performance with a score of 65/100, primarily due to severe layout stability issues that cause content to jump around as the page loads (Cumulative Layout Shift score of 0.73). The biggest problem is that the page takes 8.3 seconds to become fully interactive, mainly caused by 222 KiB of unused JavaScript from Google Tag Manager and tracking scripts, plus 53 KiB of unused CSS from Bootstrap. Additionally, web fonts are loading without proper optimization, causing text to shift when they load, and images lack proper width/height attributes which contributes to the layout instability. Removing unused code, optimizing font loading with font-display: swap, and adding explicit image dimensions could improve the score by 25+ points and dramatically reduce the jarring visual shifts users experience.
Why It Matters:
Custom fonts cause 0.73 CLS score due to text repositioning when fonts load, severely impacting user experience.
How to Fix:
Add font-display: swap to your custom Odudosoft fonts in CSS. Use font metric overrides or size-adjust to match fallback fonts. Preload critical font files using <link rel='preload'> in your WordPress theme's header.php.
Why It Matters:
3.6MB of assets load without caching headers, forcing repeat downloads and delaying LCP by 850ms.
How to Fix:
Configure WordPress caching plugin like W3 Total Cache or WP Rocket with 1-year expiry for static assets. Set cache headers for images, videos, and fonts in .htaccess or server config. Enable Gzip compression for all text resources.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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.