Core Web Vitals explained for business owners
Core Web Vitals is a term you will hear from any developer or SEO specialist. Behind the jargon it is simple: three measurements of how good your site feels to use. Here is what they mean for your business.
The three metrics
LCP, Largest Contentful Paint, measures how fast the main content appears. In plain terms: how quickly the visitor sees that the page has loaded. Good is under 2.5 seconds.
INP, Interaction to Next Paint, measures how fast the page responds to a click or tap. Good is under 200 milliseconds.
CLS, Cumulative Layout Shift, measures how much elements jump around while loading. Good is under 0.1.
Why Google uses them
Google wants to show users sites that are fast and pleasant. A slow page that jumps and lags frustrates people.
Core Web Vitals are an official ranking factor. They are not the most important one, content quality matters more, but between two otherwise equal pages the faster one wins.
Why it affects revenue
The impact goes beyond Google. A slow site loses customers directly.
- Every extra second of load time lowers conversion
- Mobile users leave a slow site faster than desktop users
- A shifting layout makes people tap the wrong button, which frustrates them
Core Web Vitals are not a developer detail. They are a direct line to your revenue.
How to check and fix
Use Google PageSpeed Insights for an instant score, and Google Search Console for real-user data over time. Both are free.
The most common fixes are image optimisation for LCP, removing heavy scripts for INP, and reserving space for images and ads for CLS. A good developer can usually move all three into the green zone.
Why a small Estonian site often shows no real-user data
Open PageSpeed Insights for a young company site and the top block frequently says there is not enough real-world data. That is normal. Google builds that block from Chrome users who actually visited the page over the past weeks, and a site with modest traffic does not reach the minimum.
In that case the score you see further down is a lab test: one simulated visit on a slow phone. It is useful for finding problems, but it is not what Google uses to assess your pages, and it changes from run to run.
For a low-traffic site the practical routine is this. Test three page types instead of only the homepage: home, a service or product page, and the contact or checkout page. Run each test three times and look at the middle result. Then open the site on a real mid-range phone over mobile data. If it feels quick and nothing jumps, you are close enough.
Which parts of a typical Estonian site hurt which metric
Generic guides talk about images and scripts. On sites built for the Estonian market the usual suspects are more specific.
- Cookie banner: a banner that pushes the page down when it appears causes layout shift (CLS). One that overlays the page without moving content does not.
- Parcel locker selector: Omniva, SmartPosti and DPD modules load long lists of lockers. When they load on every page instead of only in the checkout, they slow the response to taps (INP).
- Bank link buttons: a row of bank logos that arrives late and shoves the order button down is a classic CLS problem at the worst possible moment.
- Three languages: fonts that must cover both Estonian letters and Cyrillic are heavier. Loading only the character sets a page needs helps the main content appear sooner (LCP).
- Language switcher redirects: sending a visitor from the root to a language folder adds a round trip before anything is drawn.
If your customers are not in Estonia
Many e-resident companies host in Estonia out of habit while their visitors sit in Germany, India or the United States. Distance adds delay to every request, and it shows up in LCP.
The fix is rarely to move servers. A content delivery network keeps copies of the pages close to the visitor, wherever the origin server stands. When you test, remember that PageSpeed Insights runs from Google's own locations, so also ask a customer or colleague in your main market how the site feels there.
FAQ
Where do I see my site's Core Web Vitals?+
Free tools: Google PageSpeed Insights gives an instant assessment, Google Search Console shows results from real users over time.
Does a bad score mean my site drops in Google?+
Not automatically. Core Web Vitals are one factor among many. But in a competitive niche they can decide between two similar pages.
Can an old site be fixed, or does it need a rebuild?+
Often it can be fixed: image optimisation, caching, removing heavy plugins. Sometimes a rebuild on a modern stack is simpler and cheaper.
PageSpeed Insights gives my site a different score every time. Which one is right?+
None of them exactly. The lab score is a single simulated visit and naturally varies. Run the test several times, take the middle value and watch the trend after changes. Where Google has enough visits, the real-user block at the top is the one that counts.
Are Core Web Vitals measured separately for each language version?+
Yes, they are assessed per page, and Search Console groups similar pages together. It is common for the English version to pass while the Russian or Estonian one fails because of a heavier font or a different banner, so test one page in every language.