Pragmatic CenterPragmatic CenterTechnology studio
Home/Journal/Core Web Vitals
Core Web Vitals · 12 February 2026

Core Web Vitals in plain words and how they affect sales

Google rates sites on three usability metrics — Core Web Vitals. We explain without jargon what they are, why they affect your place in search and your revenue, and how to tell whether your site is in good shape.

If you have ever talked to developers about a website, you may have heard the mysterious “we need to pull up the Core Web Vitals”. It sounds like a technical detail an owner does not need to get into. In fact, behind those words is something that directly affects both your site's place in search and how many people leave without waiting for it. In other words, money.

Let us explain it in human terms, without formulas.

What they actually are

Core Web Vitals are three metrics Google uses to measure how comfortable your site is to use. Not how beautiful it is and not how clever — precisely how comfortable it feels to a visitor. Did it load quickly. Does the page jump about. Does the site respond to actions without delay.

Google introduced these metrics because it grew tired of guessing at the usability of sites indirectly and decided to measure it directly, through the eyes of an ordinary visitor. And — this is the important part for you — it made them a ranking factor. All else being equal, a site with good scores will sit higher in search than a site with bad ones.

And this is not only a Google story. Every major search engine judges pages on the same principles. The wording and the metrics differ from one engine to another, but they all look at exactly the same things: did the page load quickly, is it comfortable to use, does someone on a phone struggle with it. A slow, awkward site drops everywhere at once. So by pulling up your Core Web Vitals you improve your positions across search engines — it is one and the same job, not several different ones.

There are three metrics, and each one has a simple, human meaning.

Metric one: how quickly the main thing appears

The first metric answers the question: how long does a person wait for the main content to appear on the screen — the large image, the headline, the thing they came for.

A good result is when the main content is drawn in about two and a half seconds or faster. If a person stares at an empty or half-loaded screen for longer, they start to get restless, and some visitors simply leave without having seen anything at all.

Essentially this is about the first impression. Slow-appearing content is like a salesperson who keeps you waiting at the door. Some people will wait; others will turn around.

Metric two: does the page jump about

The second metric is about the small annoyance that irritates everyone. You open a page, see the button you need, reach out to press it — and at that moment the page “jumps”, because an image or an advert has finished loading, and you press the wrong thing.

This metric measures how much the content shifts around while the page loads. A good site stays put: what appeared stays where it appeared. A bad one jumps about, and the user gets annoyed. On a checkout page a jump like that can cost you the sale at the very last step.

Metric three: how quickly the site responds

The third metric is about responsiveness. Someone pressed a button, clicked a filter, opened a menu — how quickly did the site react? A good site responds almost instantly. A bad one hesitates, and you get the feeling that the site is stalling and working with effort.

This metric matters especially for stores and interactive sites, where a person presses a lot of things. If every action comes with a delay, using the site is tiring, and patience does not last long.

Why this affects money, not just search

Here is the most important part. Google invented Core Web Vitals for ranking, but they measure exactly the things sales depend on.

A site that loads slowly, jumps about and lags in response to actions loses people at every step. One person leaves without waiting for it to load. Another misses the jumping button and gets irritated. A third gets tired of the delays and closes the tab. Each of these small things is a lost visitor — and at scale, a noticeable loss of revenue.

So by improving the scores for search you improve the site itself for people at the same time. And the other way round: a site that is comfortable for people usually passes Core Web Vitals well. Here Google and the user want the same thing.

How to tell whether your site is in good shape

You can check your site for free — Google has a tool called PageSpeed Insights: you enter the address of a page and get a score on all three metrics, separately for phone and for computer. Look at the mobile version first, because that is what search engines judge the site by and that is where most people come from today.

Do not walk past Google Search Console either. It shows how the search engine sees your site and whether it has any complaints about speed and the mobile version, and its Core Web Vitals report is built on data from real visitors: how quickly pages load and where people run into trouble. Together with PageSpeed Insights this gives you the full picture.

If the scores are in the green zone, excellent. If they are yellow or red, that is not a verdict, but a signal that the site is losing both visitors and positions, and that it is worth finding out why.

Why sites fail, and what to do about it

Most often the reasons are these: heavy unoptimised images and video, bloated code, a pile of third-party scripts and widgets, an outdated foundation that simply cannot be fast.

Sometimes it is all fixed by optimisation — tidying things up, taking out the excess weight, speeding up the load. Sometimes the problem is in the foundation, and then cosmetics will not help: the site is built in a way that cannot become fast. Which of the two applies in your case becomes clear once someone looks at the site. Either way, it can be solved.

The best option, of course, is when Core Web Vitals are thought about not after launch but from the very beginning. A site designed to be fast from the start passes these checks without heroic effort.

How we do it

At Pragmatic Center we build speed and comfort into the foundation of a site from day one instead of tuning them just before launch. We make sure our sites pass Core Web Vitals in the green zone on phones and look good to search engines, and we make sure video and effects decorate the site rather than sink its speed. More on why speed is money in the most direct sense you can read in our article about online stores.

If your site has problems with speed, or you want a site that is fast by default, write to us. We will take a look and tell you honestly what is going on.

Let's talk

Already have a task in mind?

A website, an online store or automation — tell us about it and we will say honestly how we can help.

The Pragmatic Center journal

  • 01How strong websites and stores are built.
  • 02Why speed matters more than it seems.
  • 03What automation really gives a business.