Yes, but less than most people expect. Core Web Vitals are a confirmed part of Google's page experience signals, and they work as a tiebreaker between pages of similar relevance rather than as a way to outrank better content. The larger cost of a slow site is behavioral: people leave before the page renders, and that lost revenue never appears in any ranking report.
What Google actually measures
| Metric | What it measures | What a user experiences |
|---|---|---|
| Largest Contentful Paint | How long until the main content appears | Staring at a blank or half-built page |
| Interaction to Next Paint | How quickly the page responds to a tap or click | Tapping a button and nothing happening |
| Cumulative Layout Shift | How much the layout moves while loading | Content jumping as you go to tap it |
These are measured from real visits to your site, not from a lab test. That distinction matters: a perfect score in a testing tool and a poor score in the field report are entirely compatible, and the field data is the one Google uses.
Where speed sits among ranking signals
Relevance and content quality decide who is in the running. Speed helps decide between pages already close to each other. A fast page with a weak answer does not outrank a slow page with the right one.
This is worth saying plainly because performance work is visible, measurable and satisfying, which makes it an easy place to spend a budget that would do more elsewhere.
The cost that does not show up in rankings
People abandon slow pages. That happens before any analytics event fires on most setups, which means the visitors you lose to load time are largely invisible in your own reporting. You see the sessions that survived.
On mobile connections, with a real phone on a real network, the gap between a two-second and a six-second load is the gap between a visit and a bounce back to the results page. Google does notice that pattern, which is a second-order way speed affects what you see.
What usually causes it
- Images, uncompressed and served at desktop dimensions to phones. The most common cause by a distance and the easiest to fix.
- Third-party scripts. Chat widgets, tag managers, heat mapping, five analytics tools. Each one is someone else's server between your visitor and your page.
- Render-blocking CSS and JavaScript loading before anything can be drawn.
- Web fonts loading late and shifting the layout when they arrive.
- Server response time, which no amount of front-end work will fix.
How to work out whether it is your problem
- Open the Core Web Vitals report in Search Console. This is field data from real visits, and it is the version Google uses.
- Check how many URLs are in the poor bucket, and whether they are pages that matter.
- Test a few of those pages individually to find what is causing it.
- Compare against the sites ranking above you. If they are slower than you and still winning, speed is not your gap.
Fix speed because slow sites lose customers. Treat any ranking benefit as a bonus. Teams that pursue it the other way around tend to spend months chasing a score and get a small result.