Why Google Sometimes Still Ranks Slow Websites
A client once showed me a competitor's site that took over six seconds to load on mobile. No caching worth mentioning, images served at full resolution, a theme that looked like it hadn't been touched since the early days of flat design. Their own site was clean, fast, and properly optimised. The competitor still sat two positions higher. That kind of thing is frustrating until you understand what Google is actually weighing up when it decides who goes where.
On this page
Speed Is One Signal Among Many
Core Web Vitals are a confirmed ranking factor. They are not a dominant one, and treating them as though they were leads to a lot of wasted effort.
Google processes hundreds of signals when it decides which pages to surface. Content relevance sits at the top of that pile, followed by backlink authority, topical depth, and how well a page answers the query. Page speed matters, but in Google’s overall weighting it sits considerably further down. A page that loads in 4 seconds and comprehensively covers a subject will, in most cases, outrank a page that loads in under a second but says very little. That might feel counterintuitive if you’ve spent time chasing performance scores, but it’s consistent with how Google has always behaved. It is trying to find the most useful result, not the fastest one.
Where speed becomes a real differentiator is when two pages are closely matched on everything else. If content quality, authority, and relevance are roughly equivalent, a faster site does pull ahead. But that scenario is less common than most people assume. In practice, the gap in content quality between competing pages is usually wide enough that a slow site with something useful to say keeps its rankings despite the performance deficit, often comfortably.
What the Slow Site Usually Has That the Fast One Doesn’t
The sites that hold rankings despite poor load times almost always carry something that took years to build, and that a faster competitor hasn’t had time to accumulate.
The most common factor is domain age combined with a backlink profile that grew organically over a long period. A site that has been earning links since the mid-2000s carries a weight of trust that no amount of performance tuning can replicate overnight. Google interprets those links as editorial endorsements from across the web, and that accumulated trust tends to outweigh a slow server response, at least until a faster rival closes the content gap too. You see this pattern most often in established industries where a few older sites have owned the conversation for so long that newer, technically cleaner competitors are still working their way up.
Topical coverage plays a big part in this too. A slow site that has covered every angle of a subject, published consistently, and built up internal linking across dozens of pages gives Google a complete picture of its authority on that topic. A look at what Google weighs when ranking makes clear that topical depth carries real weight, and it is the kind of depth that only comes with time.
Click-through history matters as well. A site users have clicked on, returned to, and spent time with has behavioural signals that reinforce its position. That track record doesn’t vanish the moment a faster site appears.
How Google Measures Page Experience
Google does not use the score you see on PageSpeed Insights to decide rankings. That score comes from a lab test, a simulated run against a fixed set of conditions.
What Google uses is field data from the Chrome User Experience Report, known as CrUX. CrUX collects real measurements from real Chrome users visiting real pages, aggregated over a rolling 28-day window. A site might score 54 in the lab and still show green passes in CrUX, because the people visiting it on decent connections in typical conditions are loading it well within the bands Google cares about.
Lab scores vs field data
The lab test is a diagnostic tool for finding problems. CrUX is what feeds into Google’s Page Experience signal. Treating them as the same thing leads to a lot of wasted effort chasing a number that Google is not watching.
A local services site with modest traffic and a loyal returning audience on fast broadband might produce consistently clean CrUX data, even if a PageSpeed test run on a throttled mobile connection makes it look sluggish on paper. The score you see is not the score that matters.
What the passing bands actually require
Pass Largest Contentful Paint under 2.5 seconds for at least 75% of visits, keep Cumulative Layout Shift below 0.1, and meet the Interaction to Next Paint threshold, and Google considers the experience good regardless of what any lab number says.
The Pass/Fail Nature of Core Web Vitals
Google’s Core Web Vitals scoring works on a pass/fail basis, not a continuous scale that rewards every incremental improvement. Once a page clears the ‘Good’ band on Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift, it has done its job in the algorithm’s eyes.
A site loading in 1.8 seconds and one loading in 0.9 seconds can sit at exactly the same position in the rankings, because both have cleared the threshold and neither earns anything extra for the gap between them. That binary nature is the part most people miss when they’re puzzling over why a noticeably slower competitor keeps outranking them.
The practical consequence is that PageSpeed scores mean less than whether the passing bands are met. Chasing a perfect 100 on Lighthouse when you’re already in the ‘Good’ range is effort spent on something Google cannot distinguish from a score of 75.
That’s not an argument against optimising further. Faster pages convert better, retain visitors longer, and reduce bounce rates on mobile. But the ranking benefit stops at ‘Good’, so if a slow site has cleared that bar and your faster site hasn’t, the algorithm will not save you from the comparison.
When Speed Does Flip the Result
Speed rarely decides rankings on its own. But there are specific situations where it tips the balance.
The clearest case is a closely contested query where the top few results are near-identical in authority, backlink profile, and content depth. Google has no strong editorial reason to prefer one over another, so the signals it can measure precisely start to carry more weight. Page Experience is one of those signals. A 2.1-second LCP against a competitor’s 4.8-second one stops being noise and starts being a differentiator.
The same dynamic shows up on mobile-heavy traffic, where Core Web Vitals scoring is measured against real-world mobile data, not a desktop proxy. A page that loads cleanly on a mid-range Android phone on a 4G connection is serving that audience better, and Google’s data reflects it. If you’ve ever wondered why your PageSpeed score doesn’t map neatly to your position, this is often why. The relationship is conditional, not constant.
Where speed matters most
Thin-content pages are where speed becomes the most decisive factor. A location page, a category archive, or a sparse product listing often has little else for Google to weigh up. No depth of content, no strong E-E-A-T signal, nothing that clearly separates it from the next page in the results. In that vacuum, a fast, stable page experience is one of the few real edges left.
What This Means for Your Own Site
Speed improvements are worth doing, but they work best when they sit inside a broader effort to make your site cleaner and more credible overall.
If a competitor has years of quality backlinks, a well-structured site, and content that answers what people are searching for, shaving 0.4 seconds off your Largest Contentful Paint is unlikely to flip the rankings on its own. What speed work does do is remove a reason for Google to doubt you. A slow, bloated site signals neglect, and that matters at the margins. Fix the performance issues because they make the site better for real visitors, because they reduce bounce rates, and because they contribute to a trustworthiness that accumulates across everything Google evaluates. Think of it as tidying up the foundations rather than pulling a lever labelled “rank higher”.
The sites that tend to see meaningful movement after a speed pass are those where performance was genuinely terrible and the rest of the site was already in reasonable shape. If your PageSpeed scores are sitting in the red and you’ve never looked under the bonnet, there is probably real ground to recover. But if you’re chasing a stronger domain with a tidier score, the gap won’t close on speed alone.
There are often less obvious reasons a site stays slow even after the obvious fixes have been made. Getting those sorted is the unglamorous part of the job, and it tends to take more time than people expect.