How Important Is Page Speed for SEO?
Page speed matters for SEO, but it is a lighter signal than most speed-test tools make it look. Google confirms that Core Web Vitals, its measures of loading speed, responsiveness and visual stability, are used by its ranking systems, and it also says that Google Search “always seeks to show the most relevant content, even if the page experience is sub-par.” In practice it works more like a tiebreaker between pages that are similarly relevant, and it tends to become a serious problem when a page is slow for a large share of real visitors. Its bigger effect is on the people who arrive, because a slow page can lose visitors whether it ranks or not.

This guide sets out what Google has said about speed over the years, how it actually measures it, what the numbers in PageSpeed Insights do and do not mean, and how to decide whether speed is the thing holding your pages back or whether your effort belongs somewhere else.
What Google says about how much speed matters
Three of Google’s public statements about speed and ranking, from 2010, 2018 and today, tell the same story. When site speed first became a signal in April 2010, Google wrote that it “doesn’t carry as much weight as the relevance of a page” and that fewer than 1% of search queries were affected, at the time only English searches on Google.com. That was a small, careful start, and it is worth remembering because the 2010 date is often quoted as if speed had become a major factor overnight.
In January 2018 Google announced the “Speed Update”, which made page speed a ranking factor for mobile searches from July 2018. The announcement said the change “will only affect pages that deliver the slowest experience to users and will only affect a small percentage of queries,” and added that “a slow page may still rank highly if it has great, relevant content.” The update was aimed at the slowest pages on the web rather than at shaving tenths of a second off pages that were already reasonable.

Today’s documentation, Google’s page on understanding page experience, keeps that balance. It says there is “no single signal” for page experience, that Core Web Vitals are used by the ranking systems, and that good scores in Search Console or third-party tools do not guarantee a page will rank at the top. It even warns that “trying to get a perfect score just for SEO reasons may not be the best use of your time.” Other parts of page experience, such as avoiding intrusive pop-ups, do not directly lift rankings according to the same page, although Google still recommends them because they make a site more satisfying to use.
Read together, these statements answer the question fairly precisely. Speed is a real input, it is weighted below relevance and the quality of the content, and its effect is concentrated on pages that are clearly slow for real users. That is why speed sits inside technical SEO as one part of a sound site rather than as a strategy of its own.
Where speed can tip the result
The tiebreaker idea is the most useful way to picture it. When two pages answer a query equally well and carry similar authority, page experience is one of the things that can separate them, and Google’s page experience FAQ says as much: for queries where “there is lots of helpful content available,” a great page experience “can contribute to success in Search.” Many local service searches look like that, with several Calgary businesses offering near-identical pages for the same service.

The reverse case matters just as much. A fast page that does not answer the search well will not be pulled up by its speed, and a slow page that is clearly the best answer can still rank. If a page is stuck on page three, a faster server is unlikely to be the main reason, and the time is usually better spent on what the page says, which searches it targets and who links to it.
How Google actually measures speed
Google does not rank pages on the PageSpeed Insights score. Its ranking systems use Core Web Vitals, which come from real Chrome users rather than a simulated test, and Google publishes a “good” target for each of the three metrics.
| Metric | What it measures | Google’s “good” target |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | Within 2.5 seconds |
| Interaction to Next Paint (INP) | How quickly the page responds to a tap, click or key press | Under 200 milliseconds |
| Cumulative Layout Shift (CLS) | How much the layout jumps around while loading | Under 0.1 |
INP replaced the older First Input Delay metric in March 2024, so any guide that still lists First Input Delay as a Core Web Vital is out of date. There is more detail on what each of the three metrics measures and why it matters in a separate article.
The detail that changes how you should read your own results is the way these numbers are counted. Google’s web.dev guidance measures each metric at the 75th percentile of page loads, separately for mobile and desktop, and the Search Console report covers the last 28 days of real visits. A page passes only when the slower end of its real audience still gets a good experience. If you check your site on a new laptop over office internet, you are sitting in the fast half of that distribution, while the slower quarter of real visits, which is what the 75th percentile reflects, can come from older phones or weaker connections. A page that feels instant to its owner can still fail.

Reading PageSpeed Insights and Search Console without being misled
PageSpeed Insights shows two different things on one screen, and most of the confusion about speed comes from mixing them up. The section headed with real-user data comes from the Chrome User Experience Report, covering the previous 28 days. The big coloured score further down is a lab result: Lighthouse loads the page once in a simulated environment, and Google’s own bands call 90 or above good, 50 to 89 in need of improvement and below 50 poor. The lab score is useful for finding causes, but it can move between runs and it is not what the ranking systems use.
Small business sites run into a second problem. PageSpeed Insights only shows field data for a URL when enough real Chrome users have visited it, and Google notes that a page may lack data “if it has been recently published or has too few samples from real users.” In that case it falls back to data for the whole domain, and if even that is too thin, Search Console’s Core Web Vitals report shows “No data available.” A low-traffic local service site in Calgary, Edmonton or Vancouver can be in exactly this position for many of its pages. Google does not document what its ranking systems do when a page has no field data, so any claim that a low lab score is costing those pages rankings is a guess.
This table is a practical way to decide what to do with what you find.
| What the field data shows | What it suggests | What to do |
|---|---|---|
| Good on all three metrics | Core Web Vitals are not what is holding the page back | Leave the lab score alone and put the effort into content, targeting and links |
| Needs improvement on one metric | Borderline for the slower quarter of visitors | Fix the cause at the template level when convenient, mobile first |
| Poor on any metric | Real visitors are having a slow or jumpy experience | Treat it as a priority, because it costs visitors and enquiries regardless of rankings |
| No data available | Too few Chrome visits to measure | Use the lab LCP on mobile as a rough guide and fix anything clearly slow, without expecting a ranking change |
Why speed still matters when rankings barely move
The ranking effect of speed is modest, but its effect on the people who do arrive is direct. A visitor who waits for a blank screen on a phone can simply go back to the results and pick the next business, and nothing about that requires Google to be involved. A page that is slow for its real audience can lose some of the visitors it worked to attract, and for a service business those visitors are calls and quote requests.
Paid traffic makes the cost easier to see, because each of those lost visitors is a click you paid for. Google’s own advice to advertisers in Google Ads Help says to “see if the speed of your mobile site is costing you customers” and lists “Keep it quick” among the basics of an effective mobile site. Landing page experience is also one of the three components Google reports in Quality Score, which Google describes as a diagnostic tool and not an input to the auction, but it is a useful signal that a landing page needs work. Anyone running Google Ads to a slow landing page is paying for visits the page may then fail to keep.
What to fix first when speed is the problem
When the field data does show a problem, the causes on small business sites are usually familiar. Oversized images are a frequent culprit, especially photos uploaded straight from a camera or phone and then shrunk on screen by the theme. Other usual causes are slow server response from low-cost shared hosting, heavy themes, page builders and plugins that load scripts on every page whether they are needed or not, and third-party widgets such as chat tools, booking embeds and tracking tags.
The order matters more than the checklist. Start with the metric that is failing and the template it fails on, because Search Console groups similar URLs together and a fix to one blog or service template often repairs dozens of pages at once. A poor LCP usually points to the main image or to server response time, a poor INP to heavy JavaScript, and a poor CLS to images, ads or embeds that load without reserved space.
After a fix, give it time before judging the result. The Core Web Vitals report and the PageSpeed Insights field data both look back over 28 days, so the numbers catch up gradually, and once you start validation in Search Console it monitors the fix over a 28-day session. For the practical work itself, there is a step-by-step guide to improving loading speed that goes through each fix in order.

Where to start
So how important is page speed for SEO? Important enough that a page which is clearly slow for its real visitors should be fixed, and not important enough to justify chasing a perfect lab score while the content, keyword targeting and links still need work. Open the Core Web Vitals report in Search Console first, check whether any URL group is marked Poor on mobile, and let that answer decide how much of your time speed deserves.
If you would rather have someone look at speed alongside everything else that affects your rankings, a website audit from SEO Company To-The-TOP! weighs speed against the content and links that usually matter more. To-The-TOP! is a Calgary specialist, founded in 2007, and you can reach it at (403) 308-5949.
Contact Calgary SEO Company To-The-TOP!
Questions about anything in this article, or about your own rankings? Talk to a Calgary SEO specialist directly.
Phone: (403) 308-5949
Address: 1509 14 Ave SW, Calgary, AB T3C 0W4
Hours:
Monday to Friday: 10:00 am – 7:00 pm
Saturday: 12:00 pm – 4:00 pm
Sunday: closed
