Search Console site speed: find and fix slow pages
Short answer Open the Core Web Vitals report, start with Mobile, and click each Poor issue. Search Console lists slow pages in groups of similar pages, using 28 days of real Chrome visits. Fix Poor groups first, starting with the pages that bring customers, test them in PageSpeed Insights, then click Start Tracking for a 28-day check.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow to find slow pages in Search Console
Search Console is free: Google calls it "a free service offered by Google" (Search Console Help: About Search Console). Its speed tool is the Core Web Vitals report. Five steps:
| Step | Do this | What you see |
|---|---|---|
| 1 | Open the Core Web Vitals report | Two charts: Mobile and Desktop |
| 2 | Click Open report next to Mobile | A chart of Poor, Need improvement and Good URLs, and a table of issues |
| 3 | Click a Poor row, such as an LCP issue | The issue page, with example URLs |
| 4 | Click an example URL | Other pages in the same group, with a link to test them |
| 5 | Run the PageSpeed Insights test from there | What to fix on that page |
Start with Mobile. Google ranks the mobile version of your site, as our guide to Core Web Vitals and ranking explains.
What the Core Web Vitals report shows
It shows how real visitors experienced your pages, not a lab test. The data comes from the Chrome User Experience Report (CrUX), anonymous speed data from Chrome users, over the last 28 days (Search Console Help: Core Web Vitals report).
Each page group is judged on three measures:
| Measure | Plain meaning | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main photo or text appears | 2.5 s or less | Over 4 s |
| INP (Interaction to Next Paint) | How long the page takes to react to a tap or click | 200 ms or less | Over 500 ms |
| CLS (Cumulative Layout Shift) | How much the page jumps while loading | 0.1 or less | Over 0.25 |
Thresholds: Search Console Help: Core Web Vitals report. In between is "Need improvement." INP replaced FID (First Input Delay) on March 12, 2024 (web.dev). A guide still telling you to fix FID is out of date.
Three rules explain most of what owners find confusing:
- Pages come in groups. Google puts pages with a similar experience together, on the assumption that they share a template and the same cause (same help page). Fixing one service page template can fix the whole group.
- The worst measure wins. A group with Poor CLS and Good LCP is Poor.
- It's a sample. Only indexed pages appear, and not all of them.
"The report is not designed find the status of a specific URL, but rather to see your site's performance as a whole, and troubleshoot issues affecting multiple pages on your site." (Search Console Help: Core Web Vitals report)
To check one page, run PageSpeed Insights on it directly.
Why does the report say "No data available"?
Either the property is new, or too few Chrome visitors reached your site for Google to report on that device type (Search Console Help: Core Web Vitals report). This is common for a small local business.
When a page group is too small, Search Console rolls it into one group for the whole site (the "origin"). If even that has too little data, the report stays empty (same page). You aren't penalized for this. Test your key pages in PageSpeed Insights instead. Its lab test works with no visitor data; its real-visitor section may fall back to your whole site or be missing (PageSpeed Insights: About PageSpeed Insights).
Which slow pages should I fix first?
Google gives the order in its help page:
"We recommend fixing everything labeled "Poor" first, then prioritize your work either by issues that affect the most URLs, or by issues that affect your most important URLs." (Search Console Help: Core Web Vitals report)
For a service business, "most important" means the pages people book or call from: home page, main service pages, the contact or booking page. Inside a group, Google lists pages by impressions, highest first, so the top ones weigh most on the group's status (same page).
Not a developer? Google says to sort the issues, then share the report with whoever maintains your site. The Share button gives a link to that one issue page only, with no other access to your account (same page).
How do I find what's slowing a page group?
Open an example URL and run PageSpeed Insights from it. Its lab section lists specific fixes for that page. Its numbers may not match the group's, because one page can be an outlier, and PageSpeed Insights ignores URL parameters while Search Console doesn't (Search Console Help: Core Web Vitals report).
Google's help page gives two rules of thumb for any page:
| Check | Google's guide |
|---|---|
| Page weight | Under 500 KB for the page and everything it loads |
| Number of files | 50 or fewer for best speed on mobile |
Source: Search Console Help: Core Web Vitals report.
Typical causes by failing measure:
| Failing | Usual cause on a small business site | First fix |
|---|---|---|
| LCP | Big header photo, slow hosting | Resize and compress the top image |
| INP | Chat widgets, trackers, booking embeds | Remove scripts you don't use |
| CLS | Images, banners or embeds with no set size | Reserve their space in the layout |
The deeper fixes per measure are in Core Web Vitals and ranking. On Wix or Squarespace you control images and add-ons, not the server; see Wix, Squarespace or WordPress for SEO.
How do I tell Google I fixed it?
On the issue page, click Start Tracking. Search Console then watches that issue for 28 days. If no page shows it in that window, the issue counts as fixed (Search Console Help: Core Web Vitals report).
"Start tracking does not trigger re-indexing or any other active behavior from Google." (Search Console Help: Core Web Vitals report)
So it won't speed anything up. It only tells you whether real visitors now get the faster page.
| Status | Meaning |
|---|---|
| Started | Tracking began; no remaining cases found yet |
| Looking good | Every case checked so far is fixed |
| Passed | All pages passed |
| Failed | One or more pages still have the issue |
Statuses: same page. If it fails, fix again and click Start new validation on the details page. You don't need to watch daily. Google says Search Console emails you when it finds new issues, and suggests a check about once a month (Google Search Central: Get started with Search Console).
My status changed, but I didn't change anything
Google's help page names the usual reasons: many pages sat on the edge of a status, then something site-wide nudged them over, such as a traffic spike or a slower image service. Less often, a browser update or more visitors on slow networks does it. Data from all countries is combined, so a lot of traffic from places with slow connections drags the score down (Search Console Help: Core Web Vitals report). Check the group's numbers: if they sit right at a threshold, a small change explains it.
Other Search Console reports for speed
- Crawl Stats (under Property settings) shows how fast your server answers Google's crawler. Google says a site with fewer than a thousand pages "should not need to use this report" (Search Console Help: Crawl Stats report).
- Mobile Usability no longer exists. Google retired the report and the Mobile-Friendly Test starting December 1, 2023 (Google Search Central Blog, April 2023). Use the Mobile tab of the Core Web Vitals report and PageSpeed Insights.
Example
Illustrative cases, not measured results.
A roofer with 40 Poor mobile URLs
All 40 are city pages built on one template, in one LCP group. A 3 MB header photo is shared by every page. Compressing it fixes the group; he clicks Start Tracking and gets Passed after the 28 days.
A salon with "No data available"
Too few Chrome visitors to report. The owner runs PageSpeed Insights on the home page and the booking page, finds a booking widget slowing taps, and moves it to load after the page.
An accountant whose status dropped overnight
Nothing changed on the site. The group's LCP sat at 2.4 seconds, right at the edge; a slower image host pushed it to 2.6. A faster host brings it back.
FAQ
Is the Core Web Vitals report free?
Yes. It's part of Search Console, which Google provides free. PageSpeed Insights, which the report links to for each page, is also from Google.
How long does Search Console take to show my speed fix?
Up to 28 days. The report uses the last 28 days of real visits, and Start Tracking watches for 28 days.
Why does PageSpeed Insights say my page is fine when Search Console says Poor?
Search Console judges a whole group of similar pages, and one page can be an outlier. Compare the real-visitor section, not the lab score.
Why isn't my page in the report?
The report shows only a sample of indexed pages. Groups with too little data are merged into the whole-site group or left out.
Does Start Tracking make Google recrawl my pages?
No. Google says it only restarts a four-week monitoring clock on real-visitor data (Search Console Help: Core Web Vitals report).
Different for you?
- Want to know how much speed matters to ranking: Core Web Vitals and ranking.
- New to the other reports: Google Search Console for a small business.
- Fast site, still no calls: website not getting leads.
- Pages missing from Google, not slow: crawled or discovered, currently not indexed.
- Want slow pages found and fixed for you: Website Agent.