Article 14 min read
Core Web Vitals: Google's Three Metrics, One by One, and How Much They Weigh
by Daniel Sócrates published
On September 14, 2026, we searched for “core web vitals” on Google. The search ran on Google in Brazil, where we are based. At the top, an AI Overview summed up the subject in two lines. These are Google metrics for page experience, and they influence ranking. 1
Scroll down the first page. A hosting company’s guide, in Portuguese, calls the metrics a ranking factor. It promises better odds to sites with good numbers. A network company’s page, also in Portuguese, still lists FID among the three. FID left the list in March 2024. 2
The Google page that answers how much this weighs says two things in the same answer. The metrics are used by the ranking systems. And Search shows the most relevant content even when the page experience is sub-par. 17
This piece works with the documentation open, checked on September 14, 2026.
One boundary before we go on. Speed as the visitor feels it already has its own piece, on site speed. That one covers the test against the real visit and what makes a site slow. This one covers the three metrics from the inside, the thresholds, where the data comes from, and the weight in Search. The rest of the technical ground, from crawling to markup, is in technical SEO.
What Core Web Vitals are
Think of three moments in a visit. The page appears. You tap a button, and it responds. You read, and the text stays in place.
Google measures each moment with a number, taken from real visits. This is called Core Web Vitals.
The documentation’s definition fits in one sentence. It is a set of metrics for the real-world experience of loading, interactivity, and visual stability of the page. 3 The Chrome team introduced the metrics in 2020. 10 The set can change over time, and each stable metric changes no more than once a year. 4
Today there are three: LCP, INP, and CLS. 4 What the page declares to Google, from the title to the markup, is in the piece on on-page SEO. The three metrics measure something else: the delivery.
LCP: when the main thing appears
Picture a shop with a steel roll-up gate. The customer does not wait for the whole shop to be ready. They wait for the gate to go up and the window display to show.
On the page, the window display is the largest element that fits on the screen: an image, a block of text, or a video. 5 The time until it appears, counted from the moment the person asked for the page, is called Largest Contentful Paint. The abbreviation is LCP. 5
The clock starts early. It includes the redirect, the connection, and the wait for the server’s first byte. 5 That is why the number measured with real visitors can differ from the number in a test.
The thresholds are these. Up to 2.5 seconds is good. Up to 4 seconds needs improvement. Over 4 seconds is poor. 5 6
INP: when the page responds
You press the elevator button, and the light does not come on. You press again, unsure whether the first press counted.
Interaction to Next Paint, or INP, measures that gap on the page. It watches clicks, taps, and key presses throughout the whole visit. 7 For each interaction, it counts the time until the browser paints the next frame on screen, the first visible response. 7
The final value is the slowest interaction of the visit. On pages with many interactions, the calculation ignores one in every 50, so a single stumble does not decide everything. 7 Scrolling and hovering do not count. 7
The thresholds: up to 200 milliseconds is good. Up to 500 needs improvement. Over 500 is poor. 7 6
How INP replaced FID
Before INP, the spot belonged to First Input Delay, or FID. It measured only the delay of the first interaction in a visit. 8 The rest of the visit went unmeasured.
INP started as an experimental metric in May 2022 and became a pending metric in 2023. 9 On March 12, 2024, it became an official Core Web Vital and took FID’s place. 9 4 Google had announced that, with the switch, the Search Console report would stop showing FID. 10 Chrome ended support for FID in its tools on September 9, 2024. 8
Any text that still lists FID among the three was written before that date, or was never reviewed after it.
One detail of INP trips up a lot of people. It can come back empty. That happens when nobody clicked, when the person only scrolled, or when the visitor was a bot. 7 Tools that only watch the page load do not measure INP either. In those tools, Total Blocking Time serves as a stand-in, without replacing the metric. 7
CLS: when the page holds still
Picture a news story open on your phone. You are on the third paragraph. An ad loads above it, the text drops, and your finger taps the wrong link.
That jump has a name. This is called a layout shift, and the metric that measures these jumps is Cumulative Layout Shift, or CLS. 11
The sum follows a rule. web.dev groups shifts that happen less than 1 second apart, in a window of up to 5 seconds. A page’s CLS is the largest of these bursts. 11 A shift that happens within half a second of a tap, click, or key press stays out of the count. The visitor caused it, so the visitor expects it. 11
The most common causes sit on the page itself: an image or video with no declared size, a font that changes size as it loads, an ad or widget that resizes itself. 11
CLS has no unit. It is a score. Up to 0.1 is good. Up to 0.25 needs improvement. Over 0.25 is poor. 11 6
A caveat on sources. The help page for the Search Console report still describes CLS as the sum of every shift over the whole life of the page. web.dev records that formula as the old one. 6 11 For the definition, go with web.dev.
The 75th percentile, the yardstick for all three
The owner of a pizza place promises delivery in 40 minutes. He does not go by the fastest delivery of the night. Nor by the latest one, the driver who got a flat tire. He looks at the time within which three out of four orders arrived.
Google does the same math with visits. This is called the 75th percentile. 12
The web.dev rule is direct. If at least 75% of visits land in good, the page is good on that metric. If at least 25% fall in poor, the page is poor. 12 An LCP of 2 seconds at the 75th percentile is good. One of 5 seconds is poor. 12
The reason for 75 is written down too. It ensures that most visits, three out of four, reached the target level or better. 12 And it holds up against outliers. On a site with 100 visits, it would take 25 disastrous visits to move the number. 12
The math is done separately for mobile and desktop. The page passes when all three metrics are good at the 75th percentile. 4
| Metric | What it measures | Good | Need improvement | Poor |
|---|---|---|---|---|
| LCP | loading of the main element | up to 2.5 s | up to 4 s | over 4 s |
| INP | response to a click, tap, or key | up to 200 ms | up to 500 ms | over 500 ms |
| CLS | visual stability | up to 0.1 | up to 0.25 | over 0.25 |
Where the data comes from
Imagine a satisfaction survey nobody has to fill out. The browser notes how the visit went, with no name attached, and sends it to a shared pool.
Chrome does this for people who opted in. This is called the Chrome UX Report, or CrUX. 13 It is the official dataset of the metrics program. Chrome’s documentation says Google Search uses this data to inform the page experience ranking factor. 13
Not every visit counts. The user needs usage statistics reporting and browser history sync turned on. 14 Chrome on desktop and Chrome on Android count. Chrome on the iPhone stays out, and so do browsers like Edge. 14 The window is always the last 28 days. 15
Not every page counts either. It must be public, respond normally, and not be marked noindex. 14 It also needs enough visits. The minimum is not disclosed, and there is no way to sign your site up. 14
This is where the small-site question comes in. If the page does not have enough visits, PageSpeed Insights shows the data for the whole site, the origin. If not even the origin has enough, no visitor data appears at all. 15 In Search Console, the screen says no data is available. 6
In that case, what is left is the lab test. It helps you find the problem. It does not count as field data. The details of that difference are in the piece on site speed.
Today’s measurement, on one of our pages
On September 14, 2026, at 6:20 a.m. Brasília time, I ran PageSpeed Insights on our own homepage. The page is seogenome.com, our company site in Brazil. 16
The “This URL” button came up disabled. The homepage alone had no visitor data. The report showed the origin, the whole site. 16 15
On mobile, the Core Web Vitals assessment passed. LCP of 2.4 seconds, CLS of 0.02, and INP with no value, marked N/A. 16 On desktop, it also passed: LCP of 2 seconds, CLS of 0.01, and no INP value. 16
A pass like this calls for three readings.
INP had no data. Under the PageSpeed Insights rule, an origin passes with good LCP and CLS when INP is missing. 15 Today’s pass says nothing about the response to a tap.
On mobile, LCP sits 0.1 second from the threshold. The Search Console help explains this case. A page right at the edge changes bands with a small site-wide change, like a traffic spike. 6
And there is the window. The 28 days start in mid-August, and the new SEO Genome site has been live since September 2. 16 Today’s number mixes the old site with the new one.
In the same report, the performance score at the top of the diagnosis was 98. That score comes from the lab, with a simulated phone. 16 15 The field data sits in the section above it, the one about what real users experience.
The Core Web Vitals report in Search Console
PageSpeed Insights looks at one page or one origin. Search Console looks at the site. The Core Web Vitals report uses the same CrUX field data. 6
It shows only indexed URLs, and only a sample. Mobile and desktop are kept apart. 6
The most confusing part is the grouping. The report puts similar URLs into a group, and the whole group gets the same status. The help page explains the assumption: pages built on the same template tend to share the same problem for the same reason. 6 The group’s status is that of its worst metric. Poor CLS with good INP makes a poor group. 6
Three rules from the help page save hours of guesswork:
- A group without enough data for both LCP and CLS stays out of the report. When data is missing, Search Console builds a larger group, with the whole origin. 6
- The data goes to the actual URL. In most other reports, it goes to the canonical. 6
- The group’s value is the 75th percentile. It covers visits from the last 28 days. 6
The order of work is in the help page too. Everything in Poor comes first. Then the issues that hit the most URLs, or your most important URLs. 6 That yardstick of severity times reach goes into the SEO audit, along with the other reports.
After the fix, you click Start Tracking in the report itself. Search Console opens a 28-day monitoring session. 6 If a single URL still has the issue, the validation fails. And the validation does not request any reindexing. It only restarts the clock. 6
The report and PageSpeed Insights can disagree. One speaks for the group, the other for the URL. PageSpeed Insights also strips the parameters from the address before it measures. 6
How much it weighs in Search, in Google’s own words
Google’s page on page experience answers the question in FAQ style. I take what it says, sentence by sentence. 17
Core Web Vitals are used by the ranking systems. Google recommends reaching good numbers, for success in Search and for the user experience. 17 3
There is no single page experience signal. The systems look at many signals. 17
A good result in the Search Console report or in a third-party tool does not guarantee the top spot. 17 And chasing a perfect score just for SEO may not be the best use of your time. 17
Search always seeks to show the most relevant content, even with a sub-par experience. For many searches, there is plenty of helpful content available. In those cases, a great experience can contribute to success. 17
Beyond Core Web Vitals, the other aspects of page experience do not directly help you rank higher. 17 The assessment is usually page by page, with some site-wide assessments. 17
A note for anyone who reads Google in translation. The Portuguese version of this page drops one word from the self-assessment question. The English asks whether your pages have good Core Web Vitals. The Portuguese asks only whether they have Core Web Vitals. 17 Go with the original.
In my reading, Google’s text puts the metrics in the equation and says when they decide. Among pages that answer well, experience breaks the tie. Against a page that answers better, it does not jump the line. No Google page I read for this piece says the weight will grow.
What the person does after the page loads is a different reading. It shows up, with the data laid over the page itself, in the piece on Page Analytics.
The one-morning check
Pick the page that sells the most and open two screens: Search Console and PageSpeed Insights.
- Open the Core Web Vitals report, mobile version. Write down the groups in Poor and the metric that sank each one. 6
- If the report says there is no data, run the homepage through PageSpeed Insights and see whether the origin has field data. 15
- In PageSpeed Insights, read the top section first. Note whether the data is for This URL or for the Origin. 15
- Look at INP. If it says N/A, the pass came from LCP and CLS alone. 15
- Measure the distance to the threshold. An LCP of 2.4 seconds passes today, right at the edge. 6 12
- Send the developer an example URL from each poor group, with the metric and its 75th percentile value. 6
- After the fix, start the validation and put a date 28 days out on your calendar. 6
From now on, when someone shows you a speed score, you will ask three questions. Is it visitor data or test data? Is it for the page or the whole site? And how close to the threshold is the 75th percentile?
Open PageSpeed Insights today, paste in the address of the page that sells the most, and see whether the “This URL” button lights up.
Frequently asked questions
Are Core Web Vitals a ranking factor?
Google writes that the metrics are used by its ranking systems. 17 On the same page, it says a good result does not guarantee the top spot. And the most relevant content shows up even with a sub-par experience. 17
What PageSpeed Insights score do I need to pass?
The 0 to 100 score comes from the lab. 15 The Core Web Vitals assessment sits in the top section, with visitor data. It passes when LCP, INP, and CLS are good at the 75th percentile. Without INP data, it passes with good LCP and CLS. 15
Why does Search Console say there is no data?
The property may be new, or the Chrome UX Report lacks data. 6 The page has to be public and get enough visits, and the minimum is not disclosed. 14
Does FID still count?
No. INP took FID’s place on March 12, 2024. 9 Chrome ended support for FID in its tools on September 9, 2024. 8
How long until the report shows the fix?
The data covers the last 28 days. 6 The validation you start in the report also follows the site for 28 days. 6
Notes and sources
- Live reading of the Google Brazil results page for “core web vitals,” September 14, 2026, at https://www.google.com.br/search?q=core+web+vitals&hl=pt-BR&gl=br&pws=0, in the author’s own browser tab. The search ran on Google in Brazil, where we are based, with the interface in Portuguese. The AI Overview, labeled “Visão geral criada por IA” in Portuguese, said that Core Web Vitals “são métricas criadas pelo Google para medir a experiência real de carregamento, interatividade e estabilidade visual de uma página web. Elas ajudam a garantir que um site seja agradável de usar e influenciam o ranqueamento na busca do Google” (are metrics created by Google to measure the real-world loading, interactivity, and visual stability experience of a web page; they help make a site pleasant to use and influence ranking in Google Search). Organic results on the first page, in order: Google Search Central, web.dev, Cloudflare, web.dev, SpeedVitals, Semrush, Locaweb, and Akamai. Accessed September 14, 2026.
- SEO Genome survey, September 14, 2026, of texts from the first page in note 1 and from the Semrush snapshot (Brazil database), downloaded and read the same day. HostGator, “Core Web Vitals (CWV): o que é e como melhorar?” (Core Web Vitals: what it is and how to improve it), published April 9, 2026, and modified May 12, 2026, https://www.hostgator.com.br/blog/core-web-vitals/: “o Core Web Vitals é um fator de ranqueamento do Google” (Core Web Vitals is a Google ranking factor), with “mais chances” (better chances) for sites with good numbers. Cloudflare, “O que são os Core Web Vitals (CWV)?” (What are Core Web Vitals?), https://www.cloudflare.com/pt-br/learning/performance/what-are-core-web-vitals/: lists “Largest Contentful Paint (LCP), First Input Delay (FID) e Cumulative Layout Shift (CLS)” and does not mention INP. Conversion, “Core Web Vitals: o que é, como melhorar e SEO com UX” (Core Web Vitals: what it is, how to improve it, and SEO with UX), July 12, 2025, https://www.conversion.com.br/blog/core-web-vitals/: calls the metrics “fatores de classificação diretos” (direct ranking factors) and writes that the “peso destas métricas aumentará progressivamente” (weight of these metrics will increase progressively), with no source. Semrush, https://www.semrush.com/blog/core-web-vitals/, modified March 19, 2024: “Google also considers the Core Web Vitals in its ranking factors”. Locaweb, https://www.locaweb.com.br/blog/temas/marketing-e-seo/core-web-vitals/, April 8, 2024. Accessed September 14, 2026.
- Google Search Central, “Understanding Core Web Vitals and Google search results,” https://developers.google.com/search/docs/appearance/core-web-vitals, page last updated December 10, 2025; Portuguese version updated December 18, 2025. Accessed September 14, 2026. Passages: “Core Web Vitals is a set of metrics that measure real-world user experience for loading performance, interactivity, and visual stability of the page”; “We highly recommend site owners achieve good Core Web Vitals for success with Search and to ensure a great user experience generally”; “This, along with other page experience aspects, aligns with what our core ranking systems seek to reward”.
- Philip Walton, “Web Vitals,” web.dev, https://web.dev/articles/vitals, published May 4, 2020, and last updated October 31, 2024. Accessed September 14, 2026. Passages: “The metrics that make up Core Web Vitals will evolve over time”; “Stable Core Web Vitals metrics won’t change more than once per year”; “a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices”; “Tools that assess Core Web Vitals compliance should consider a page passing if it meets the recommended targets at the 75th percentile for all three of the Core Web Vitals metrics”; and “INP became a stable Core Web Vital metric in 2024”, with LCP, CLS, and INP as the three stable metrics.
- Philip Walton and Barry Pollard, “Largest Contentful Paint (LCP),” web.dev, https://web.dev/articles/lcp, last updated September 4, 2025. Accessed September 14, 2026. Passages: “LCP reports the render time of the largest image, text block, or video visible in the viewport, relative to when the user first navigated to the page”; “LCP includes any unload time from the previous page, connection set up time, redirect time, and other Time To First Byte (TTFB) delays”; “sites should strive to have Largest Contentful Paint of 2.5 seconds or less”; and, in the alt text of the thresholds image, “poor values are greater than 4.0 seconds, and anything in between needs improvement”.
- Search Console Help, “Core Web Vitals report,” https://support.google.com/webmasters/answer/9205520, English version (the Portuguese version carries a notice of AI translation). Accessed September 14, 2026. Passages: the report is based on “real world usage data (sometimes called field data)”; “Only indexed URLs can appear in this report”; “It shows a sample of pages”; “Data is assigned to the actual URL, not the canonical URL”; “the URL group’s status is its most poorly performing metric”; “If a URL group does not have a minimum amount of reporting data for both LCP and CLS, the URL is omitted from the report”; “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”; the origin group for groups without data; “75% of page requests” “in the last 28 days”; the thresholds table (LCP <=2.5s, <=4s, >4s; INP <=200ms, <=500ms, >500ms; CLS <=0.1, <=0.25, >0.25); “If you see a ‘No data available’ screen, it means either that your property is new in Search Console, or that there is not enough data available in the CrUX report”; “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”; the validation, “Click Start Tracking to start a 28-day monitoring session”, “The presence of that issue in any URL is enough to mark the issue as not fixed”, and “Start tracking does not trigger re-indexing or any other active behavior from Google”; the case of “a borderline status for many pages”; “PageSpeed Insights strips all parameter data from the URL”; and the CLS definition, “CLS measures the sum total of all individual layout shift scores for every unexpected layout shift that occurs during the entire lifespan of the page”. The body uses the English labels: Good, Need improvement, and Poor.
- Jeremy Wagner and Barry Pollard, “Interaction to Next Paint (INP),” web.dev, https://web.dev/articles/inp, last updated September 2, 2025. Accessed September 14, 2026. Passages: INP observes “the latency of all click, tap, and keyboard interactions that occur throughout the lifespan of a user’s visit to a page”; “The final INP value is the longest interaction observed, ignoring outliers”; “we ignore one highest interaction for every 50 interactions”; the latency runs until “the moment the browser is next able to paint a frame”; “hovering, zooming, or scrolling” are not observed; the thresholds “below or at 200 milliseconds” (good), “above 200 milliseconds and below or at 500 milliseconds” (needs improvement), and “above 500 milliseconds” (poor); INP empty when “the user never clicked, tapped, or pressed a key”, when there was only scrolling, or when “The page is being accessed by a bot”; and “some lab tools won’t report a page’s INP because they only observe the loading of a page without any interactions. In such cases, Total Blocking Time (TBT) may be a reasonable proxy metric for INP, but it’s not a substitute for INP in and of itself”.
- web.dev, “First Input Delay (FID),” https://web.dev/articles/fid, page last updated October 6, 2024. Accessed September 14, 2026. Passages: “FID measures the time from when a user first interacts with a page”; “FID only measures the ‘delay’ in event processing”; and the notice “First Input Delay (FID) is no longer a Core Web Vital, and has been replaced by the Interaction to Next Paint (INP) metric. As a consequence, support for FID ended on September 9, 2024.”
- Jeremy Wagner and Rick Viscomi, “Interaction to Next Paint becomes a Core Web Vital on March 12,” web.dev, January 31, 2024, https://web.dev/blog/inp-cwv-march-12. Accessed September 14, 2026. Passages: Chrome “introduced Interaction to Next Paint (INP) as an experimental metric in May 2022. Last year, INP became a pending metric”; and “INP will officially become a Core Web Vital and replace FID on March 12 of this year”.
- Google Search Central Blog, “Introducing INP to Core Web Vitals,” May 10, 2023, https://developers.google.com/search/blog/2023/05/introducing-inp; and Google Search Central, “Latest Google Search documentation updates,” https://developers.google.com/search/updates, entry of March 12, 2024. Accessed September 14, 2026. Passages: “In early 2020, Google’s Chrome Team introduced the Core Web Vitals”; “When INP replaces FID in March 2024, the Search Console report will stop showing FID metrics and use INP as the new metric for responsiveness”; and, in the March 12, 2024, entry, “Additionally updated to reflect that INP is now a Core Web Vital”.
- Milica Mihajlija and Philip Walton, “Cumulative Layout Shift (CLS),” web.dev, https://web.dev/articles/cls, page last updated April 12, 2023. Accessed September 14, 2026. Passages: “CLS is a measure of the largest burst of layout shift scores for every unexpected layout shift that occurs during the entire lifecycle of a page”; “one or more individual layout shifts occur in rapid succession with less than 1-second in between each shift and a maximum of 5 seconds for the total window duration”; “Previously CLS measured the sum total of all individual layout shift scores that occurred during the entire lifespan of the page”; “Layout shifts that occur within 500 milliseconds of user input will have the hadRecentInput flag set, so they can be excluded from calculations”; the causes “images or videos with unknown dimensions, fonts that render larger or smaller than its initial fallback, or third-party ads or widgets that dynamically resize themselves”; and “Good CLS values are 0.1 or less. Poor values are greater than 0.25.”
- web.dev, “Defining the Core Web Vitals metrics thresholds,” https://web.dev/articles/defining-core-web-vitals-thresholds, published May 21, 2020, and last updated May 7, 2025. Accessed September 14, 2026. Passages: “if at least 75 percent of page views to a site meet the ‘good’ threshold, the site is classified as having ‘good’ performance for that metric. Conversely, if at least 25 percent of page views meet the ‘poor’ threshold, the site is classified as having ‘poor’ performance”; “a 75th percentile LCP of 2 seconds is classified as ‘good’, while a 75th percentile LCP of 5 seconds is classified as ‘poor’”; “most visits to the site (3 of 4) experienced the target level of performance or better”; and “for a site with 100 visits, 25 of those visits would need to report large outlier samples for the value at the 75th percentile to be affected by outliers”.
- Chrome for Developers, “Overview of CrUX,” https://developer.chrome.com/docs/crux, page last updated February 8, 2024. Accessed September 14, 2026. Passages: “CrUX is the Google dataset of the Web Vitals program”; and the data is “used by Google Search to inform the page experience ranking factor”.
- Chrome for Developers, “CrUX methodology,” https://developer.chrome.com/docs/crux/methodology, page last updated June 20, 2024. Accessed September 14, 2026. Passages: “A page must be publicly discoverable”, with a 200 status and no
noindex; “An exact number is not disclosed” on the minimum number of visitors; “At this time, you cannot manually submit pages or origins for inclusion”; the user must “Enable usage statistic reporting” and “Sync their browser history”; the accepted platforms, Chrome on desktop and Android; and the exceptions “Chrome on iOS”, “Android apps using WebView”, and “Other Chromium browsers (for example Microsoft Edge)”. - Google for Developers, “About PageSpeed Insights,” https://developers.google.com/speed/docs/insights/v5/about, page last updated October 21, 2024. Accessed September 14, 2026. Passages: real-user data “over the previous 28-day collection period”; “PSI’s data is updated daily”; “When this happens, PSI will fall back to origin-level granularity” and “Sometimes the origin may also have insufficient data, in which case PSI will be unable to show any real-user experience data”; “the aggregation passes the Core Web Vitals assessment if the 75th percentiles of all three metrics are Good” and “If the aggregation has insufficient data for INP, then it will pass the assessment if both the 75th percentiles of LCP and CLS are Good”; and the Lighthouse performance score, which “analyze the given URL in a simulated environment”, with 90 or above as good.
- SEO Genome record, September 14, 2026. PageSpeed Insights, https://pagespeed.web.dev/, address https://seogenome.com/, report created at 6:20:46 a.m. (Brasília time), permanent link https://pagespeed.web.dev/analysis/https-seogenome-com/pjrax02vnn. The report was run with the interface in Portuguese; the labels here are the ones the same permanent link shows in the English interface, checked on September 14, 2026. Section “Discover what your real users are experiencing,” with the “This URL” button disabled (“Este URL” in Portuguese) and origin data, “Latest 28-day period.” Mobile: Core Web Vitals assessment “Passed” (“aprovado”), LCP 2.4 s, INP N/A, CLS 0.02. Desktop: “Passed,” LCP 2 s, INP N/A, CLS 0.01. Lab diagnosis on mobile (Lighthouse 13.4.1, emulated Moto G Power, slow 4G): performance 98. The new site has been live since September 2, 2026. Accessed September 14, 2026.
- Google Search Central, “Understanding page experience in Google Search results,” https://developers.google.com/search/docs/appearance/page-experience, page last updated December 10, 2025; Portuguese version, “Como entender a experiência na página em resultados da Pesquisa Google” (Understanding page experience in Google Search results), updated December 18, 2025. Accessed September 14, 2026. Passages: “Core Web Vitals are used by our ranking systems”; “There is no single signal. Our core ranking systems look at a variety of signals that align with overall page experience”; “getting good results in reports like Search Console’s Core Web Vitals report or third-party tools doesn’t guarantee that your pages will rank at the top of Google Search results”; “trying to get a perfect score just for SEO reasons may not be the best use of your time”; “Beyond Core Web Vitals, other page experience aspects don’t directly help your website rank higher in search results”; “Our core ranking systems generally evaluate content on a page-specific basis” and “However, we do have some site-wide assessments”; and “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.” In the self-assessment, the English asks “Do your pages have good Core Web Vitals?”; the Portuguese version says “Suas páginas têm Core Web Vitals?” (Do your pages have Core Web Vitals?).
Want to see SEO Genome more often on Google? Add it as a preferred source.
Let us look at what the machine understands about your company
A diagnostic conversation, with no slide deck. You bring your website address. We bring what Google and the AI assistants already know about it today.