Chykalophia Docs

Google's three measurements of loading, responsiveness and visual stability, explained in plain English — what they measure, what the targets are, and why they matter for your site.

Core Web Vitals are three measurements Google uses to judge how good your page feels to a real visitor. Google's ranking systems use them too, although there is no single score to pass and good numbers on their own will not lift you to the top of the results. This guide explains each one clearly.

Quick summary

Google measures three things: how fast your main content loads (LCP), whether your page moves around unexpectedly (CLS), and how quickly it responds to clicks and taps (INP). Each has a target range — green means good, red means needs work.

The three Core Web Vitals

1. Largest Contentful Paint (LCP) — loading speed

LCP measures how long it takes for the largest visible piece of content to appear on screen. This is usually your hero image, a large heading, or a banner.

Think of it as: "When does the visitor see the main thing they came for?"

Result	Score
2.5 seconds or less	Good
More than 2.5, up to 4.0 seconds	Needs improvement
Over 4.0 seconds	Poor

What causes a bad LCP? Usually a large, unoptimized hero image, slow hosting, or a heavy page that has to load many files before it can display anything.

2. Cumulative Layout Shift (CLS) — visual stability

CLS measures how much the page layout jumps around while it is loading. You know the experience: you go to click a button, something loads above it at the last second, and you click the wrong thing.

Think of it as: "Does the page stay still as it loads?"

Result	Score
0.1 or less	Good
More than 0.1, up to 0.25	Needs improvement
Over 0.25	Poor

CLS is measured as a score (not seconds). Lower is better. A score of 0 means nothing moved at all.

What causes a bad CLS? Images without defined dimensions (so the browser does not reserve space), ads that load after the page, and web fonts that swap in late.

3. Interaction to Next Paint (INP) — responsiveness

INP measures how quickly the page responds after you click, tap, or press a key. If you tap a button and nothing happens for a second, that is bad INP.

Think of it as: "Does the page feel alive and responsive?"

Result	Score
200 milliseconds or less	Good
More than 200, up to 500 milliseconds	Needs improvement
Over 500 milliseconds	Poor

What causes a bad INP? JavaScript that runs too much work when you interact with the page. Heavy plugins are often the culprit.

INP replaced FID in 2024

You may have heard of "First Input Delay" (FID). INP became a Core Web Vital and replaced FID on 12 March 2024, and FID was deprecated in the same move. FID only measured the delay on the very first interaction; INP looks at all of them.

How Google uses Core Web Vitals

Google says its core ranking systems do use Core Web Vitals. But there is no single "page experience" signal to pass or fail: Core Web Vitals sit alongside other things Google's systems look for, such as serving pages securely, working properly on a phone, and not burying the content under ads and pop-ups.

This is not a magic ranking formula. Google's own guidance is blunt about it — good Core Web Vitals scores do not guarantee that your pages will rank at the top, and chasing a perfect score purely for SEO may not be the best use of your time. Great content and strong SEO still matter more. But Core Web Vitals are a real factor, and they are worth fixing for your visitors either way.

How to check your Core Web Vitals

The easiest way is Google PageSpeed Insights (free):

Go to PageSpeed Insights. Visit pagespeed.web.dev in your browser.

Enter your URL. Type or paste your website address and press Analyze.

Look at the Core Web Vitals section. Each metric shows green (good), amber (needs improvement), or red (poor). The real-visitor data comes first; the simulated lab test from Lighthouse follows underneath.

See How to measure your site's speed for more tools and a deeper walkthrough.

Common questions

Do Core Web Vitals affect mobile and desktop separately?

Yes. Core Web Vitals are assessed separately for mobile and desktop, and Search Console's Core Web Vitals report makes you pick a device type. If most of your visitors arrive on a phone, the mobile numbers are the ones to care about. Your desktop scores may look better because desktop machines usually have faster processors and connections.

What if I don't have enough real visitor data?

Google PageSpeed Insights only shows real-visitor data if that page has enough of it. A page that is new or quiet may not qualify, in which case PageSpeed Insights falls back to data for your site as a whole — and if that is thin too, it shows no real-visitor data at all. You still get the simulated lab test, which is enough to find problems and improve.

Can I have a good speed score but still fail Core Web Vitals?

Yes, and the reason is that the two come from different places. The 0–100 performance score comes from the simulated Lighthouse test; the Core Web Vitals pass or fail comes from what real visitors actually experienced. So a good score can sit next to a failing Core Web Vital, and the other way round. Focus on the individual Core Web Vitals, not just the overall score.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.

Core Web Vitals explained