Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Core Web Vitals data: decide which pages to fix first

Updated · 5 min read

Short answer Fix Poor pages first, and among those, the ones that bring the most search clicks or bookings. Google's own advice is Poor before Need improvement, then the issues hitting the most pages or your most important ones. Pull status from Search Console's Core Web Vitals report and clicks from its Performance report, then fix the shared template, not page by page.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Which pages to fix first

Status first, traffic second. Google's Search Console Help gives the order:

"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)

"Most important" is for you to define. For a service business it means two things: pages that get search clicks, and pages people book or call from. A Poor page nobody visits can wait. A Need improvement page that brings half your leads may not.

Core Web Vitals are three measures of how a page feels to real visitors: LCP (how fast the main content shows), INP (how fast the page reacts to a tap) and CLS (how much the layout jumps). INP replaced the older FID metric on March 12, 2024, according to Google's web.dev. A checklist that still lists FID is out of date. What each number means and how much it moves rankings is in Core Web Vitals and Google ranking.

Where the data comes from

Two free Search Console reports give you everything you need. No paid tool required.

You needReportWhat to note
Speed status per page groupCore Web Vitals report, mobile firstPoor, Need improvement or Good, and which metric fails
Search traffic per pagePerformance report, Pages tabClicks over the last 3 months
Business valueYour own recordsWhich pages lead to calls, forms or bookings

The Core Web Vitals report uses field data: real Chrome visits over the last 28 days, judged at the 75th percentile, meaning three in four visits must hit the target (Search Console Help; PageSpeed Insights). Clicks in the Performance report are the times someone clicked your site from Google results (Search Console Help: Performance report).

If you track bookings in Google Analytics, use those too: GA4 key events for calls, forms and bookings.

How to rank your pages: a simple score

Put each failing page in a sheet with its status and its clicks, then sort.

PriorityStatusTraffic or bookingsAction
1PoorHighFix now
2PoorLowFix next, often for free with priority 1 if they share a template
3Need improvementHighFix after all Poor pages
4Need improvementLowLeave unless the fix is cheap
—GoodAnyDon't touch for speed

Also note which metric fails. A Poor LCP on your home page (slow main photo) and a Poor CLS on your booking page (buttons jumping) are different jobs for whoever does the work.

Fix the template, not the page

Search Console doesn't judge pages one by one. It groups pages that look alike, and the whole group gets the status of its worst metric (Search Console Help). Google explains why:

"It is assumed that these groups have a common framework and the reasons for any poor behavior of the group will likely be caused by the same underlying reasons." (Search Console Help: Core Web Vitals report)

For you this means one fix often clears dozens of pages. If all 30 city pages fail LCP because they share one heavy header photo, fixing that header once fixes all 30. Count templates, not URLs, when you budget the work.

Inside a group, Search Console lists pages by impressions, highest first, so "the URLs at the top have the most affect on the group status" (Search Console Help). Test those first.

Too little data: what a small site does

Many small sites see "No data available" or only one site-wide group. Search Console Help says a page group with too little data rolls up into an origin group, meaning all pages on your domain together. PageSpeed Insights does the same for a single page (PageSpeed Insights).

Then rank by business value alone:

  1. List your 3–5 pages that bring calls or bookings, plus the home page.
  2. Run each through PageSpeed Insights on mobile. Its lab test works with no real-user data.
  3. Fix the slowest of those first.

Google's Search Console Help also gives a rough size target for non-technical owners: keep a page and everything it loads under 500KB, and under 50 resources on mobile.

After the fix: check in 28 days

Numbers move slowly because every figure is a 28-day average. When you think an issue is fixed, open it in the Core Web Vitals report and click Start Tracking:

"Click Start Tracking to start a 28-day monitoring session to check for instances of this issue in your site." (Search Console Help: Core Web Vitals report)

Tracking only watches the data. It "does not trigger re-indexing or any other active behavior from Google" (same page).

Example

Illustrative cases, not measured results.

A roofer with 40 Poor city pages

His city pages get 50 clicks a month in total; his roof-repair page gets 400 and is Need improvement. He fixes the shared city-page header first, because Google says Poor comes first and one template fix clears all 40. The repair page comes next.

A dental office with one Poor booking page

The booking page gets only 80 clicks a month, but most new patients book there. Its CLS is Poor because the date picker loads late and shifts the page. It goes first, ahead of blog posts with more clicks.

A bookkeeper with no field data

Search Console shows "No data available." She tests her home, services and contact pages in PageSpeed Insights, finds a 3 MB photo on the home page, and fixes that one.

FAQ

Should I fix every page to Good?

No. Fix Poor pages, then the pages that matter to your business. Google calls Need improvement pages "less important to fix than Poor URLs" (Search Console Help).

Why doesn't my page appear in the Core Web Vitals report?

The report shows only indexed pages with enough Chrome visits. It is a sample, not a full list of your pages (Search Console Help).

Mobile or desktop first?

Mobile, for most service businesses: Search Console shows the two separately, and a page can be Good on desktop and Poor on mobile (Search Console Help).

Does a PageSpeed score of 50 mean I must fix the page?

Not by itself. The 0–100 score is a lab test; Search Console's status comes from real visits. Rank by the real-visit status.

Different for you?

Keep learning

NextCore Web Vitals Checklist: Quick Wins for a Faster SiteA one-week Core Web Vitals checklist for a small business site: find the failing metric, then the image, layout and script fixes an owner can make.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Search Console Help: Core Web Vitals report
  2. Search Console Help: Performance report (Search results)
  3. PageSpeed Insights: About PageSpeed Insights
  4. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12