Skip to content

Page Experience Update: Core Web Vitals Guide & Audit Checklist

Google's Page Experience update brought Core Web Vitals into the SEO conversation.

This guide explains what the metrics measure, the benchmarks to aim for, and the tools that help you audit and improve your site. It is based on a 2021 expert podcast episode, so treat the benchmarks as a dated reference and check current Google documentation before making decisions.

What the Page Experience update changed

Page Experience is a set of signals Google uses to assess how users experience a web page. The update made Core Web Vitals a more prominent part of that assessment. The original episode was recorded shortly before the 2021 rollout, when the exact ranking impact was still unknown. That uncertainty is a useful reminder: Page Experience is one input among many, not a single switch that guarantees rankings.

The update covers three Core Web Vitals metrics plus existing experience signals. For local businesses and agencies, the practical task is to measure the metrics, identify pages that fall outside the recommended range, and fix the causes.

The three Core Web Vitals metrics

Core Web Vitals focus on loading, interactivity, and visual stability. Each metric has a recommended threshold. The thresholds below are the ones commonly cited around the 2021 update; confirm the current values in Google's documentation because they can change.

  • Largest Contentful Paint (LCP): measures how long the largest visible element takes to load. A good target is 2.5 seconds or less.
  • First Input Delay (FID): measures the delay before the page responds to a user's first interaction. A good target is 100 milliseconds or less. FID has since been supplemented by Interaction to Next Paint (INP) in Google's current guidance; check which metric applies to your reporting period.
  • Cumulative Layout Shift (CLS): measures unexpected movement of page content. A good target is 0.1 or less.

These are field metrics: they describe real user experiences, not just a lab test. A page can pass a lab audit and still fail in the field, so use both views.

How to read the benchmarks

The benchmark numbers are thresholds, not scores. A page at 2.6 seconds LCP is not catastrophically slow, but it is outside the recommended range and worth investigating. Use the 75th percentile of real-user data where available, because averages can hide slow experiences for a meaningful share of visitors.

A simple decision rule:

  1. If a metric is within the good range, monitor it and move on.
  2. If it is in the needs-improvement range, identify the largest contributor before changing code.
  3. If it is poor, prioritise the fix and re-measure after deployment.

Do not optimise every metric at once. Fix the one with the biggest gap and the clearest cause first.

Tools for finding Page Experience issues

The original episode recommended a small set of tools. Each serves a different purpose, so use them together rather than treating any single score as definitive.

  • Google PageSpeed Insights gives both lab and field data for a URL. Start here to see whether real users are experiencing problems.
  • Lighthouse for Google Chrome runs a lab audit in the browser. It is useful for diagnosing causes and testing changes before deployment.
  • Screaming Frog can crawl a site and surface Core Web Vitals data at scale. Use it to find patterns across templates rather than checking pages one by one.
  • Sitebulb is another crawler that can include performance and experience checks in a site audit.
  • thruuu is a SERP analyser that can help you compare page experience across competing results.
  • Seosly's Google Page Experience Audit Checklist and Template provides a structured checklist for a manual review.

A sensible workflow is: field data first (PageSpeed Insights), then a lab diagnosis (Lighthouse), then a site-wide crawl (Screaming Frog or Sitebulb) to find repeatable template issues.

Audit input and output map

When you run an audit, keep track of what you put in and what you get back. A simple map:

  • Input: URL, device type (mobile or desktop), and reporting period.
  • Output: LCP, FID/INP, and CLS values, plus a pass/fail status against the benchmark.
  • Diagnostic output: the specific element or request responsible for a poor metric.
  • Action: the change made, the date, and the re-measurement result.

Recording this information makes it easier to show progress and to avoid re-fixing the same template issue on every page.

What might come next

The original discussion considered Google's motivation for the update and what might follow. Page Experience signals are likely to keep evolving, and metric definitions can change. Build a habit of checking Google's current documentation rather than relying on a single 2021 snapshot. The durable skill is the audit loop: measure, diagnose, fix, and re-measure.

Frequently asked questions

What is Google's Page Experience update?

It is a set of signals Google uses to assess how users experience a page, with Core Web Vitals as a central part. The 2021 rollout made these metrics more prominent in SEO discussions, but ranking impact was not fully known at the time.

What are the Core Web Vitals benchmarks?

The commonly cited 2021 thresholds were LCP of 2.5 seconds or less, FID of 100 milliseconds or less, and CLS of 0.1 or less. Check Google's current documentation because metrics and thresholds can change.

Which tools should I use to audit Page Experience?

Start with Google PageSpeed Insights for field data, use Lighthouse for a lab diagnosis, and use a crawler such as Screaming Frog or Sitebulb to find template-level issues across a site. A structured checklist helps with manual review.

Why do lab and field results differ?

Lab tools test a page under controlled conditions. Field data reflects real users on different devices, networks, and locations. A page can pass a lab audit and still show poor field metrics, so use both views.