Core Web Vitals are three metrics Google uses to describe real user experience: how fast the main content appears, how quickly the page reacts, and how stable the layout is. They are part of Google's page experience signals, and they map closely to whether visitors stay or leave. Your hosting mostly affects the first one, but it sets the floor for all of them.
Before you start
- Your site URL and access to Google Search Console.
- Know the difference between lab data (a single test run) and field data (real Chrome users over 28 days).
The three Core Web Vitals
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | When the biggest image or text block renders | 2.5 s or less | over 4 s |
| INP (Interaction to Next Paint) | Delay between a click or tap and the next visual update | 200 ms or less | over 500 ms |
| CLS (Cumulative Layout Shift) | How much content jumps around while loading | 0.1 or less | over 0.25 |
A page passes when at least 75% of visits meet the good threshold for all three. INP replaced First Input Delay (FID) in March 2024.
How web hosting affects Core Web Vitals
The key server metric is Time to First Byte (TTFB): the time until the browser receives the first byte of HTML. Nothing can render before that, so slow TTFB eats directly into your LCP budget. Aim for a TTFB under about 0.8 seconds for real users. Hosting factors that drive TTFB:
- Web server and caching: LiteSpeed with LSCache can serve cached WordPress pages without running PHP at all.
- Storage: NVMe drives make database queries and file reads faster than SATA SSD or HDD.
- CPU and resource limits: an overloaded server or a plan hitting its CPU or entry-process limits queues requests.
- Distance: choose a server location near your visitors, or use a CDN.
- Protocols: HTTP/2 and HTTP/3 reduce connection overhead, especially on mobile.
MdmHost hosting runs LiteSpeed on NVMe storage with CloudLinux, in Germany, the USA and Singapore, which covers the server side of this list.
How to measure your Core Web Vitals
- Open Search Console → Experience → Core Web Vitals for field data grouped by URL pattern.
- Run PageSpeed Insights on key pages. The top section is field data (CrUX); the lower section is a Lighthouse lab test with suggestions.
- Check TTFB in the browser: DevTools → Network, click the document request and read Waiting for server response.
How to improve each metric
Improve LCP
- Enable full-page caching and check that cached pages show a cache-hit header.
- Compress and resize the hero image, serve WebP or AVIF, and do not lazy-load the LCP image.
- Remove render-blocking CSS and JavaScript, and preload the main font or hero image.
Improve INP
- Reduce heavy JavaScript: page builders, chat widgets, tracking tags.
- Defer non-essential scripts and break up long tasks.
Improve CLS
- Set width and height on images, videos and iframes.
- Reserve space for ads and embeds, and use
font-display: swapwith similar fallback fonts.
Note: Field data updates over a rolling 28-day window, so Search Console needs weeks to reflect improvements.
Troubleshooting
- Good lab score, poor field data: real visitors use slower phones and networks, or visit uncached pages (logged in, cart, search).
- High TTFB only sometimes: the cache is being purged too often, or the account is hitting resource limits during traffic peaks.
Frequently asked questions
Are Core Web Vitals a big ranking factor?
They are one signal among many. Relevance and content quality matter more, but passing the vitals helps when pages are otherwise similar, and it improves conversions.
Can better hosting alone fix Core Web Vitals?
It fixes server delay, which mainly helps LCP. INP and CLS depend mostly on your theme, scripts and images.
Does a CDN improve Core Web Vitals?
Yes, for visitors far from your server, by serving static files and sometimes cached HTML from nearby locations.