- Published
- Updated
- 11 min read

TL;DR: No. Google's documentation does not say the March 2026 core update grades a whole site by its slowest page. Core Web Vitals are measured from real visits, page by page, with some site-wide assessments Google does not detail. Search Console groups similar URLs, so one slow template still shows up across many pages. Fix templates first.
Correction, October 2026: an earlier version of this note said Google's March 2026 core update switched Core Web Vitals from page-level to site-wide scoring and graded every site by its slowest pages. That is not in Google's documentation, and we have rewritten the note around what Google actually publishes.
If you heard that Google now judges your entire website by its worst page, you heard it from a lot of places this spring. We repeated it on this blog too. So here is what Core Web Vitals actually measure, what the March 2026 core update did and did not announce, and where a small business should spend its next few hours of website work.
The short version: speed still matters, slow templates still hurt, and the fix list barely changes. The reason behind it does.
What did the March 2026 core update actually change?
The dates are real. Google's Search Status Dashboard logged the March 2026 core update starting on March 27, 2026, with the note "Released the March 2026 core update," and later posted "The rollout was complete as of April 8, 2026." (Google Search Status Dashboard (opens in a new tab))
That entry says nothing about Core Web Vitals, page speed or a new way of scoring them. Google's own explanation of core updates describes them the opposite way from a targeted speed penalty: "These changes are broad in nature, and don't target specific sites or individual web pages." (Google Search Central, core updates (opens in a new tab))
The thresholds did not move either. Google's Core Web Vitals page still asks for Largest Contentful Paint "within the first 2.5 seconds of the page starting to load," an Interaction to Next Paint "of less than 200 milliseconds," and a Cumulative Layout Shift "of less than 0.1." (Google Search Central (opens in a new tab))
So where did the site-wide story come from? Several SEO blogs published it during the rollout, often with a percentage of failing URLs that would sink a whole domain. None of them linked to a Google page that says it, and I could not find one on developers.google.com or web.dev. Traffic did move during the update for plenty of sites. A core update moves rankings by design. That is not evidence of a new speed rule.
Does Google grade your whole site by its slowest page?
Not according to anything Google has published. The answer is in Google's page experience documentation, and it is more careful than either the scare version or the "speed does not matter" version.
What Google says about page-level and site-wide signals
Google asks the question directly: "Is page experience evaluated on a site-wide or page-specific basis?" Its answer: "Our core ranking systems generally evaluate content on a page-specific basis, including when understanding aspects related to page experience. However, we do have some site-wide assessments." (Google Search Central, page experience (opens in a new tab))
Read that slowly. Page by page is the general rule. Some site-wide assessment exists, and Google does not say what it is. Nowhere does Google say a site is graded by its slowest page, by a share of failing URLs, or by an average of every page on the domain. Anyone who gives you a precise cutoff for the "site-wide score" is filling a gap Google left open.
Where the site-wide idea comes from
There is a real reason people see whole-site numbers. Google's tools fall back to them when a single page has too little traffic.
PageSpeed Insights explains that a page "might not have sufficient data if it has been recently published or has too few samples from real users. When this happens, PSI will fall back to origin-level granularity, which encompasses all user experiences on all pages of the website." (Google, About PageSpeed Insights (opens in a new tab))
Search Console does something similar. If a group of URLs lacks data, "Search Console creates a higher-level origin group that should contain enough URLs and data to show in the report." (Search Console Help (opens in a new tab))
For a small business site with modest traffic, that fallback is common. You run a test on your services page and see numbers that really describe the whole domain. That is a reporting fallback when data is thin. It is not a ranking rule that your slowest page drags the rest down.
How are Core Web Vitals measured?
Core Web Vitals are three metrics taken from real Chrome users, not from a test you run once. Google describes them as "a set of metrics that measure real-world user experience for loading performance, interactivity, and visual stability of the page." (Google Search Central (opens in a new tab)) Our performance optimization guide covers the build side in more depth.
The three metrics and their thresholds
- Largest Contentful Paint (LCP): when the biggest thing on screen finishes painting. Good is 2.5 seconds or less; poor is over 4 seconds.
- Interaction to Next Paint (INP): how fast the page responds after a tap or click. Good is 200 milliseconds or less; poor is over 500 milliseconds.
- Cumulative Layout Shift (CLS): how much the layout jumps while loading. Good is 0.1 or less; poor is over 0.25.
Those bands are the ones PageSpeed Insights publishes: LCP "[0, 2500ms] (2500ms, 4000ms] over 4000ms," INP "[0, 200ms] (200ms, 500ms] over 500ms," and CLS "[0, 0.1] (0.1, 0.25] over 0.25." (Google, About PageSpeed Insights (opens in a new tab))
Field data beats a lab score
The pass mark is set at the 75th percentile. web.dev recommends measuring "the 75th percentile of page loads, segmented across mobile and desktop devices," and treating a page as passing "if it meets the recommended targets at the 75th percentile for all three of the Core Web Vitals metrics." (web.dev, Web Vitals (opens in a new tab)) Search Console reports each group over "the last 28 days." (Search Console Help (opens in a new tab))
That is why a 98 in a Lighthouse test on your office Wi-Fi can sit next to a failing field result. Lab tools run "in a controlled environment with a predefined set of network and device conditions," while field data comes from "monitoring all users who visit a page." (web.dev, lab and field data (opens in a new tab)) Your customer on a three-year-old phone in a parking lot is the field data.
And the phone is the version that counts. "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central, mobile-first indexing (opens in a new tab)) We wrote more on that in Google already grades your site on a phone.
How much do Core Web Vitals matter for ranking?
They count, and they are not the whole game. Google says plainly: "Core Web Vitals are used by our ranking systems." It also says good results in Search Console's Core Web Vitals report or third-party tools don't promise top rankings, and that "Google Search always seeks to show the most relevant content, even if the page experience is sub-par. But for many queries, there is lots of helpful content available. Having a great page experience can contribute to success in Search, in such cases." (Google Search Central, page experience (opens in a new tab))
Here is how I explain that to an owner. If your page is the best answer, slow loading will not erase it. If ten local businesses have equally good answers, a fast, stable page is one of the things that can separate you. And whatever it does for rankings, a page that jumps around while someone tries to tap "Call" costs you the call.
The old version of this note had that part right: content quality and relevance still lead. A clear SEO strategy built on pages that answer real questions does more than shaving 100 milliseconds off a page nobody needs.
How many websites pass Core Web Vitals?
About half on phones. The 2025 Web Almanac, built on Chrome UX Report data from July 2025, found good Core Web Vitals on "48% for mobile websites and 56% for desktop websites." (HTTP Archive Web Almanac 2025 (opens in a new tab)) The old note said 47%; the published figure is 48%.
The middle of the web does worst. Among the top 1,000 sites, 51% pass on mobile, "declining further for the next tiers to 42% for the top 10,000 and 37% for the top 100,000 sites." (HTTP Archive Web Almanac 2025 (opens in a new tab)) Many small business sites sit somewhere in that long tail, often with more tracking and plugins than their traffic justifies.
Why does one slow template still hurt?
This is the useful part of the old advice, and it survives the correction. You do not fix speed one URL at a time. You fix the thing the URLs share.
Search Console groups pages by template
Search Console's Core Web Vitals report groups "pages that have a similar user experience," and "The LCP, INP, and CLS status applies to the entire group." Google adds: "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 (opens in a new tab))
The status of a group is also its weakest metric: "the URL group's status is its most poorly performing metric." So if your blog template has a layout shift problem, every post on it shows as poor, even if each post loads fast. Fix the template once and the whole group can move. On a site with 300 posts on one template, that is one fix for 300 pages.
Third-party scripts pile up
Most sites carry code they did not write. The 2025 Web Almanac found "Around 90%-92% pages use third-parties across different rank groups." (HTTP Archive Web Almanac 2025, third parties (opens in a new tab)) Chat widgets, tag managers, ad pixels, review badges and booking embeds each add work for the phone to do, and that work shows up in INP.
Pull a list of every script your site loads. Ask who added it, what it does and whether anyone still looks at its data. In my experience the answer for at least one is "nobody remembers."
Images and the hero
The hero image is usually the LCP element on a small business page. web.dev is blunt: "Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay, and will have a negative impact on LCP." (web.dev, optimize LCP (opens in a new tab)) Serve it at the size the phone actually displays, in a modern format, and let the browser find it in the first HTML it receives.
Old pages: improve before you delete
The old note told owners to prune old posts for the sake of site-wide speed. Google's advice on content is more careful. "Deleting content is a last resort, and only to be considered if you think the content can't be salvaged." It also says that "if you're considering deleting entire sections of your site, that's likely a sign those sections were created for search engines first, and not people." (Google Search Central, core updates (opens in a new tab))
So keep the useful old pages and improve them. Retire the ones that only exist to catch a keyword. Do it for your readers, not because of a speed rule Google never published.
How long does recovery take?
Google says some changes "can take effect in a few days, but it could take several months" for its systems to confirm a site is producing helpful content, which "could mean waiting until the next core update." (Google Search Central, core updates (opens in a new tab)) Speed fixes show up in field data on the 28-day window, so give a fix a full month before you judge it.
What should a small business check this week?
- Open Search Console. Go to the Core Web Vitals report, mobile first. Note which URL groups are poor and which metric is the worst in each.
- Map groups to templates. Blog post, service page, location page, product page. Usually two or three templates explain almost every poor URL.
- Test one URL per template in PageSpeed Insights. Check whether the field data shown is for the URL or for the whole origin, so you know what you are reading.
- Fix the hero image. Right size, not lazy-loaded, discoverable in the HTML. This is often the cheapest LCP win.
- Cut one third-party script. The one nobody can explain. Then the next one.
- Reserve space for anything that loads late. Banners, embeds and ads need fixed dimensions so the page stops jumping.
- Wait 28 days and look again. Field data needs time. Write down today's numbers so you can tell whether it moved.
My rule of thumb: if you can only do one thing, do the template that the most URLs share. If you want a quick outside read first, I wrote about what a free website check finds for a small business (opens in a new tab), and my wife Amelia, Kief Studio's co-founder and CEO, covered the practical Core Web Vitals fixes that actually move the needle (opens in a new tab).
Frequently asked questions
Did the March 2026 core update make Core Web Vitals site-wide?
Not according to Google. The update ran from March 27 to April 8, 2026, and Google's notes about it do not mention Core Web Vitals. Google says core updates are broad and do not target specific sites or pages.
Does Google rank a whole site by its slowest page?
No published Google rule says so. Google says its systems generally evaluate page experience page by page, with some site-wide assessments it does not detail. There is no documented slowest-page or percentage cutoff.
What are good Core Web Vitals scores?
LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real visits, on mobile and desktop separately.
Why does PageSpeed Insights show data for my whole site?
When a page has too little real-user data, PageSpeed Insights falls back to origin-level data, which covers every page on the site. That is a reporting fallback, not a ranking penalty.
Are Core Web Vitals a ranking factor?
Yes. Google says its ranking systems use Core Web Vitals. It also says the most relevant content can still rank with a weaker page experience, so they help most where many pages answer equally well.
How long until Core Web Vitals fixes show up?
Search Console reports on the last 28 days of visits, so allow about a month after a fix. Ranking changes from wider site improvements can take longer, sometimes until the next core update.
Where we fit
Kief Studio is in Shrewsbury, and this is the kind of work our managed website operations covers: we host the site on dedicated machines, watch uptime, speed and security, and fix problems before visitors see them. When a site has outgrown its template, our custom web application work builds around how the business actually runs and keeps it fast after launch.
On the search side, our SEO, AEO and GEO work writes true pages, structures them and keeps the site fast and crawlable. If a number cannot be sourced, we leave it out, which is why this note now says what Google documents and nothing more.
First conversation is free. No commitment.




