Core Web Vitals for business sites: what actually moves the numbers
Hosting, caching strategy and image handling account for most real-world gains. Here is the order we work through them.
Performance work has a long tail of micro-optimisations that feel productive and change almost nothing. On a typical business site, three things account for the majority of the improvement — and they are usually the three nobody has touched.
1. Fix the server response first
Every millisecond before the first byte is a millisecond every other optimisation has to overcome. Undersized hosting, a database on the far side of the world, or an uncached page rebuilt on every request will cap your score no matter how neat the frontend is.
Measure time to first byte from the regions your customers are actually in, not from wherever your testing tool defaults to.
2. Cache with intent
Full-page caching for anonymous visitors is the single biggest lever on a content or brochure site. Store pages at the edge, set sensible expiry, and define precisely which routes must bypass the cache — cart, account, checkout, admin.
The common failure is caching everything and then punching so many holes in it that nothing is cached in practice. Decide the exceptions deliberately and keep the list short.
3. Treat images as a budget
Images are usually the largest content payload and the most common cause of layout shift. Serve modern formats, generate sizes that match the layout rather than the original upload, always declare width and height, and lazy-load anything below the fold while eagerly loading the hero.
Then, and only then, the frontend detail
Once hosting, caching and images are handled, the remaining wins come from removing unused scripts, deferring third-party tags, and cutting render-blocking CSS. Third-party tags deserve particular scrutiny: analytics, chat widgets and marketing pixels are often the slowest thing on an otherwise fast page, and each one needs an owner who can justify it.
Work top-down: server response, caching, images, then frontend detail. Teams that reverse that order spend weeks shaving kilobytes off a page that still waits a second for its first byte.
Talk to our team
