Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize oldthorns.com
The cookie consent banner causes massive layout shifts (CLS: 0.14) accounting for all visual instability.
Reserve space for the OneTrust banner with CSS min-height or position it as fixed/absolute to avoid layout impact. Configure OneTrust to load synchronously or implement a placeholder div with matching dimensions before the banner loads.
A score of 29 falls in the "Poor" 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 severe performance problems with a critically low score of 29/100. The biggest issue is an extremely slow Largest Contentful Paint of 15.5 seconds, primarily caused by a cookie consent banner that's creating massive layout shifts and blocking the page from loading properly. The site is also drowning in unused JavaScript (926 KiB) and CSS (207 KiB), with render-blocking requests delaying the initial page load by over 5 seconds. Fixing the cookie banner implementation, removing unused code, and optimizing the 543 KiB of uncompressed images could dramatically improve load times and boost the performance score by 40+ points.
Why It Matters:
LCP takes 15.5 seconds with a 3-second render delay, severely impacting user experience and Core Web Vitals.
How to Fix:
Identify the LCP element (likely the OneTrust policy text div) and optimize its loading. Preload critical resources, reduce server response time from 0.12ms, and eliminate render-blocking resources. Consider lazy-loading the cookie banner after initial page render.
Why It Matters:
926 KiB of unused JavaScript and 207 KiB of unused CSS slow down page loading and block rendering.
How to Fix:
Remove or defer unused Elementor, reCAPTCHA, and Ultimate Addons scripts that aren't needed for above-the-fold content. Use WP Asset CleanUp to selectively disable plugins on specific pages. Implement code splitting to load features only when needed.
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.