Core Web Vitals explained simply

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content appears, how quickly the page responds when someone taps, and whether things jump around while it loads. Explained simply, they measure the frustration you feel on a slow website, turned into numbers.

They matter for two reasons. Google uses page experience as one of many ranking signals, so poor scores can hold a page back when competitors are otherwise similar. And, more directly, slow and jumpy pages lose customers before they read your offer. You do not need to become a developer to understand them; you need to know what each number means and when to worry.

The three Core Web Vitals

LCP: how long until the main thing shows

Largest Contentful Paint measures how long it takes for the biggest visible element, usually the main photo or headline block, to appear. Google considers 2.5 seconds or less good, and more than 4 seconds poor.

In plain terms: when someone taps your site in search results, how long do they stare at a blank or half-built screen? Large uncompressed photos, slow hosting and heavy page builders are the usual culprits.

INP: how fast the page reacts

Interaction to Next Paint replaced an older metric (First Input Delay) in March 2024. It measures how quickly the page visibly responds after someone taps a button, opens a menu or types in a form. Good is 200 milliseconds or less; above 500 milliseconds is poor.

In plain terms: does the menu open when you tap it, or do you tap twice because nothing happened? Too much JavaScript, often from chat widgets, tracking scripts and plugins, is the usual reason pages feel sluggish.

CLS: does the page jump around

Cumulative Layout Shift measures unexpected movement of content while the page loads. Good is 0.1 or less; above 0.25 is poor.

In plain terms: you go to tap "Call now" and a banner loads above it, so you tap an ad instead. Images without set dimensions, late-loading fonts and banners that push content down cause most layout shifts.

Lab data versus real-user data

Here is where many owners get confused. There are two kinds of measurements:

	Lab data	Field data
Where it comes from	A simulated test run once	Real Chrome users visiting your site
Shown in	PageSpeed Insights (lower section), Lighthouse	PageSpeed Insights (top section), Search Console
What it is good for	Finding causes, testing fixes	Knowing how real visitors experience the site
Used by Google for ranking	No	Yes

Google judges Core Web Vitals on field data, at the 75th percentile: three out of four visits should hit the "good" mark. A small local business may not have enough traffic for field data on every page, in which case Google groups pages or shows nothing. The lab score from PageSpeed Insights is a diagnostic tool, not a grade. Chasing a perfect 100 there is rarely worth the money.

How to check your site in 10 minutes

1. Open PageSpeed Insights and enter your homepage. Look at the top section first: does it say your Core Web Vitals assessment passed or failed?
2. Switch between mobile and desktop. Mobile is usually worse and matters more for local businesses.
3. Repeat for your most important service page, not just the homepage.
4. In Google Search Console, open the Core Web Vitals report. It groups URLs into good, needs improvement and poor, using real-user data.
5. Note which of the three metrics fails. That tells you where to look.

What usually fixes each metric

For slow LCP:

• compress and resize images, and serve modern formats such as WebP;
• avoid huge sliders and background videos at the top of the page;
• improve hosting or add a content delivery network;
• reduce render-blocking CSS and fonts.

For poor INP:

• remove plugins and widgets you do not use;
• load chat widgets and non-essential scripts after the page is usable;
• audit tracking tags in Google Tag Manager, keeping only those you need.

For high CLS:

• set width and height on images and video embeds;
• reserve space for banners, cookie notices and ads;
• load fonts in a way that does not reshuffle the text.

Why some sites struggle more than others

Sites built on heavy page builders or with dozens of plugins often carry code for features nobody on the page uses. Every theme option and every widget adds weight. That is a big part of why I build hand-coded websites or sites on a custom CMS: the page only loads what it needs. That said, I do not promise a specific PageSpeed score, because hosting, third-party scripts and your own future additions all affect it.

A well-built WordPress site can pass Core Web Vitals too; it just takes more discipline over time. I compare the options in WordPress or a custom-built site.

A word on what owners add later

Many sites pass Core Web Vitals at launch and fail a year later. The usual story: a chat widget here, a review carousel there, a second analytics tag, a popup for a seasonal offer, a big hero video because a competitor has one. Each addition seems harmless. Together they double the amount of code a phone has to process.

A simple habit helps: every time something is added to the site, run PageSpeed Insights before and after. If one widget turns a green result orange, decide whether it earns its place. Fewer, better tools almost always beat more tools.

How much should you care?

Core Web Vitals are a tie-breaker, not a magic switch. Relevant content, clear service pages and a strong Google Business Profile matter more for local rankings. But speed affects every visitor, including the ones you pay for through ads. If your pages are in the "poor" range on mobile, fixing that is worth doing before buying more traffic.

If your site fails on all three metrics and runs on an aging theme, a website speed optimization project or a rebuild may be cheaper than endless patching. For other technical checks, see the technical SEO checklist.

If you are weighing a rebuild against fixes, see when to redesign your website, and for a professional check of speed and tracking, a free audit.