Core Web Vitals: why speed is a design decision
Performance isn't only an engineering concern. How fast a page feels is part of how good it feels — and how well it ranks.
Kumar Gaurav
Founder
Core Web Vitals are Google's measures of how a page actually feels to use: how fast the main content loads, how quickly it responds to input, and how much the layout jumps around. They affect both search ranking and the human impression of quality — which makes speed a design decision, not just an engineering one.
What are the Core Web Vitals?
Three measures, in plain terms: Largest Contentful Paint (how soon the main thing appears), Interaction to Next Paint (how quickly the page answers a tap or click), and Cumulative Layout Shift (how much things move while loading). Each maps to a feeling: is it here yet, did it hear me, and did it hold still.
Why is speed a design problem?
Because many of the worst offenders are design choices.
- Huge unoptimised images and heavy fonts delay the first paint.
- Content that loads without reserved space makes the layout jump.
- Blocking scripts make the page look ready before it can respond.
- Every 'nice to have' widget adds weight someone pays for.
How fast is fast enough?
Fast enough that the delay never enters the user's awareness. The thresholds are useful targets, but the real bar is perception: the main content up quickly, input answered immediately, nothing shifting under the user's thumb.
How we use it
We treat performance as part of the design, budgeted from the start, not patched at the end — because a fast page is a feeling of quality you don't have to explain.
Let's build
Have something worth making well?
Tell us what you're working on. We'll come back with how we'd approach it — and whether we're the right studio for it.