liveBook · Manning

Core Web Vitals

As explained in Fast by Default

Core Web Vitals are Google's standardized set of user-centric web performance metrics for loading, visual stability, and interaction responsiveness.

Core Web Vitals measure web performance through three user-facing questions: when the main content appears, how quickly interactions respond, and whether the page stays visually stable. They connect technical performance with user satisfaction, search visibility, and abandonment. section 2.2.1 section 3.2.1

The metrics describe distinct failure patterns:

  • Largest Contentful Paint (LCP) measures the time until the largest visible content appears, such as a hero image or main headline. section 3.2.1
  • Interaction to Next Paint (INP) measures the delay between a user action and visible feedback, such as an “Add to cart” response. section 3.2.1
  • Cumulative Layout Shift (CLS) measures unexpected movement while content loads, such as an advertisement pushing article text downward. section 3.2.1

Measure individual metrics rather than relying on an overall performance score. Use field data to discover real user problems, lab data to debug them, and field data again to confirm impact. Set specific goals before optimization and embed them in the definition of done. section 3.2.1 section 3.6

E-commerce product page

A useful performance check asks whether the product image and price appear quickly, whether the “Add to cart” control responds promptly, and whether late-loading content moves the page. These correspond to LCP, INP, and CLS, respectively. section 3.2.1

Table 3.3 Core Web Vitals for web applications
Metric
Measures
Example
Largest Contentful Paint (LCP)
Time until the largest visible content appears
A hero image or main headline finishes loading
Interaction to Next Paint (INP)
Delay between user interaction and visual feedback
User clicks “Add to cart” and sees the button respond
Cumulative Layout Shift (CLS)
How much the page layout shifts during loading
An ad loads late and pushes the article text down

Use the comparison table to map each metric to its user-visible behavior and representative failure. section 3.2.1

How Fast by Default covers it

How deep it goes
Defines LCP, INP, and CLS with concrete examples and measurement guidance, but does not detail metric-specific remediation techniques.
Examples
Uses product-page content appearance, Add to cart feedback, layout shifts, Chrome DevTools captures, and Search Console reports.
What you can do after
Apply via Chrome DevTools, PageSpeed Insights, and field monitoring to set, debug, and validate user-centered web performance goals.
How it connects
Links loading performance with SEO, user satisfaction, field data, lab data, PageSpeed Insights, and Google Search Console.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.