Core Web Vitals and site speed
Core Web Vitals measure real visitors' loading, responsiveness and visual stability. Learn the thresholds, where the data comes from, and the fixes that matter most.
- Time
- 22 min
- Level
- intermediate
- Reviewed
- 5 November 2026
After this lesson you can
- Explain LCP, INP and CLS and their "good" thresholds.
- Tell field data from lab data, and know which one Google uses.
- Prioritise the most common performance fixes.
Core Web Vitals are three metrics that describe how a page feels to real visitors. Google's ranking systems use them, and they also affect conversions, often more than rankings.
The three metrics
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP, Largest Contentful Paint | When the main content (usually a hero image or heading) has loaded | ≤ 2.5 s | > 4 s |
| INP, Interaction to Next Paint | How quickly the page responds to taps, clicks and key presses | ≤ 200 ms | > 500 ms |
| CLS, Cumulative Layout Shift | How much the layout jumps while loading | ≤ 0.1 | > 0.25 |
Field data and lab data
- Field data comes from real Chrome users through the Chrome UX Report (CrUX), over a rolling 28 days. The Search Console Core Web Vitals report and the top of PageSpeed Insights use it. Pages with too little traffic have no field data of their own, so Search Console may fall back to grouped or origin-level data, or show nothing.
- Lab data comes from a simulated load in Lighthouse, on one simulated device and network. It varies from run to run. Use it to debug, not to judge.
The Search Console report groups similar URLs together, and a group's status is its worst metric.
Where speed matters for ranking
The fixes that matter most
LCP (loading)
- Do not lazy-load the main above-the-fold image. Consider
fetchpriority="high"on it. - Serve images at the size they are displayed, in WebP or AVIF.
- Reduce server response time with caching, a closer server or a CDN, and fewer slow database queries.
- Remove render-blocking CSS and JavaScript where possible.
INP (responsiveness)
- Reduce heavy JavaScript: unused libraries, large third-party scripts, chat widgets and tag managers loading everything.
- Break long tasks into smaller ones, and defer non-essential work.
- Be careful with scripts that run on every interaction.
CLS (stability)
- Set
widthandheightoraspect-ratioon images, videos and embeds. - Reserve space for ads, cookie banners and dynamic content, or show them without pushing content down.
- Load web fonts in a way that avoids large layout jumps.
Platform notes
- PrestaShop: enable the built-in CCC options (combine, compress and cache) in Advanced Parameters, then Performance, and test the result, because some modules break. Disable unused modules, and check that image sizes match the theme.
- WordPress / WooCommerce: use a caching plugin, and audit heavy plugins and page builders, which often cause poor INP.
- Shopify: theme choice and installed apps make the biggest difference. Remove apps you do not use, because many inject scripts.
Practice
Read the lesson, pass the quiz and do the exercise to complete it.
Knowledge check
5 questions. Get at least 4 right to pass.
Exercise: Measure and diagnose two templates
Run PageSpeed Insights on your home page and one other important template, such as a product, service or article page, on mobile. Record the field data (if available) and the lab results. For each failing or weak metric, write down the main cause PageSpeed Insights points to, and one concrete fix. Check the Core Web Vitals report in Search Console too.
Deliverable: A table per template with LCP, INP and CLS (field and lab), the main cause of each weak metric, and the planned fix. Real problems go to the Issues tab.
Sources
Checked against these sources on 5 November 2026. Next review by 5 February 2027.
- Web Vitals (web.dev (Google Chrome team), official)
- Interaction to Next Paint is now a stable Core Web Vital, replacing First Input Delay (web.dev (Google Chrome team), official)
- Core Web Vitals report (Search Console Help, official)
- About PageSpeed Insights (Google for Developers, official)
- Understanding page experience in Google Search results (Google Search Central, official)