Your speed shows before they click
Structure and markup refreshed for current answer engines; the original analysis is preserved.
Google announced this month that Chrome for Android will start labelling links as a “Fast page” — a badge shown in the context menu, before anyone visits, for pages that have historically met the Core Web Vitals thresholds. It is a small feature with a meaningful shift behind it: your page performance stops being an invisible ranking input and becomes a visible mark of quality that people see while deciding whether to click. Speed is no longer just counted; it is shown.
the short answer
Chrome for Android will badge links as a “Fast page” in the context menu — shown before anyone visits — for pages that historically meet the Core Web Vitals thresholds, judged on field data over ~28 days, host-by-host where a URL lacks data. It isn’t a ranking factor yet, but it changes who clicks: a badged link beats an unbadged one. The deeper shift — your page experience becomes public, a mark of quality beside your link.
key takeaways
- Google announced this month that Chrome for Android will badge links as a “Fast page” in the context menu — shown before anyone visits — for pages that historically meet the Core Web Vitals thresholds.
- The judgement uses field data from real Chrome users over a trailing ~28-day window, refreshed about twice a week; where a URL lacks data, it falls back to a host-by-host assessment.
- It is not a ranking factor (that is coming, with notice, next year). For now it changes who clicks: a badged link beside an unbadged one wins the tap, so it moves click-through.
- The deeper shift is that your page experience becomes public. A quality judgement Google used to keep private now sits next to your link as a mark of endorsement — that is reputation made visible.
- Earn it on field data, site-wide: improve real-world Core Web Vitals across the host, not one page, and let the ~28-day window catch up. Quality good enough to be shown, not just to scrape by.
what the user sees, before clicking
The badge sits in the moment of choosing, not after it. That is why a feature that touches no ranking can still move your traffic — and why it is better read as reputation than as a speed tweak.
The idea, in four parts
What Google announced; how quality becomes visible before the click; why a badge is a reputation, not just a metric; and what to do about it. Open each part.
01 What Google announced
This month Google said that Chrome for Android will begin labelling links as leading to a “Fast page.” The label appears in the link context menu — the menu you get when you long-press a link before opening it — shown with a blue checkmark, and it indicates that most users navigating to that page have historically had a particularly good experience. It starts rolling out in Chrome 85 Beta. The judgement behind the badge is the Core Web Vitals, the metrics Google introduced earlier this year to capture loading, interactivity, and visual stability, measured not in a lab but from real Chrome users in the field. Links to pages that have historically met or exceeded all of the Core Web Vitals thresholds get labelled. Three mechanics are worth holding onto, because they shape how you would earn the label. First, it runs on field data — real-world measurements aggregated over a trailing window of about 28 days, refreshed roughly twice a week — so it reflects sustained real performance, not a one-off test. Second, when a specific URL lacks enough data, Google assesses it host by host, aggregating data from URLs with a similar structure, so a new or unpopular page inherits the speed reputation of the site around it. Third, and importantly for reading this correctly, the label is not the ranking change: Google has said page experience will become a ranking factor, but not yet. For now the badge is purely about what a person sees next to your link — and that turns out to be the whole story.
02 Quality becomes visible before the click
The reason this small feature matters is that it moves a judgement that used to be invisible into the most consequential moment there is: the instant someone decides whether to click. Until now, your page speed was Google’s private business. It measured it, it might let it influence where you ranked, but the person scanning a results page or a list of links had no way to know how fast any destination was until they had already gone there and waited. The “Fast page” label changes that completely. Now, before committing, a user long-pressing a link can see whether the page on the other side is marked as fast. Think about what that does to choice. Place two links next to each other — one carrying a “Fast page” badge and a blue checkmark, the other plain — and the badged one has an edge that has nothing to do with its content, an edge that is strongest for exactly the users Google built this for: people on slow or unreliable connections who have learned to dread a heavy page. The label does not need to be a ranking factor to matter, because it acts before ranking is even relevant: it shapes which link gets the tap. And click-through is not a vanity number; it is traffic, the thing the ranking was supposed to win you in the first place. Your performance has stepped out from behind the curtain of the algorithm and onto the surface of the page, where users act on it directly.
03 A badge is a reputation, not just a metric
Look closely at what the label is, and it is less a speed feature than a reputation mechanism — which is the part most people will overlook while they focus on the milliseconds. On the surface the logic is simple: meet the Core Web Vitals thresholds, earn the badge. But consider what the badge actually does in the world. Google is taking a quality judgement it formerly kept private and displaying it to your prospective visitors, as a mark of endorsement, right beside your link, at the exact moment they decide. That is reputation made visible. A third party whose judgement people trust — Google — is vouching for your page, or pointedly not vouching for it, before anyone has seen a word you wrote. Appearing without the badge next to a competitor who has it is a real disadvantage, and notice that it is a disadvantage of presentation, not of substance: your content might be better, but Google is framing them as the safe, fast choice and you as the unknown. This is a pattern Google has run before, and recognising it helps. Years ago it attached a “mobile-friendly” label to pages that worked well on phones, using it to steer users toward those pages and developers toward building them, and it kept the label until most of the web had complied. Labels are the lever by which Google converts a technical standard into a reputational one: it makes the quality visible, lets the side-by-side comparison do the persuading, and the whole ecosystem shifts to earn the mark. So the question this raises is not merely is my page fast. It is is my page publicly vouched for — because a public vouch, or its absence, is now part of how you are presented. And earning the marks that trusted third parties choose to display about you is a different and older discipline than tuning the numbers they measure in private; it is the one the AC Group has worked in for {years} years.
04 What to do about it
Treat the badge as something to earn on the terms it is judged: real-world Core Web Vitals, assessed across your whole site, with patience for the measurement lag. Begin with field data rather than a lab score, because the label reflects what actual Chrome users experience over a trailing window — so the Core Web Vitals report in Search Console and the field data in PageSpeed Insights are the instruments that matter, with Lighthouse and DevTools to find and fix the causes of slow loading, sluggish interactivity, or shifting layout. Then respect the host-by-host fallback: because pages without their own data are judged on the site’s aggregate, you cannot buy the badge for one showcase page while the rest of the site lags — a new or quiet page inherits the reputation of the whole host, so the whole host has to be in good shape. Build in the lag as well: field data accumulates over roughly 28 days and refreshes about twice a week, so a fix you ship today surfaces gradually, not at once — do the work early and let the window confirm it. And keep the larger trajectory in view while you do the technical part: Google has been clear this is an early step, that page experience is something it intends to show in more places and, before long, to rank on, so the work you do to earn a visible badge now is the same work that will hold up your rankings later. The mindset that pays off is to stop treating performance as a private hygiene task and start treating it as part of your public reputation — build a site whose quality is good enough to be displayed, not merely good enough to pass unnoticed. That reputational discipline, earning the marks others show about you, is the one the AC Group has worked by for {years} years.
Why this is a reputation point, not a speed tip
The easy reading of this is a performance to-do: chase the Core Web Vitals, earn the badge, move on. That reading is not wrong, but it stops at the surface. What actually changed this month is not that speed matters — it already did, quietly, for ranking — but that your speed became something other people can see, attached to your link, at the moment they choose. A private metric turned into a public signal. And public signals do work that private ones never could: they let strangers judge you before they meet you, and they invite comparison, because the badge you have or lack is right there next to the badge your competitor has or lacks.
That is why the right lens is reputation. The label is a small instance of a large and recurring move: a trusted intermediary takes a judgement about you and shows it to the people deciding about you. Whether the judgement is speed, a star rating, or a verification check, the dynamic is the same — what is displayed about you shapes the choice as much as what is true about you, and often sooner. Earning the marks that trusted parties choose to display, rather than only tuning the things they measure in private, is the reputational work the AC Group has done for 27 years.
What to do with this
Work it on the terms the badge is judged. Measure your field data, not a lab score, since the label reflects what real Chrome users experience over a trailing window — the Core Web Vitals report in Search Console and the field data in PageSpeed Insights are the instruments, with Lighthouse and DevTools to find causes. Treat it as a site-wide job, not a per-page one: because pages without their own data are judged host by host, a fast hero page cannot rescue a slow site, and a new page inherits the whole host’s reputation. Build in the lag — field data accumulates over about 28 days and refreshes roughly twice weekly — so fix early and let the window confirm it.
Then hold the larger frame. Google has signalled this is an early step — that page experience will be shown in more places and, before long, ranked on — so the work that earns a visible badge now is the same work that protects your position later. The shift in mindset is the real point: stop treating performance as a private hygiene chore and start treating it as part of your public reputation, building a site whose quality is good enough to be displayed rather than merely good enough to pass unnoticed. Earning the marks others show about you is the reputational discipline the AC Group has worked by for 27 years.
The “Fast page” label, plainly: quick answers
What is the “Fast page” label?
It is a label Google announced this month that Chrome for Android will show in the link context menu — the menu you get when you long-press a link before navigating to it — marking links that lead to a “Fast page.” The badge, shown with a blue checkmark, indicates that most users navigating to that page have historically had a particularly good experience. It rolls out starting in Chrome 85 Beta. The judgement is based on the Core Web Vitals: the metrics Google introduced earlier this year for loading, interactivity, and visual stability, measured from real Chrome users rather than a lab test. Links to pages that have historically met or exceeded all the Core Web Vitals thresholds get the label. A few mechanics matter. The assessment uses field data — real-world measurements aggregated over a trailing window of about 28 days — and the labelling is refreshed roughly twice a week, so it reflects how your pages actually perform for people over time, not a single snapshot. And when there is not enough data for a specific URL, Google evaluates it host by host, aggregating data from URLs with a similar structure, so a new or low-traffic page inherits the speed reputation of the site around it. The label is separate from ranking — Google has said page experience will become a ranking factor, but not yet — so for now this is purely about what users see next to your link, before they choose whether to follow it.
Why does a label matter if it isn’t a ranking factor yet?
Because it changes who clicks, which matters whether or not it changes who ranks. Until now, your page speed was something Google measured invisibly — it might affect where you ranked, but a person scanning results had no idea how fast any given page was until they landed on it. The label moves that judgement forward, into the moment of choosing. A user long-pressing a link now sees, before committing, whether the destination is marked as fast. Put two links side by side — one with a “Fast page” badge and a blue checkmark, one without — and you do not need a study to guess which gets the tap, especially from someone on a slow or unreliable connection, which is exactly who this feature is aimed at. So even with ranking untouched, the label can move your click-through, and click-through is traffic. There is a second reason it matters: it is a preview of direction. Google has been signalling for months that page experience is becoming something it rewards, and has already said the ranking change is coming, with notice, sometime next year. The label is that intent made visible early — a way of both nudging users toward fast pages and nudging developers toward building them, before the ranking consequences arrive. Treating the badge as a harmless cosmetic thing misreads it. It is the first place your page experience becomes public, and public quality signals shape behaviour.
Is this really an authority question, or just a speed one?
It is both, and the authority part is the one most people will miss. On the surface it is about speed: meet the Core Web Vitals thresholds and you earn the badge. But look at what the badge does and it is a reputation mechanism. Google is taking a quality judgement it used to keep to itself and displaying it to your prospective visitors as a mark of endorsement, right next to your link, at the moment of decision. That is reputation made visible — a third party whose judgement people trust is vouching, or declining to vouch, for your page before anyone sees it. Showing up without the badge beside a competitor who has it is a perceptible disadvantage that has nothing to do with your content and everything to do with how Google is presenting you. This is not new behaviour from Google, which is worth knowing: it used a “mobile-friendly” label years ago to flag phone-ready pages and steer both users and developers, keeping it until most of the web had complied. Labels are how Google turns a technical standard into a reputational one — it makes the quality visible, lets the comparison do the persuading, and the ecosystem moves. So the right frame is not just is my page fast but is my page publicly vouched for, because the second is what now sits beside your link. Earning the marks that third parties display about you, rather than only optimising the things they measure quietly, is the work the AC Group has done for 27 years.
How do I earn the label?
Earn it the way it is judged: by improving your real-world Core Web Vitals until your pages meet the thresholds for loading, interactivity, and visual stability, and by treating it as a site-wide reputation rather than a per-page fix. Start by measuring the field data, not a lab score — the label is based on what real Chrome users experience over a trailing window, so the Core Web Vitals report in Search Console and the field data in PageSpeed Insights are what to watch, with Lighthouse and DevTools to diagnose causes. Because the assessment falls back to a host-by-host evaluation when a URL lacks data, you cannot earn the badge by optimising one hero page while the rest of the site is slow; new and low-traffic pages inherit the site’s aggregate reputation, so the whole host has to be healthy. Account for the lag, too: field data accumulates over about 28 days and refreshes roughly twice weekly, so improvements show up gradually, not instantly — fix early and let the window catch up. And hold the wider point while you do the technical work: this is the first of what Google signalled will be more ways your experience is shown and, before long, ranked, so the investment compounds. Building a site whose quality is good enough to be displayed publicly — not just good enough to scrape by quietly — is the reputational discipline the AC Group has worked by for 27 years.
A note on sources and timing
This is written in August 2020, just after Google announced “Fast page” labelling for Chrome on Android. The description — a badge in the link context menu, shown with a blue checkmark for pages that have historically met the Core Web Vitals thresholds, judged on field data over a roughly 28-day window and host-by-host where a URL lacks data, rolling out in Chrome 85 Beta — follows Google’s own announcement, as does the note that page experience is slated to become a ranking factor at a later date with advance notice. The reading offered here — that a visible badge is a reputation signal, not just a speed metric — is our interpretation, set against Google’s earlier use of a “mobile-friendly” label to the same end. The durable point outlasts this one feature: when quality becomes visible, earning it publicly is reputation — the discipline the AC Group has worked by for 27 years.