liveBook · Manning

Perceived performance

As explained in Fast by Default

Perceived performance is the speed and responsiveness of a digital experience as experienced by users, which can differ from its technical loading time.

Perceived performance is how fast and responsive a digital experience feels to users, rather than how quickly it finishes loading. Users notice when meaningful content appears, interactions respond, and the layout remains stable. section 3.2.1

Evaluate perceived performance through the moments users depend on:

  • Content appearance: measure when the largest visible element, such as a headline or hero image, appears with Largest Contentful Paint (LCP). section 3.2.1
  • Interaction feedback: measure the delay between an action and visible feedback with Interaction to Next Paint (INP). section 3.2.1
  • Visual stability: measure unexpected movement during loading with Cumulative Layout Shift (CLS). section 3.2.1
  • Prioritize individual metrics that predict user satisfaction instead of optimizing only an aggregate performance score. section 3.2.1

E-commerce product page

Users need the product image and price quickly, an immediately responsive “Add to cart” button, and a stable page. A page can finish loading sooner yet feel slower if these moments are delayed. 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 Core Web Vitals table to compare each metric with the user-visible behavior it represents. section 3.2.1

How Fast by Default covers it

How deep it goes
Explains the distinction from technical loading and applies LCP, INP, and CLS, but does not detail optimization implementation.
Examples
Uses an e-commerce product page with product imagery, pricing, cart interaction, and loading-induced layout shifts.
What it assumes
Assumes a web-application context and teaches the difference between technical load completion and user-perceived responsiveness.
What you can do after
Evaluate user-facing web performance with LCP, INP, CLS, Chrome DevTools, PageSpeed Insights, or monitoring dashboards.
How it connects
Connects web performance with Core Web Vitals, user experience, real user monitoring, and browser developer tools.

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.