Google has made page experience part of how it ranks pages, and the headline metrics are the Core Web Vitals. They sound technical, but each one measures something a real visitor feels: how fast the page shows up, how quickly it responds, and whether things jump around while it loads.
Here's what each Vital means in plain English, the numbers you're aiming for, and how to measure and improve them without paying for anything.
The three Core Web Vitals
Largest Contentful Paint (LCP) — how long until the biggest thing on screen (usually the hero image or headline) has loaded. It's your 'is this page fast?' metric. Aim for under 2.5 seconds.
Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. A laggy button feels broken even on a 'fast' page. Aim for under 200 milliseconds.
Cumulative Layout Shift (CLS) — how much the page jumps around as it loads. You've felt this: you go to tap a link and an ad pushes it down. Aim for under 0.1.
How to measure yours
Run your page through the free Page Speed Test. It reports all three Vitals — from real Chrome users where available, plus a lab test — for both mobile and desktop, and lists the specific fixes that will help most.
Page Speed TestMeasure Core Web Vitals and Lighthouse scores.Test mobile first. Most traffic is mobile, Google indexes mobile-first, and phones are where slow sites hurt most.
How to improve LCP (loading)
- Compress your hero and above-the-fold images — they're the usual culprit. Use the Image Compressor.
- Serve modern formats like WebP; convert with the Image Converter.
- Enable gzip or Brotli compression and good caching — check what your server sends with the HTTP Header Checker.
- Remove render-blocking scripts and unused CSS so content paints sooner.
How to improve CLS (visual stability)
- Set width and height on every image so the browser reserves space. Find images missing dimensions with the Image SEO Checker.
- Reserve space for ads and embeds instead of letting them push content down.
- Avoid inserting content above what the user is already reading.
How to improve INP (responsiveness)
- Break up long JavaScript tasks so the main thread isn't blocked when someone interacts.
- Defer or lazy-load non-critical scripts.
- Keep third-party scripts (chat widgets, trackers) to a minimum — each one competes for the main thread.
After each change, re-test with the Page Speed Test and watch the trend. Small, measured improvements add up.