Core Web Vitals Explained for People Who Are Not Performance Engineers
By ABD Web Tools Editorial · 2026-02-23 · 8 min read
Core Web Vitals sound like an engineering concern, but the causes of poor scores are usually decisions made outside engineering: a video background, a font chosen for its personality, a chat widget, three analytics scripts. Understanding what the three metrics measure lets you have that conversation with evidence instead of instinct.
LCP: how quickly the main thing appears
Largest Contentful Paint measures when the biggest visible element — usually a hero image, video poster or headline block — finishes rendering. Good is under 2.5 seconds for most visitors.
The usual culprits are an enormous hero image, a slow server response, and render-blocking CSS or fonts loaded before anything can paint.
INP: how quickly the page answers you
Interaction to Next Paint measures the delay between a tap or click and the visible response, across the whole visit rather than just the first interaction. Good is under 200 milliseconds.
Failures come from long JavaScript tasks blocking the main thread: heavy hydration, oversized third-party bundles, or expensive work done synchronously in an event handler.
Advertisement
CLS: how much the page jumps around
Cumulative Layout Shift measures unexpected movement of visible content. Good is under 0.1. Almost every failure traces to images without dimensions, ads or embeds inserted after load, or web fonts swapping in at a different size.
The fixes ranked by return on effort
In our experience, five changes resolve the majority of failing pages:
- Compress and correctly size the hero image, and preload it.
- Set explicit width and height on every image and embed slot.
- Load third-party scripts after interaction or defer them entirely.
- Self-host fonts, subset them, and use font-display: swap with a matched fallback metric.
- Split large JavaScript bundles so the initial route ships less code.
Lab data versus field data
A synthetic audit on a fast laptop tells you what could happen; field data from real visitors tells you what does happen. When they disagree, trust the field data and look for the device class or region dragging the distribution down. Averages hide this; look at the 75th percentile.
How much does it matter for rankings?
Page experience is a tiebreaker rather than a primary factor. Fixing vitals will not rescue a page that does not answer the query, but between two comparable pages it can decide which one wins — and it reliably improves conversion regardless of search.
A sensible monitoring cadence
Check the field report monthly and after every release that touches the layout, the font stack or third-party tags. Set a budget — for example, no page ships over 1 MB of images — and enforce it at review time rather than after launch.
Frequently asked questions
Does a perfect performance score guarantee good vitals?
No. Lab scores are simulations. Real users on mid-range phones and slow networks produce the numbers that count.
Which metric should I fix first?
Whichever one is failing for the most visitors. If several fail, CLS is usually the cheapest to fix and the most visibly annoying to users.
Do vitals apply to pages behind a login?
They are measured wherever real users go, but search ranking only considers publicly indexable pages. Fix authenticated pages for the user experience, not for search.
Can a content management system be the bottleneck?
Often, yes — through bundled themes, plugin scripts and unoptimised media. Audit what the theme loads before blaming the platform itself.
Advertisement
