Does Website Speed Affect Google Rankings?

The short answer is yes. Website speed is a confirmed Google ranking factor. The longer answer is that it matters more in some contexts than others, and chasing a perfect score on PageSpeed Insights is not the goal — meeting the thresholds that Google's algorithm actually uses is.

Here is what is real, what is overstated, and what to focus on if you want speed improvements to actually move your rankings.

When Google made speed an official ranking factor

Google has confirmed page speed as a ranking signal three times, each time with increasing specificity:

2010: Google announced desktop page speed as a ranking signal for a small percentage of queries
2018: Speed became a mobile ranking factor — the "Speed Update" — affecting the slowest pages most significantly
2021: Core Web Vitals became a confirmed ranking signal as part of the Page Experience Update, combining LCP, CLS, and FID (later replaced by INP)

Each update moved the goalposts from a vague "speed matters" to specific, measurable thresholds that Google's algorithm evaluates.

What Core Web Vitals actually measure

Core Web Vitals are the three metrics Google uses to score page experience:

LCP — Largest Contentful Paint How long until the largest visible element (usually a hero image or headline) finishes loading. Google's threshold: under 2.5 seconds is "good," 2.5–4s is "needs improvement," over 4s is "poor."

INP — Interaction to Next Paint How quickly the page responds when a user taps or clicks. Under 200ms is "good," 200–500ms is "needs improvement," over 500ms is "poor." This replaced FID in March 2024.

CLS — Cumulative Layout Shift How much the page layout shifts around as it loads — images popping in, fonts swapping, buttons moving. Under 0.1 is "good." A high CLS score is what makes pages feel janky and unreliable on mobile.

A page that scores "good" on all three is in the green zone. A page with one or more "poor" scores is being actively penalised relative to competitors in the green zone.

How much does speed actually affect local rankings?

Speed is a tiebreaker, not a trump card. Google's algorithm weights relevance, authority, and content quality higher than page experience in most cases. A slow website with highly relevant content and strong local signals will typically outrank a fast website with thin content for competitive queries.

But tiebreakers matter. In a local market where the top three competitors all have decent content and GBP profiles, the one with Core Web Vitals in the green zone gets the edge. And in mobile search — which is the majority of local queries — the threshold effect is more pronounced: pages below certain speed benchmarks are filtered from consideration entirely for some rankings.

Google's own documentation on Page Experience states: "Page experience is used as a tiebreaker when there are many pages that may be similarly relevant to a search query."

The mobile-first reality for local businesses

Google uses mobile-first indexing — the mobile version of your site is what Google evaluates for rankings. This is particularly significant for local service businesses because local searches are predominantly mobile.

A site that scores 85 on desktop PageSpeed and 42 on mobile is being ranked on the 42. Desktop performance is largely irrelevant to your search position.

Run PageSpeed Insights on your site right now and look specifically at the mobile tab. If your score is below 50, you have a ranking problem that is actively costing you position. If it is 50–70, there is meaningful improvement available. If it is above 70, you are competitive — further optimisation is diminishing returns unless you are in an extremely competitive local market.

What actually improves speed (and rankings)

High impact:

Compress and resize images, convert to WebP — usually the single biggest improvement available
Switch from a page builder (Elementor, Divi, Wix) to a lean framework — this alone can move a score from 40 to 90+
Fix render-blocking JavaScript — scripts that load before the page content delay everything

Medium impact:

Enable caching at the hosting level
Move to faster hosting or add a CDN
Self-host Google Fonts with font-display: swap

Low impact (despite being frequently recommended):

Minifying CSS and JS — modern build tools do this automatically; manual minification rarely moves the needle significantly
Removing Google Analytics — the performance cost is real but small; the data loss is usually not worth it

The PageSpeed score vs. the field data distinction

PageSpeed Insights shows two types of data: Lab data (simulated, from a controlled test environment) and Field data (real-world measurements from Chrome users visiting your site). Google's ranking algorithm uses field data, not lab data.

This means your PageSpeed score and your actual ranking signal can differ. A site with a lab score of 60 that has field data showing good Core Web Vitals is in better shape for rankings than a site with a lab score of 80 and poor field data. Field data is collected over 28 days from real visits — it takes time to update after optimisations.

The bottom line

Website speed affects your Google rankings — confirmed, measurable, and more important on mobile than desktop. The practical target for local businesses is Core Web Vitals in the "green" zone on mobile: LCP under 2.5s, INP under 200ms, CLS under 0.1. Getting there usually requires image optimisation and, in many cases, rebuilding on a more efficient platform than a drag-and-drop page builder.

Speed is not everything. But in a competitive local market, a slow website is a handicap you are paying for every day in lost rankings.