Core Web Vitals are a business metric, not an engineering one
Treating performance as a technical concern is why it never gets prioritised. Attach a revenue number to it and the work gets scheduled.
Key takeaways
- Performance loses prioritisation arguments because it is reported as a score, not as revenue.
- Largest Contentful Paint is the vital most tightly coupled to commercial outcomes.
- The engineering is unglamorous: ship less JavaScript and keep the request path short.
Why should a business care about Core Web Vitals?
Because they map to revenue. Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift describe how quickly a page becomes usable and how stable it feels, and all three correlate with whether a visitor completes a purchase. Reported as a score they get ignored; reported as conversion they get funded.
The framing problem
Performance work gets deprioritised because it is presented as a technical score. Nobody outside engineering has an intuition for what a 2.8 second Largest Contentful Paint costs.
Reframe it. On a retail site we worked on, cutting LCP from 3.4s to 1.2s moved mobile conversion 11%. That is the number that gets the work scheduled, and it is the same work either way.
How to translate each vital into a business question
| Vital | What it measures | Business question it answers |
|---|---|---|
| LCP | Time to the main content rendering | How many visitors leave before they see anything |
| INP | Responsiveness to interaction | How many abandon a form or filter mid-task |
| CLS | Visual stability while loading | How many mis-tap and lose trust in the page |
The engineering is boring, and that is fine
The technical work is usually unglamorous: ship less JavaScript, stop blocking render on third-party tags, serve images at the size they are displayed, and move what can be static off the request path.
None of it requires a rewrite. On most sites, four days of disciplined removal beats four weeks of clever optimisation, because the biggest wins are in the things that should not have been on the critical path at all.
Instrument it where the money is
Lab scores are a debugging tool. Field data segmented by device, connection and — critically — by whether the session converted is what turns performance into a business conversation.
Once a dashboard shows LCP at the 75th percentile next to conversion rate for the same cohort, performance stops competing with features and starts being one.
FAQFAQ
Frequently asked questions
About the author
Tom builds the front end: rendering strategy, performance budgets and accessible interfaces that hold up under real network conditions. He writes about treating Core Web Vitals as a revenue metric rather than a lint rule.
- Core Web Vitals
- Next.js and React
- Web accessibility
- Frontend architecture
