Why page speed quietly wins rankings
Core Web Vitals still move the needle — here is what to fix first.
Fast pages rank and convert better; prioritize image weight, render-blocking scripts and server response time.
Speed is the first thing a visitor feels and the last thing most sites fix. Search engines treat it the same way: Core Web Vitals are a real input, and a slow page bleeds rankings and the readers who would have converted. The good news is that most slowdowns trace back to a handful of causes you can clear in an afternoon.
Start with the heavy hitters
Images and scripts cause the large majority of slow loads. Before anything clever:
- Serve images as WebP or AVIF, and size them to their container — a 1600px hero on a 360px phone is wasted bytes.
- Lazy-load anything below the fold, and mark the hero image as eager so it paints first.
- Defer or drop render-blocking JavaScript. A third-party widget you forgot about is often the single worst offender.
Know the three numbers
You only need to watch three metrics, and each has a clear target:
- LCP (largest contentful paint) — under 2.5s. Usually your hero image or headline.
- INP (interaction to next paint) — under 200ms. Heavy JavaScript is the usual culprit.
- CLS (cumulative layout shift) — under 0.1. Reserve space for images and embeds so nothing jumps as the page loads.
Measure on real devices
Lab scores flatter you. Your laptop on office wifi is not your reader on a three-year-old Android over patchy 4G — and it is the reader’s experience that Google’s field data records. Test on a mid-range phone and a throttled connection before you trust a green score.
Speed rarely fails alone. A fast page that targets the wrong query still loses, so pair performance work with the fundamentals: matching intent and avoiding the other common SEO mistakes, and grounding every page in real keyword research before you write a word.