Himanshu SharmaSoftware engineer
Let’s talk

SEO Basics · Lesson 21 of 32

Core Web Vitals and page speed for SEO

Learn the three Core Web Vitals (LCP, INP, CLS), their documented good thresholds, how field and lab data differ, and practical fixes for slow pages.

12 minTechnical SEOUpdated 14 November 2026

Awaiting technical review. This lesson is readable but not yet listed in search engines.

By the end of this lessonName the three Core Web Vitals and their good thresholds, read a field versus lab report, and choose practical fixes for each metric.

After this lesson you can read a Core Web Vitals report, say which metric is failing, and name a practical fix for it. You will also keep speed in proportion: it helps people first, and search benefits second.

What the metrics are

Core Web Vitals are a set of measures of real user experience, defined by Google and documented on web.dev. As of 2026-11, the three are:

Metric Measures Good threshold
Largest Contentful Paint (LCP) Loading: when the biggest visible element appears 2.5 seconds or less
Interaction to Next Paint (INP) Responsiveness: delay between an interaction and the next visual update 200 milliseconds or less
Cumulative Layout Shift (CLS) Visual stability: how much content jumps 0.1 or less

Web.dev states that a page is assessed at the 75th percentile of page loads, split by mobile and desktop, and passes when all three are good. These thresholds and metrics have been revised before (INP replaced an older responsiveness metric), so check web.dev if you read this much later.

How much do they matter for ranking

Google's documentation says its ranking systems favour content with good page experience, and that Core Web Vitals are part of what it looks at. It also says that great page experience does not override having great, relevant content. The honest reading: they matter, they are not a magic lever, and a fast page that does not answer the query will not rank for it. Fix problems that hurt people, and you will fix the SEO side along the way.

Field data and lab data

  • Field data comes from real visits, such as the Chrome User Experience Report. It is what counts for assessing a page and what Search Console's Core Web Vitals report shows, for URLs with enough traffic.
  • Lab data comes from a simulated test, as in Lighthouse. It is repeatable and good for debugging, but it is one device on one connection, and lab scores can differ from field results.

PageSpeed Insights shows both for a URL. Do not chase a perfect score; aim for good field metrics.

Fixing LCP (loading)

The largest element is often a hero image or a big heading.

  • Compress and resize images; use modern formats. The image compressor shows the size savings. See image SEO.
  • Do not lazy-load the main above-the-fold image.
  • Reduce server response time: caching, a fast host, a content delivery network.
  • Remove render-blocking scripts and large unused CSS.
  • Avoid chains where the browser must download several things in sequence before the image can start.

Fixing INP (responsiveness)

INP is hurt when the main thread is busy.

  • Ship less JavaScript; remove unused libraries.
  • Split long tasks so the browser can respond between them.
  • Avoid heavy work in click handlers.
  • Be wary of third-party scripts such as chat widgets and tag managers.

Fixing CLS (stability)

Layout shift happens when something appears and pushes content.

html
<style>
  .hero { width: 100%; max-width: 480px; aspect-ratio: 3 / 2; background: #ddd; }
</style>
<img class="hero" width="480" height="320" alt="Placeholder showing reserved space for an image"
     src="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='480' height='320'%3E%3Crect width='480' height='320' fill='%23c8d6e5'/%3E%3C/svg%3E">
<p>This text does not jump when the image loads, because the image has width and height.</p>
  • Set width and height (or aspect-ratio) on images and embeds.
  • Reserve space for ads and banners.
  • Avoid inserting content above existing content after load.
  • Be careful with web fonts that change text size when they load.

A sensible routine

  1. Check Search Console's Core Web Vitals report for groups of URLs that need work.
  2. Run PageSpeed Insights on a template page, not just the home page.
  3. Fix the biggest cause for your failing metric.
  4. Re-measure. Field data takes weeks to reflect changes, because it covers a rolling period.

Pages built from one template often share problems, so fixing the template improves many URLs at once. This site is exported as static files, which tends to help server response time, but this lesson makes no claim about its measured scores.

Common mistakes

  • Optimising the lab score while real users on slow phones still suffer.
  • Lazy-loading the main image.
  • Adding many third-party scripts without measuring them.
  • Images with no dimensions.
  • Expecting the Search Console report to change overnight.
  • Treating speed as the whole of SEO.

Exercise

Run a page you care about through PageSpeed Insights. Record which of the three metrics is weakest, and list the first two suggestions the report gives for it. Then decide which one you would do first and why.

Show how to choose

Pick the fix that is cheap and affects the failing metric most. For a poor LCP caused by a large hero image, compressing and resizing it is quick and safe. For a poor CLS caused by missing image dimensions, adding width and height is a one-line change per image. Write the expected effect as a hypothesis and re-measure after the field data updates.

Key points

  • Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability).
  • As documented on web.dev, good means LCP at or under 2.5 seconds, INP at or under 200 ms and CLS at or under 0.1, at the 75th percentile of page loads.
  • Field data comes from real users; lab data is a controlled test that helps you debug.
  • Page experience is one of many signals; content relevance still matters most, so do not expect speed alone to rank a page.

Check yourself

1. Which metric measures how quickly the main content appears?
2. What is a good CLS score according to web.dev?
3. What does the 75th percentile mean in this context?
4. What is the usual cause of layout shift when an image loads?

Free tools for this lesson