You invested in a website. It looks professional. The content is solid. You've done some SEO work and your on-page scores are respectable. But something is still holding you back in search — and nobody has been able to pinpoint exactly what.
In many cases, the culprit is your website's loading speed. Specifically, a metric called the Largest Contentful Paint (LCP) — and there's a specific failure pattern that explains why so many well-built websites are being quietly penalised by Google.
We call it the Ghost Load.
What Is LCP and Why Does Google Care?
Largest Contentful Paint measures how long it takes for the most prominent visual element on your page — usually a hero image or large heading — to fully appear on screen. It's one of the Core Web Vitals, used as a direct ranking signal.
Google's threshold:
- Under 2.5 seconds: Good
- 2.5 to 4 seconds: Needs improvement
- Over 4 seconds: Poor
Many businesses we audit have LCP scores in the 8, 12, even 19-second range. In a world where 50% of users abandon a page that takes more than three seconds to load, those businesses are quietly losing customers before they've had a chance to make any impression.
The Ghost Load: Symptoms
The Ghost Load is a diagnostic pattern we see repeatedly:
- LCP is extremely high (often 10–20+ seconds on mobile)
- Total Blocking Time (TBT) is very low (often under 50ms)
This combination matters. TBT measures how long JavaScript blocks the browser. A low TBT means your code is clean. The bottleneck is your visual assets.
When LCP is terrible but TBT is excellent, the cause is almost always one of three things:
1. An uncompressed hero image. A full-resolution JPEG or PNG might be 3–5MB. The fix is converting your hero image to WebP or AVIF and compressing it under 100KB — a 98% reduction with no visible quality loss.
2. Server location. A US-hosted site serving Australian users adds round-trip latency on every request. Migrate to Australian hosting or add a CDN like Cloudflare.
3. The lazy-load mistake. Lazy loading is great for images below the fold. It's catastrophic for your hero image. Add fetchpriority="high" to your hero image tag instead.
Other Hidden Performance Killers
Uncompiled CSS frameworks. Loading Tailwind/Bootstrap from a CDN ships 3–4MB of CSS when only 2% is used. Replace with a compiled, purged bundle.
Render-blocking scripts. GTM, analytics, and widgets in <head> block content rendering. Move them to async or defer.
Above-the-fold animations. Lighthouse waits for animations to complete before recording LCP. A 2-second hero animation = 2 seconds added to LCP. Disable entrance animations on mobile.
Oversized DOM. More than 800 elements adds meaningful render overhead. Visual page builders often produce 1,400–2,000+.
What a Technical Fix Actually Achieves
Fixing a Ghost Load (compress hero, enable Cloudflare, remove lazy-load from hero) typically moves an LCP from 15–19 seconds to under 3 seconds. That's the difference between a failing Core Web Vitals score and a passing one — which Google uses as a ranking signal.
For a local service business ranked #5, this kind of performance improvement can be enough to push them into the top three.
Diagnose Your Own Site
Run your homepage through Google's PageSpeed Insights and Lighthouse. Look at:
- LCP — under 2.5 seconds?
- TBT — if low but LCP is high, you have the Ghost Load
- Largest Contentful Paint element in Diagnostics — tells you exactly which element is causing the delay
- "Reduce unused CSS" and "Eliminate render-blocking resources" — your quick wins
If LCP is over 4 seconds and TBT is under 200ms, start with your hero image. That single fix delivers the biggest improvement for the least effort.
Back to Academy