Core Web Vitals are Google’s way of measuring how a page feels to the visitor, and the three metrics can be improved on a WordPress site with concrete, checkable steps. It is not about a single speed number, but about three different things: how quickly the largest content appears, how quickly the page responds to a click, and how much the layout jumps while it loads. This guide explains what LCP, INP and CLS actually measure, what you should measure them with, and which changes tend to move the needle. No invented results, just the method and the common causes.
The three metrics, in plain terms
- LCP (Largest Contentful Paint) measures how long it takes before the largest element in view appears, often a hero image or a heading. It is the visitor’s sense of “the page has loaded now”.
- INP (Interaction to Next Paint) measures how quickly the page responds when the visitor clicks, taps or types. INP replaced the older FID and looks at response time across the whole visit, not just the first click.
- CLS (Cumulative Layout Shift) measures how much content moves while the page loads. It is the annoying experience of reaching for a button and it jumps away because an image or ad loaded in above it.
Measure on field data, not just in the lab
A common mistake is to run only a lab test and assume it reflects reality. Lab tools like Lighthouse run under controlled conditions and are good for debugging, but Google ranks on field data: how real visitors actually experience the page, seen over time. Here is how to measure it right:
- Look at field data in Google Search Console under the Core Web Vitals report. That is the data Google actually uses.
- Use PageSpeed Insights to see both field and lab data for a single address.
- Measure several page types: the front page, an article, a product page. They have different problems.
- Measure on mobile, because that is usually where the metrics are worst and where Google weighs heaviest.
Core Web Vitals reward real experience, not tricks. A page that loads its most important content early, responds instantly to a click and does not jump around passes the metrics almost on its own. The goal is a page that feels calm to use.
Improving LCP
LCP is mostly about how quickly the server responds and how heavy the largest element is. The common fixes:
- Turn on page caching, so HTML is served straight away without PHP starting. That lowers time to first byte, which LCP builds on.
- Optimise the hero image: right size, modern compression, and load it early rather than deferring it.
- Do not lazy-load the very element that is the LCP. Lazy loading is good below the fold, but not for the first thing you see.
Improving INP
INP is about JavaScript. When the page is busy running scripts it cannot respond to clicks, and that shows up in the metric. Look at how much JavaScript your plugins and theme load, and remove what you do not use. Heavy third-party scripts, such as chat widgets and tracking codes, are common culprits. The less script that runs, the faster the page responds.
Improving CLS
CLS is often the easiest to fix, because the causes are few and concrete. Always set a width and height on images and video, so the browser reserves space before they load. Reserve room for ads and embedded content. Load fonts so the text does not jump when the real typeface swaps out the fallback. Once every element knows how big it will be before it loads, the page stops jumping.
The server matters for all three
A fast server helps LCP directly through lower TTFB, and gives INP room by not forcing the visitor’s browser to wait on slow responses. Page caching, a modern PHP version and a server that is not overloaded are therefore part of the foundation for good scores. On Celestio, full page caching with rules you control is part of the platform, together with per-site PHP. If you want to understand the caching layers each in turn, we have written a walkthrough of caching, and if you are wondering why the site is slow in the first place, there is a guide on exactly that.
Most of these changes you can do yourself, one metric at a time. If you want to sit on a platform where the server foundation is already in place, read more about our platform or start an account and move the site across.