“Slow” is a matter of opinion until someone measures it. Google has measured it, published the numbers it considers acceptable, and built a free tool that compares any page against them. That makes this one of the few SEO questions with a definite answer for your own site.
The numbers Google uses
Google judges speed with three measurements called Core Web Vitals: one for loading, one for how quickly the page responds, and one for how much it jumps about. Our lesson, Core Web Vitals, explained, covers what each one means. For each, Google sets a “good” mark and a “poor” mark, and anything between the two is rated “needs improvement”.
- Loading (LCP): good at 2.5 seconds or less, poor above 4 seconds.
- Responsiveness (INP): good at 200 milliseconds or less, poor above 500 milliseconds.
- Stability (CLS): good at a score of 0.1 or less, poor above 0.25.
The marks are applied at the 75th percentile, with phones and computers counted separately. In plain terms, three out of four visits have to come in under the mark. A page that loads in a second on the office connection and in six on a customer’s phone can fail, because the measurement comes from visitors’ own devices.
How to check your own site
- Open PageSpeed Insights at pagespeed.web.dev and enter the address of a page.
- Look at the top section first. If it has data, it shows what real Chrome users experienced over the previous 28 days, and whether the page passed the Core Web Vitals assessment.
- Check the mobile tab as well as the desktop tab. The two are measured separately.
- Then read the lower section, which is a single test run in a simulated setting, with a score out of 100 and a list of suggestions.
- Repeat for your busiest pages, not just the home page.
A small site may see no real-visitor data at all, because there has to be enough of it to report. In that case the simulated test is all there is. Google rates a score of 90 or above as good and 50 to 89 as needing improvement, and it warns that the two kinds of result can differ, since one test on one simulated device cannot stand in for every visitor.
How much speed matters to Google
Less than many sales pitches suggest, and more than nothing. Google says its core ranking systems look to reward a good page experience, of which Core Web Vitals are one part, and that there is no single page experience signal. It also says Search always seeks to show the most relevant content, even if the page experience is sub-par. Where many pages are equally helpful, a good experience can contribute to success in Search.
So a fast page with the wrong content will not outrank a slow page with the right content. Where two businesses offer much the same information, speed is one of the things that can separate them. Bing takes a similar line: it lists page load time among its ranking parameters and notes that slow pages can lead a visitor to leave.
How much it matters to customers
Here the case is stronger, because customers do not weigh relevance against speed: they wait or they leave. Google’s web.dev site collects published examples. The BBC found it lost an additional 10 per cent of users for every additional second its site took to load. Vodafone reported that a 31 per cent improvement in LCP increased sales by 8 per cent.
Those are very large websites, and a local business should not expect the same percentages, only the same direction. The same page also explains why phones are hit hardest: mobile devices have limited processing power and memory, and a page that ships a lot of code makes them work for it.
What to fix first
Start with whichever of the three measures is rated worst on the pages that get the most visits. If that is loading, Google’s guidance on LCP points to a few places to look.
- The server’s first response. Google rates a time to first byte of 0.8 seconds or less as good, and says a high figure can make a 2.5 second load difficult or even impossible. Slow hosting shows up here.
- Redirects. Each hop from one address to another is time spent before the page starts. Google’s advice is to keep them to a minimum.
- The main image. It should not be set to lazy-load, which delays it on purpose, and it should be no larger than the space it fills.
- Distance. A content delivery network keeps copies of the site closer to visitors.
Where to go next
Our free website health check measures how long the server takes to answer, counts the redirects, and flags scripts that hold up the first paint and images with no size set. If the results point to work you would like done for you, page speed and technical performance are part of Optimisation, and a rebuild on faster foundations is covered under Websites.
Sources
- Web Vitals (web.dev) web.dev
- How the Core Web Vitals metrics thresholds were defined (web.dev) web.dev
- About PageSpeed Insights (Google for Developers) developers.google.com
- Understanding Core Web Vitals and Google search results (Google Search Central) developers.google.com
- Understanding page experience in Google Search results (Google Search Central) developers.google.com
- Why does speed matter? (web.dev) web.dev
- Optimize Largest Contentful Paint (web.dev) web.dev
- How Bing delivers search results (Microsoft Support) support.microsoft.com