Site Speed and SEO: Does Page Speed Affect Your Google Ranking?

June 5, 2025Updated October 14, 2026Advice7 min read

Yes, but modestly. Google says its ranking systems use Core Web Vitals, yet relevant content still comes first and good scores do not guarantee top positions. The targets are a Largest Contentful Paint (LCP) of 2.5 seconds or less, an Interaction to Next Paint (INP) of 200 milliseconds or less and a Cumulative Layout Shift (CLS) of 0.1 or less, measured at the 75th percentile of real visits.

Core Web Vitals: what Google measures

Core Web Vitals are metrics that describe real user experience. There are three, and web.dev recommends assessing them at the 75th percentile of page loads, for mobile and desktop separately:

LCP (Largest Contentful Paint): how long the largest visible element takes to load. Good: 2.5 s or less. Needs improvement: up to 4 s. Poor: over 4 s.
INP (Interaction to Next Paint): how quickly the page responds to interactions. Good: 200 ms or less. Needs improvement: up to 500 ms. Poor: over 500 ms.
CLS (Cumulative Layout Shift): how much the layout jumps while loading. Good: 0.1 or less. Needs improvement: up to 0.25. Poor: over 0.25.

INP replaced First Input Delay (FID) as a Core Web Vital and became stable in 2024. Older guides that mention FID, or that give a stricter LCP target of 1.2 seconds, are out of date.

How Google uses these metrics

Google's page experience rollout began in June 2021 on mobile. Its documentation states that Core Web Vitals are used by its ranking systems, and also that Google "always seeks to show the most relevant content, even if the page experience is sub-par". It adds that good results in Search Console or in third-party tools do not guarantee top rankings.

In practice, page experience matters most when several pages are similarly helpful. Speed also affects what happens after the click: a slow page loses visitors whatever its ranking.

Why many WordPress sites struggle

The 2025 HTTP Archive Web Almanac reports that about 45% of WordPress sites pass Core Web Vitals on mobile, one of the lowest rates among the content management systems it compares. Typical causes are pages generated on the server for each request, many plugins each adding JavaScript and CSS, and heavy themes.

Caching plugins help, but they cannot remove JavaScript that plugins load. This is an average across all WordPress sites, and a carefully built one can pass.

What actually improves LCP

Pre-rendering pages as static HTML, so the server has little to do per request.
A content delivery network, serving pages from a location close to the visitor.
Image optimisation: modern formats such as AVIF or WebP, correct sizes, lazy loading below the fold and a prioritised hero image.
Font loading: font-display: swap and preloading only the fonts that are critical.
Less render-blocking CSS and JavaScript, and removal of third-party scripts you do not need.

Google recommends server-side or pre-rendering because it makes a site faster for users and crawlers, and not every bot can run JavaScript. Googlebot does render JavaScript, so a JavaScript-heavy site can still be indexed, but pre-rendered HTML is simpler and faster.

CLS: the layout that jumps

CLS measures unexpected movement of content while the page loads, for instance when an image without set dimensions pushes the text down or a banner appears above what you were reading.

To reduce it, give images explicit width and height, reserve space for content that loads later such as ads, embeds and cookie banners, and avoid inserting content above existing content after the first render.

INP: responsiveness

INP looks at how long the page takes to respond to clicks, taps and key presses across the visit. Long JavaScript tasks are the usual cause, so ship less JavaScript, split heavy code and defer scripts that are not needed immediately.

How to measure your Core Web Vitals

Search Console, Core Web Vitals report: field data grouped by page type, for mobile and desktop.
PageSpeed Insights: shows field data from the Chrome User Experience Report when available, plus a Lighthouse lab test.
Chrome DevTools, Performance panel: a detailed recording of loading and interactions.

Field data reflects real visitors and is what counts. Lab tests such as Lighthouse are useful to find causes, but their score is not the same thing as Core Web Vitals.

What we do in practice

We check every site with Lighthouse and the Core Web Vitals thresholds above before launch, and look at field data in Search Console once real visits come in. If your site struggles to rank despite good content, performance may be one factor, but check content, structure and whether search engines and AI tools can read your pages as well.