Playbook · Speed and SEO

Updated

What are Core Web Vitals, and how do you pass them?

Core Web Vitals are three Google metrics for how a page feels to real visitors: loading (LCP), responsiveness (INP) and visual stability (CLS). You pass when at least 75% of page loads are good: LCP within 2.5 seconds, INP of 200 milliseconds or less, and CLS of 0.1 or less.

Good Core Web Vitals: LCP within 2.5 seconds, INP of 200 ms or less, CLS of 0.1 or less, measured at the 75th percentile of page loads, on mobile and desktop separately.
Source: web.dev, updated 31 Oct 2024

From my work

The storefront of The Merchant Engine scores about 100 on Lighthouse. It took several hours of trial and error, and asset size made the biggest difference. Now Lighthouse tests ship with it, so every store built on it is checked out of the box.

The three Core Web Vitals

  • Largest Contentful Paint (LCP): when the largest image, text block or video in the viewport is rendered. Good is 2.5 seconds or less, poor is over 4 seconds.
  • Interaction to Next Paint (INP): how fast the page responds to clicks, taps and key presses during the whole visit. Good is 200 ms or less, poor is over 500 ms.
  • Cumulative Layout Shift (CLS): how much the page jumps around unexpectedly while it loads and while you use it. Good is 0.1 or less, poor is over 0.25. It is the button that moves just as you go to tap it.

INP replaced FID in March 2024

On 12 March 2024, Interaction to Next Paint replaced First Input Delay as a Core Web Vital. FID only measured the delay before the first interaction, which was a generous exam. INP looks at every interaction on the page and reports the slowest, ignoring outliers. A page that passed FID can still fail INP.

Field data decides, lab data debugs

Field data comes from real Chrome users, through the Chrome UX Report, over a rolling 28 days. Lab data, like a Lighthouse run, loads the page once on one device and one network. Use field data to decide what to fix, and lab data to find the cause and test the fix before you ship it. After a fix, the field numbers take weeks to move, so there is no point refreshing the report every morning.

How to pass each one

Start with the metric your field data says fails, on the templates that bring in money.

  • Failing LCP: shrink the largest element, usually the hero image, and serve it at the size it is shown in a modern format. Load it early and never lazy-load it. Render the main content on the server so it does not wait for JavaScript. Asset size is the fix that has made the biggest difference in my work.
  • Failing INP: break up long JavaScript tasks, do less work inside click and input handlers, and cut third-party scripts, which compete with your own code for the main thread.
  • Failing CLS: give images, embeds and ads a fixed width and height or aspect ratio, and do not insert banners or notices above content that is already on screen, however urgent the announcement.

Core Web Vitals and rankings

Google says Core Web Vitals are used by its ranking systems. It also says good scores do not guarantee a top position, and that it will show the most relevant page even when its page experience is poor. Fix them because slow pages lose visitors, and treat any ranking gain as a bonus.

Read next

Sources

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.