Visibility

Site speed and Core Web Vitals: metrics, thresholds and fixes

Core Web Vitals measure loading speed (LCP), responsiveness (INP) and visual stability (CLS). A guide to the metrics, thresholds, ways of measuring and the most common fixes.

Updated

A slow website costs money. On mobile, a visitor only waits a moment before returning to the search results, and every extra second weakens conversion. That is why Google measures page experience with the Core Web Vitals metrics and uses them as part of how it ranks search results.

Speed does not maintain itself either. New images, plugins, tracking scripts and embeds gradually slow a site down. That is why monitoring speed belongs in regular maintenance. The importance of loading speed for user experience, conversions and search visibility is also discussed in eLuotsi's article How can you improve website loading speed? (in Finnish).

The three metrics

Metric What it measures Good Needs improvement Poor
LCP (Largest Contentful Paint) How quickly the largest content element in the viewport loads ≤ 2.5 s 2.5–4 s > 4 s
INP (Interaction to Next Paint) How quickly the page responds to clicks, taps and key presses ≤ 200 ms 200–500 ms > 500 ms
CLS (Cumulative Layout Shift) How much content shifts during loading ≤ 0.1 0.1–0.25 > 0.25

A page passes the assessment when all three metrics are at a good level for 75 per cent of visits. INP replaced the earlier FID metric in March 2024. INP is more demanding, because it takes into account all interactions during a visit, not just the first one.

Field data and lab data

  • Field data is collected from real Chrome users (the Chrome User Experience Report). It is shown in Search Console and PageSpeed Insights if the site has enough traffic. Google's assessment is based on field data.
  • Lab data comes from a single simulated page load, for example with Lighthouse. It is suitable for diagnosing problems and testing changes.

A small website does not always have enough field data. In that case a lab measurement is the best available estimate, and it should be run with a mobile profile.

Improving LCP

The LCP element is usually the main image on the home page or a large heading. The most common causes of a slow LCP and their fixes:

  • Slow server response (TTFB): page caching, a better server environment or a CDN. See choosing web hosting.
  • Large images: the right size, modern image formats (WebP, AVIF) and responsive images (srcset).
  • The main image loads too late: do not use lazy loading (loading="lazy") on the LCP image. Give it a high priority (fetchpriority="high").
  • Render-blocking files: unnecessary CSS and JavaScript files at the top of the page.
  • Web fonts: load only the fonts and weights you need, and use font-display: swap.

Improving INP

A poor INP is almost always caused by heavy JavaScript that ties up the browser's main thread:

  • Remove unnecessary third-party scripts: chats, tracking codes, ad tags and social media embeds.
  • Load the scripts you need deferred (defer) or only after interaction.
  • Avoid heavy page builders and sliders that load a large amount of code on every page.
  • After updates, check whether a plugin has started loading its scripts on all pages.

Improving CLS

Content jumping around during loading happens because the browser does not know the size of an element in advance:

  • Define the width and height (width, height) or aspect ratio for images and videos.
  • Reserve space for ads, embeds and cookie banners.
  • Avoid inserting content above existing content after the page has loaded.
  • Use font loading settings that minimise text reflow.

Speeding up a WordPress site

On WordPress sites, the biggest gains usually come from:

  1. An up-to-date PHP version. Newer versions are significantly faster. See WordPress maintenance.
  2. Page caching on the server or with a plugin.
  3. Image optimisation at upload.
  4. Removing plugins, especially those that load scripts on every page.
  5. A lightweight theme instead of a heavy multipurpose theme.
  6. Object caching (for example Redis) for dynamic sites and online shops.

Monitoring as part of maintenance

  • Monthly: the Core Web Vitals report in Search Console for mobile and desktop.
  • After updates: a PageSpeed Insights measurement of the home page and the most important page templates.
  • When introducing new tools: measure before and after adding a chat, analytics, a cookie tool or an embed to the site.

Speed is also part of technical SEO and affects how well a page works as a source for AI search.

Frequently asked questions

Does site speed affect Google rankings?

Yes, page experience and Core Web Vitals are part of Google's ranking signals. Google stresses, however, that relevance of content matters more. Speed mainly makes the difference when content is otherwise evenly matched. Speed also has a direct effect on visitor behaviour and conversions.

Why does PageSpeed Insights show different results from Search Console?

PageSpeed Insights shows both a lab measurement that simulates a single page load and field data from real Chrome users, if there is enough data. Search Console only shows field data and groups similar pages together. The assessment is based on field data.

What is a good PageSpeed score?

A score of 90–100 is good, but it is a lab measurement on a single simulated device. What matters more is whether pages pass the Core Web Vitals assessment with real-user data.

Do cookie banners and analytics slow a site down?

They can, especially if there are several scripts and they load before the page content. Load third-party scripts deferred, remove unnecessary tracking tools and make sure the cookie banner does not shift the page content when it loads, because that worsens CLS.

Sources

  1. web.dev: Web Vitals
  2. web.dev: Interaction to Next Paint (INP)
  3. Google Search Central: Understanding page experience
  4. PageSpeed Insights
  5. eLuotsi: How can you improve website loading speed? (in Finnish)