Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 36 ยท Technical SEO

Core Web Vitals and Page Speed

Learn what the Core Web Vitals (LCP, INP, CLS) measure, their recommended thresholds, lab versus field data and the practical fixes that make pages faster.

Fast pages keep visitors, and search engines use page experience as one of many signals. It will not rescue thin content, but between two similarly relevant pages the faster, steadier one can have an edge, and slow pages lose users before they ever read a word.

Google's Core Web Vitals are three user-centred measurements of loading, interactivity and visual stability. This lesson explains what each one measures, how to read it, and what usually fixes it.

The three metrics

Metric Measures Good Needs improvement Poor
LCP, Largest Contentful Paint Loading: when the largest visible element (hero image, heading block) renders 2.5 s or less up to 4 s over 4 s
INP, Interaction to Next Paint Responsiveness: delay between a user action and the next frame, across the whole visit 200 ms or less up to 500 ms over 500 ms
CLS, Cumulative Layout Shift Visual stability: how much content jumps around 0.1 or less up to 0.25 over 0.25

A page "passes" when the 75th percentile of real visits meets the Good threshold for each metric. These thresholds are published by Google and can be revised, so check the current documentation before reporting them. INP replaced the older First Input Delay (FID) metric.

Core Web Vitals

LCP How fast the main content appears
INP How quickly the page reacts
CLS How stable the layout stays

Measured on real visitors, judged at the 75th percentile.

1 / 2

Lab data versus field data

  • Field data comes from real users (for example the Chrome User Experience Report, shown in PageSpeed Insights and Search Console). It reflects real devices and networks and is what counts for assessment.
  • Lab data comes from a controlled test (Lighthouse, WebPageTest). It is repeatable and great for debugging, but it is one device, one network.

Use field data to find which pages have a problem and lab data to find out why.

Improving LCP

LCP is usually an image or a block of text. Work through this order:

  1. Server response time. Cache pages, use a CDN, keep database work off the critical path.
  2. Do not lazy-load the LCP image. Lazy loading is for images below the fold; the hero should load eagerly, and can use fetchpriority="high".
  3. Right-size images. Serve modern formats (AVIF, WebP) and responsive srcset sizes.
  4. Remove render-blocking resources. Inline critical CSS, defer non-critical scripts.
Responsive, stable hero image

Improving INP

INP suffers when the main thread is busy. Typical causes are long JavaScript tasks, heavy third-party scripts (ads, chat widgets, tag managers) and expensive event handlers.

  • Ship less JavaScript and split bundles.
  • Break long tasks into smaller chunks, yielding to the browser between them.
  • Debounce expensive handlers and avoid forced layout reads and writes in loops.
  • Load third-party code after the page is usable, and audit what each script costs.
A long task blocks the page

Improving CLS

Layout shifts happen when something appears and pushes content: images without dimensions, ads and embeds injected late, banners, and web fonts that swap with a different size.

  • Always set width and height (or aspect-ratio) on images, video and iframes.
  • Reserve space for ads, embeds and cookie banners.
  • Insert new content below the viewport or in response to user action, not above existing content.
  • Use font-display: swap with a similar fallback font, and preload key fonts.

Other speed basics

  • Compression (Brotli or gzip) for text assets, caching headers for static files.
  • HTTP/2 or HTTP/3 and a CDN close to your visitors.
  • Minimize CSS and JavaScript, and remove unused code.
  • Preconnect to critical third-party origins.
  • Test on a mid-range phone over a slow connection, not only on your fast laptop.

Do not chase a perfect Lighthouse score. Aim for passing field data on your important templates, then spend remaining effort on content and links.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which Core Web Vital measures visual stability?

    Cumulative Layout Shift measures how much visible content moves unexpectedly.
  2. 2. What is the recommended Good threshold for LCP?

    An LCP of 2.5 s or less at the 75th percentile of visits is rated Good.
  3. 3. Why set width and height on images?

    Known dimensions let the browser allocate space before the image downloads.
  4. 4. Which data reflects real visitors?

    Field data is collected from real users on real devices and networks.

Summary

  • Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (stability).
  • Pass means the 75th percentile of field data is in the Good range for each.
  • Use field data to find problem pages and lab tools to debug them.
  • Optimize images, ship less JavaScript, reserve space and cache aggressively.
  • Speed supports good content; it does not replace it.

Next: Structured Data and Schema Markup