Does Page Speed Affect SEO Rankings?

Yes, page speed affects SEO rankings. Google has confirmed this officially, and it has been true since 2010 for desktop and 2018 for mobile.

But the relationship between speed and rankings is more specific than most people realise. Speed is not a dominant ranking factor the way content quality and backlinks are. And once your site crosses certain performance thresholds, getting faster does not automatically push you higher.

Here is what actually matters.

How Google measures page speed for SEO

Google does not measure raw load time in seconds for ranking purposes. Instead, it uses a set of metrics called Core Web Vitals, which measure specific aspects of how a page feels to use.

There are three Core Web Vitals that affect rankings:

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element on the page to load. Usually this is a hero image, a large heading, or a video thumbnail.

Good: Under 2.5 seconds Needs improvement: 2.5 to 4 seconds Poor: Over 4 seconds

LCP is typically the most impactful metric to fix. Slow-loading images and render-blocking resources are the most common causes.

Cumulative Layout Shift (CLS)

CLS measures visual stability. Specifically, how much the page layout shifts around while it loads. If elements jump around and cause you to click the wrong thing, that is a high CLS score.

Good: Under 0.1 Needs improvement: 0.1 to 0.25 Poor: Over 0.25

Common causes: images without defined dimensions, ads loading late, and web fonts swapping out after the page appears.

Interaction to Next Paint (INP)

INP replaced First Input Delay in March 2024. It measures how quickly your page responds when a user interacts with it, such as clicking a button or opening a menu.

Good: Under 200 milliseconds Needs improvement: 200 to 500 milliseconds Poor: Over 500 milliseconds

Heavy JavaScript is usually the main culprit for poor INP scores.

How much do Core Web Vitals actually affect rankings?

Google has described Core Web Vitals as a “tiebreaker” signal. When two pages are roughly equal in content quality, relevance, and authority, the page with better scores gets the advantage.

In practice this means:

A very fast page will not outrank a slow page if the slow page has significantly better content and far more backlinks. Speed cannot override the major ranking factors.

But a slow page can lose rankings to a faster competitor when everything else is roughly equal. And for competitive niches where the top results are close in quality, Core Web Vitals can make the difference.

There is also an indirect effect. Slow pages frustrate users. Google’s own research found that as page load time goes from 1 to 3 seconds, the probability of a user bouncing increases by 32%. From 1 to 5 seconds, that probability jumps to 90%. When users leave immediately, that sends negative signals back to Google.

What the research shows

In 2021, Cloudflare published a case study showing that after they improved a client’s LCP from 4.5 to 1.9 seconds using their CDN and image optimisation, organic traffic increased by 23% over three months. The content and backlinks had not changed.

SearchPilot, a company that runs controlled SEO experiments, ran a test in 2022 improving Core Web Vitals scores for a large ecommerce site. Pages that moved from Poor to Good saw an average ranking improvement of 1.2 positions. That sounds small, but for a site with thousands of product pages, it meant a meaningful traffic increase.

Google’s own Web Almanac data from 2023 showed that only 39% of websites pass all three Core Web Vitals thresholds on mobile. This means that if your site passes, you already have an advantage over the majority of your competitors.

How to check your Core Web Vitals

Google Search Console is the best starting point. Go to Experience in the left menu and open the Core Web Vitals report. This shows your real-user data for both mobile and desktop, grouped by pages that need improvement.

Google PageSpeed Insights at pagespeed.web.dev gives you both a lab test of any URL and real-user field data if enough traffic exists. It also provides specific fix recommendations.

Lighthouse, built into Chrome DevTools, gives you a detailed lab-based audit of any page. Open DevTools, go to the Lighthouse tab, and run an audit.

Lab data from PageSpeed Insights and Lighthouse, and field data from Search Console, will sometimes differ. Google uses field data for ranking purposes. Lab data is more useful for diagnosing specific issues.

What to fix first

Not all speed improvements have equal impact. Here is where to focus:

For LCP:

• Compress and properly size all images. Use modern formats like WebP or AVIF.
• Use lazy loading for images below the fold, but do not lazy-load your hero image.
• Add a preload hint in your HTML for your largest above-the-fold image.
• Remove render-blocking resources that delay the page from displaying.

For CLS:

• Always define width and height attributes on images and video elements.
• Reserve space for ads and embeds before they load.
• Avoid inserting content above existing content after the page loads.
• Use font-display: swap for web fonts, and preload your primary font files.

For INP:

• Reduce the amount of JavaScript running on page load.
• Break up long tasks so the browser stays responsive.
• Defer or remove non-essential third-party scripts like chat widgets and social embeds.

Mobile versus desktop

Google uses mobile-first indexing, which means it primarily evaluates your mobile page for ranking purposes. Your Core Web Vitals scores for mobile are what matter most for SEO.

Mobile scores are almost always worse than desktop scores because of smaller screens, slower processors, and variable network conditions. If you can only prioritise one, fix mobile.

A realistic view of the effort involved

Improving from Poor to Good on Core Web Vitals can take significant technical work, particularly for complex sites with lots of images, third-party scripts, and custom functionality. Sites built on Astro, which outputs static HTML by default, often start in a much better position than sites built on heavier frameworks or WordPress with many plugins.

If your scores are already in the Good range, spending weeks chasing a perfect 100 on PageSpeed Insights is not a good use of time. The gains at that point are marginal. Focus that effort on content and link building instead.

If your scores are in the Poor range for important pages, that is worth fixing. Slow pages lose users, and losing users hurts rankings through both direct signals and reduced engagement.

For information on other technical issues that can affect your rankings, see how to fix crawl errors in Google Search Console.

Frequently asked questions