Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize cgbabyclub.co.uk
The main thread is blocked for 2.8 seconds by heavy script evaluation and layout calculations, creating poor user experience.
Break up long-running JavaScript tasks using setTimeout or requestIdleCallback. Reduce DOM queries that trigger forced reflows in site.js. Move heavy computations to Web Workers where possible to keep the main thread responsive.
A score of 53 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 53/100, primarily due to excessive JavaScript blocking the main thread for 2.8 seconds and an extremely slow Largest Contentful Paint of 16.3 seconds. The biggest issue is unused JavaScript code (476 KiB) from the main site.js file and Google Tag Manager, which is significantly delaying page interactivity and visual loading. Additionally, render-blocking CSS and JavaScript files are preventing the page from displaying content quickly, with an estimated 1.8 second improvement possible by deferring these resources. Reducing unused code, optimizing script loading, and implementing proper resource prioritization could dramatically improve this site's performance and user experience.
Why It Matters:
Critical CSS and JavaScript files are blocking initial page render, delaying both FCP and LCP by 1.8 seconds.
How to Fix:
Defer non-critical CSS by adding media='print' onload='this.media="all"' to stylesheets. Inline critical above-the-fold CSS directly in HTML. Move JavaScript execution after DOM content loads using defer or async attributes for non-essential scripts.
Why It Matters:
476 KB of unused JavaScript is being downloaded, wasting 2.3 seconds of LCP time and blocking user interactions.
How to Fix:
Use webpack-bundle-analyzer or similar tools to identify dead code in site.js (278KB unused). Remove unused Google Tag Manager events and OneTrust features. Implement code splitting to load only necessary JavaScript per page.
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
The oversized logo image wastes 97 KiB and delays LCP by 450ms while being displayed much smaller than its actual size.
126 KiB of unused JavaScript from Google Analytics and GTM delays LCP by 900ms and wastes bandwidth.
Render blocking CSS and fonts delay LCP and FCP by 1,050ms, preventing users from seeing content immediately.
Award images are oversized by 441KB and lack explicit dimensions, causing layout shifts.