A painting business in Hildesheim, a tax firm in Sarstedt, a medical supply store in Alfeld: all three have a website, all three use it to win customers from the region - and for all three an invisible factor now helps decide whether Google places the page high up or far down. We are talking about the Core Web Vitals, three measurements Google uses to judge the actual user experience of a page: how quickly the main content appears, how promptly the page reacts to clicks, and how calmly the layout stays as it loads. It sounds technical, but at heart it is a simple question: does your website feel fast and stable - or sluggish and shaky? The figures show there is plenty of room to improve. A good 43 percent (Google CrUX) of all websites measured worldwide fail the Core Web Vitals, and only about 48 percent (HTTP Archive) of mobile pages pass all three at once. Whoever belongs to that majority gives away ranking and enquiries to faster competitors. This article explains clearly what LCP, INP and CLS mean, how to check the 75-percent threshold and what you can concretely improve.
Key takeaways
- Core Web Vitals measure the real user experience: LCP stands for the loading time of the main content, INP for how quickly the page responds to clicks, and CLS for layout stability while loading.
- Google evaluates the metrics at the 75th percentile of real visits - a page only counts as passing once 75 percent of visits are in the green range. A good lab score alone is not enough.
- Around 43 percent of all websites fail the Core Web Vitals (Google CrUX), and only about 48 percent of mobile pages pass all three (HTTP Archive) - there is tangible potential here.
- Core Web Vitals are a confirmed ranking factor that tips the balance above all between similarly strong pages - and they act directly on conversion, because slow pages cost enquiries.
- For local businesses the mobile view counts: fast hosting, optimised images, sparing scripts and a stable layout are the biggest levers to bring the three metrics into the green range.
What Core Web Vitals Are and Why Google Measures Them
Core Web Vitals are three metrics with which Google, since 2021, has tried to translate a soft impression into hard numbers: how good does a website feel for the person in front of it? Instead of merely checking whether a page works technically, Google measures how quickly the most important content becomes visible, how promptly the page answers the first interaction, and whether elements slip unexpectedly while you read or type. These values are not collected in a developer's lab but from the anonymised data of real Chrome users who have visited your page - the so-called Chrome User Experience Report. That is exactly what makes them so meaningful: they reflect the experience of your actual visitors, on their real devices and in their real networks.
That the effort pays off is shown by how good and poor scores are distributed. A good 43 percent (Google CrUX) of the measured websites fail the Core Web Vitals - so almost every second page misses at least one of the three metrics. On the smartphone, where most local searches happen, the situation is tighter still: only around 48 percent (HTTP Archive) of mobile pages pass all three. This is no footnote for technology enthusiasts, because more than half of worldwide web traffic now comes from mobile devices, around 60 percent (StatCounter). And Google judges pages primarily from the mobile perspective, ever since it switched indexing to mobile-first (Google Search Central). Anyone who assesses their page only on a large desktop screen overlooks exactly the view that counts for ranking.
The timing of the most recent change matters: in March 2024 Google introduced the INP metric and thereby replaced the older First Input Delay value (Google Search Central). INP no longer measures only the delay to the first reaction but the responsiveness across the whole visit - a markedly stricter yardstick. Businesses that last had their page checked before 2024 may therefore be working with outdated assumptions. Each of the three current values has a clear target corridor, summarised in the overview below.
LCP - loading time
Largest Contentful Paint measures when the largest visible content appears - usually the main image or the headline. Under 2.5 seconds counts as good. For local pages, LCP is often the biggest lever, because hosting and images weigh in heavily.
INP - responsiveness
Interaction to Next Paint measures how quickly the page reacts to clicks and inputs. Under 200 milliseconds counts as good. INP is often the hardest metric to reach, because overloaded scripts slow the response down.
CLS - stability
Cumulative Layout Shift measures how much the layout slips while loading. Under 0.1 counts as good. CLS is often the easiest win: fixed dimensions for images and ads are usually enough so nothing jumps.
The 75-Percent Threshold: Why Almost Good Is Not Enough
The most common error with Core Web Vitals is the assumption that a single fast test run proves the page is fine. Google, however, does not judge an ideal case but the breadth of your visitors. What matters is the 75th percentile: only once 75 percent (Google Search Central) of real page views are in the green range for a value does that value count as passing - and this must hold for all three metrics at the same time. Put differently: even if your page loads in a flash on a new device with a fast network, it can fail if a quarter of your visitors are on older phones or weaker networks and wait noticeably longer there.
From this follows an important distinction that surprises many businesses: there is lab data and there is field data. Lab data arises when a testing tool measures your page once under controlled conditions - handy for troubleshooting, but only a snapshot. Field data comes from real visits in the Chrome User Experience Report and is what Google uses for ranking. A green lab score with a red field score is therefore no contradiction but the normal case for pages whose visitors bring a wider variety of devices than the test reflects. Anyone taking Core Web Vitals seriously looks at the field data first.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP (loading time) | up to 2.5 s | 2.5 to 4 s | from 4 s |
| INP (responsiveness) | up to 200 ms | 200 to 500 ms | from 500 ms |
| CLS (layout stability) | up to 0.1 | 0.1 to 0.25 | from 0.25 |
| Passing (all three) | 75 % of visits in the green range | less than 75 % |
Read the field data first
Improving LCP: the Biggest Lever for Local Pages
On most local business websites, LCP is the metric with the greatest room for improvement, because it hangs on factors you can get a good grip on. The value measures when the largest visible content block appears - typically the hero image or the main headline. If that moment is delayed, the visitor waits in front of a seemingly empty page, and in exactly this waiting time many decide against a business. That patience is short is shown clearly by the figures: 53 percent (Google) of mobile users leave a page that takes longer than three seconds to load, and half expect a build-up in under two seconds (Google). Every tenth of a second saved therefore pays off immediately.
The first lever is the foundation: fast, well-connected hosting with a short server response time. If the server is sluggish, half the loading time is already lost before any image appears. Solid web hosting from Germany with modern technology and geographic proximity to the audience noticeably shortens this base delay. The second big lever is images: on most pages they are the heaviest ballast. Modern formats, sizes matched to each device and loading only on scroll often bring more than any other single measure. The third lever is the code itself - lean templates without superfluous add-ons load faster than overstuffed builder pages.
- Lower the server response time: fast hosting close to the audience with an active cache.
- Deliver images in modern formats and in exactly the size needed instead of oversized.
- Load the main image with priority and load secondary images only on scroll.
- Embed fonts locally and control their display so text does not wait invisibly for the font.
- Defer non-visible code and remove unused style and script leftovers.
- After each change, check again from the field data whether the green range is reached.
INP and CLS: the Page's Response and Calm
While LCP concerns loading time, INP is about the feeling that the page responds to you. When someone taps a menu, a dropdown or a submit button and nothing happens for a moment, the impression of a jerky page arises - even if it loaded quickly. INP measures this responsiveness across the whole visit and is thus stricter than the old First Input Delay value that Google replaced in March 2024 (Google Search Central). The most common cause of poor scores is overloaded scripts, often from embedded third-party services such as chat windows, map displays or several analytics tools that block the page's main process. Fewer and more sparingly embedded scripts are the most effective route here.
CLS, finally, measures visual calm. Everyone knows the moment when you want to tap a button and at the last instant a late-loading image or a notice banner pushes everything down - the tap lands off target. Such jumps are not only annoying, they cost trust and, in case of doubt, an enquiry. The good news: CLS is usually the easiest value to fix. If images, videos and ad spaces receive fixed dimensions from the start, the space is reserved and nothing jumps. Fonts and late-loaded content can likewise be embedded so that they do not shift the layout. A calm, stable page feels more valuable and guides visitors more reliably to the goal - the enquiry form.
Keep an eye on third-party scripts
What the Metrics Mean for Ranking and Enquiries
Core Web Vitals are a confirmed part of the page experience assessment and feed into the Google ranking (Google Search Central). Their role should be judged correctly, though: they are no miracle cure that catapults a content-weak page to the front. Their effect unfolds above all where several pages are similarly strong in content - then the better user experience tips the balance. For local businesses that wrestle with direct competitors over the same regional search terms, that is often exactly the situation where it counts. Those who are faster and more stable here sort themselves ahead of the competition in the mobile ranking. How this interacts with your other local search engine optimisation reinforces the effect further.
Even more immediately than ranking, speed acts on conversion, that is, on the number of enquiries a page actually produces. The research is clear: according to Deloitte's analysis, a mobile page just 0.1 seconds (Deloitte) faster raises retail conversions by 8.4 percent and the average order value by 9.2 percent (Deloitte); in the travel sector conversions rose by 10.1 percent (Deloitte). And pages that load within five seconds record on average 70 percent (Google) longer sessions and a markedly lower bounce rate than very slow pages. Speed is therefore no end in itself but pays directly into revenue - every enquiry that does not fail at the waiting time is a possible job.
Speed is sold time
How Local Businesses Approach the Measurement
Before anything is optimised, it should be measured - otherwise you work in the dark. Getting started is free and possible without programming knowledge. The Google Search Console bundles your page's field data and shows which addresses are rated good, in need of improvement or poor, grouped by similar behaviour. A second tool complements the diagnosis with concrete hints per page and reports both field and lab data at once. This way you first recognise where the problem lies, and then why. It is important to view each page in its mobile version, because that is where the view decisive for ranking is settled.
- Open the field data in the Google Search Console and see which page groups miss one of the three values.
- Check the affected pages individually with a diagnostic tool and compare field against lab data.
- Sort the causes: is it the loading time (LCP), the response (INP) or the layout (CLS)?
- Start with the biggest lever - for local pages usually hosting and images for a better LCP.
- After implementation, wait a few weeks until enough new field data is available, then check again.
- Monitor the state regularly so that new content or add-ons do not quietly worsen the values.
You cannot see a website's speed - you feel it. And what the visitor feels, Google measures too.
Optimise or rebuild?
Realistic Expectations: Measure, Improve, Keep At It
As important as good Core Web Vitals are, their role should be viewed soberly. No one can credibly assure a specific ranking or a fixed number of enquiries, because too much depends on industry, competition and search behaviour. What can be said: a page in the green range removes an avoidable hurdle and no longer gives away prospects to the waiting time. Moreover, the values are not a one-off task. Every new image, every additional add-on and every embedded third-party service can worsen them again - speed is a state you maintain, not a certificate you acquire once. That is why regular checks of the field data belong to reliable website care that keeps speed and conversion optimisation in view together.
For local businesses a clear, workable path results: measure first, then work on the biggest lever, then verify the success against real field data and hold the state. How such an approach looks and what results are achievable in practice can be seen in our references. Anyone who also wants to stay visible in AI answers will find the right follow-on in our article on GEO for local businesses, because fast, clean pages help there too. Which steps make the biggest difference for your page we are happy to clarify in a no-obligation conversation - with honest expectations and a clear plan.