Short answer
Google says Core Web Vitals are used by its ranking systems and that its core ranking systems look to reward a good page experience. It also says relevance comes first, there is no single page experience signal, and it shows the most relevant content even when page experience is sub-par. Speed helps, but it does not replace useful content.
The statements that matter
Google Search Central has two pages that answer most questions about speed and rankings. On its page experience page, Google says: "Google's core ranking systems look to reward content that provides a good page experience" [1]. In the same document's FAQ, it says: "Core Web Vitals are used by our ranking systems" [1]. Its Core Web Vitals page adds: "We highly recommend site owners achieve good Core Web Vitals for success with Search" [2].
Those are clear statements that speed is part of the picture. The same pages are just as clear about the limits.
What Google does not promise
Google states that "Google Search always seeks to show the most relevant content, even if the page experience is sub-par" [1]. It also says "There is no single signal" for page experience; ranking draws on several signals related to overall experience [1]. And the Core Web Vitals page describes good scores as aligning with "what our core ranking systems seek to reward" rather than guaranteeing a position [2].
Put together, the honest reading is this. A fast page will not outrank a much more useful slow page for the same query. When several pages are similarly helpful, a better page experience can help, and Google says as much: good page experience can make a difference where many helpful pages are available [1].
Page experience is wider than speed
Google offers a set of self-assessment questions for page experience. They ask whether pages have good Core Web Vitals, whether they are served securely, whether content displays well on mobile devices, whether content avoids an excessive amount of ads that distract from or interfere with the main content, whether pages avoid intrusive interstitials, and whether visitors can easily distinguish the main content from other content [1]. Speed is one of six questions. A fast page covered in pop-ups is still a poor experience.
Which data Google uses
The Core Web Vitals that matter for Search are real-user measurements, not lab scores. Google's CrUX overview says Google Search uses CrUX data to inform its page experience ranking factor [3]. Search Console's Core Web Vitals report is built on the same data [4]. A Lighthouse score of 100 in a lab test is not what Google looks at; field LCP, INP and CLS are.
That also means sites without enough traffic to appear in CrUX have no field data for this purpose. CrUX only includes pages and origins that are publicly discoverable and sufficiently popular [5]. Those sites should still aim for good performance, because visitors notice, but they should not expect a Core Web Vitals report in Search Console until traffic grows.
Common myths, checked against Google's wording
| Claim | What Google's documentation supports |
|---|---|
| Speed is the most important ranking factor | No. Google says it shows the most relevant content even when page experience is sub-par |
| Speed does not affect rankings at all | No. Google says Core Web Vitals are used by its ranking systems |
| A perfect PageSpeed score improves rankings | Not supported. Search uses field data from CrUX, not lab scores |
| There is one page experience score | No. Google says there is no single signal |
| Passing Core Web Vitals guarantees better positions | No guarantee is given; Google describes it as aligning with what its systems seek to reward |
How to weigh speed work against other SEO work
If your pages are failing Core Web Vitals badly, especially on mobile where most sites struggle, fixing that is worthwhile for both visitors and search. HTTP Archive's 2025 Web Almanac found only 48% of mobile websites had good Core Web Vitals [6], so passing can set a site apart from many competitors. If your pages already pass, further speed gains are mostly about visitor experience and conversions rather than search, and content, relevance and links are likely to matter more for rankings.
Speed work also has benefits Google does not measure directly. Pages that load and respond quickly are easier to use on slow connections and older phones, and they cost less to serve.
Be wary of guarantees
Because Google itself does not promise ranking gains from speed improvements, any provider promising a specific ranking result from speed work is claiming more than the documentation supports. A reasonable promise is to improve the metrics, explain the changes and measure the outcome honestly.
A worked example: two similar pages
Imagine two fictional plumbing companies in the same city with similar service pages: both clear, both covering the same jobs, both with real photos and prices. One page passes Core Web Vitals on mobile; the other loads a 3 MB slider and fails LCP badly. Google's documentation suggests this is the kind of situation where page experience can make a difference, because many similarly helpful pages are available for the same query [1].
Now change the example. One company has a thin page with two sentences and a phone number that loads instantly. The other has a detailed, genuinely useful page that loads slowly. Google says it "always seeks to show the most relevant content, even if the page experience is sub-par" [1]. Speed will not rescue the thin page. The slow detailed page would still benefit from speed work, for its visitors and in close contests, but its content is its main asset.
Speed, crawling and large sites
For most small and mid-size sites, speed matters for search mainly through page experience. Google's crawl budget guide describes a second effect, but aims it at large sites, such as sites with 1 million or more unique pages whose content changes moderately often (about once a week), or 10,000 or more pages that change daily. In Google's description, pages that load and render faster may let its crawler get through more of a site's content [7]. For a typical business site with a few hundred pages, crawl budget is rarely a practical concern. Faster server responses are good for visitors regardless, and the same caching and CDN work that helps Time to First Byte serves both purposes [8].
What to tell a manager or client
If you need to explain speed work in a sentence, this is a fair version based on Google's own wording: "Google uses Core Web Vitals in its ranking systems and recommends good scores, but relevance comes first, so speed work supports our search visibility and our visitors' experience without guaranteeing rankings." It avoids both overselling and dismissing the work, and it can be backed up by the pages quoted in this guide [2].
How to measure whether speed work helped search
Isolating the search effect of speed is hard, because rankings move for many reasons. A reasonable approach is to note the date changes were released, watch Search Console's Core Web Vitals report until the affected groups move to good, which involves a 28-day monitoring window after validation starts [4], and then compare search performance for those pages over the following months with pages that did not change. Treat any result as suggestive rather than proof, and keep the main measure of success the one you control: real-user speed.
Speed and search questions
Will passing Core Web Vitals move me up in Google?
It may help where competing pages are similarly relevant, but Google does not guarantee it and says relevance comes first.
Does Google use my PageSpeed Insights score for ranking?
Google's documentation points to real-user Core Web Vitals data from CrUX, not the lab score shown in PageSpeed Insights.
My site has no Core Web Vitals data. Am I penalized?
Google does not describe any penalty for missing data. Smaller sites often have none until traffic grows. Good performance still helps visitors.
Sources
Opened and checked on November 3, 2026.
- Understanding Google Page Experience, Google Search Central. Primary documentation, last updated September 22, 2026.
- Understanding Core Web Vitals and Google search results, Google Search Central. Primary documentation, last updated December 10, 2025.
- Overview of CrUX, Chrome for Developers. Primary documentation, last updated February 8, 2024.
- Core Web Vitals report, Search Console Help. Primary documentation, checked November 3, 2026.
- CrUX methodology, Chrome for Developers. Primary documentation, last updated June 20, 2024.
- Performance, The 2025 Web Almanac, HTTP Archive (Himanshu Jariyal, Prathamesh Rasam, Humaira and Aaron T. Grogg). Research report (secondary analysis of public datasets), published January 15, 2026, last updated May 5, 2026, based on July 2025 data.
- Crawl Budget Management, Google Crawling Infrastructure documentation, Google for Developers. Primary documentation, last updated July 22, 2026.
- The most effective ways to improve Core Web Vitals, web.dev. Primary documentation (cites HTTP Archive and Chrome data), last updated October 31, 2024.