- Core Web Vitals are a direct Google ranking factor.
- LCP (Largest Contentful Paint) should be under 2.5 seconds.
- INP (Interaction to Next Paint) has replaced FID as the primary interactivity metric.
- Server response time (TTFB) is the foundation of good Core Web Vitals.
What Are Core Web Vitals?
Core Web Vitals are a set of specific metrics that Google considers important for a webpage's overall user experience. They measure loading performance, interactivity, and visual stability.
A Ranking Signal Since 2021
Since June 2021, these metrics have been a ranking signal in Google Search. Sites that meet the recommended thresholds have a measurable advantage in search results.
Largest Contentful Paint (LCP)
Google recommends an LCP of 2.5 seconds or less for a "Good" rating.
For WordPress sites, LCP is heavily influenced by server response time, render-blocking resources, and image optimisation. A slow hosting environment or unoptimised images can push LCP well beyond acceptable thresholds. Before touching your theme or plugins, measure where the time actually goes: if the server takes over a second to send the first byte, no front-end optimisation will save you.
Interaction to Next Paint (INP)
Google has transitioned to INP (Interaction to Next Paint) as its interactivity metric, replacing the older FID. INP measures how quickly your page responds to a real interaction throughout the whole visit, not just the first one.
JavaScript is the Enemy of INP
Heavy JavaScript execution is the primary cause of poor INP scores. WordPress sites loaded with plugins often have significant JavaScript overhead that blocks the main thread.
Start With the Server: TTFB
Time to First Byte is the quiet foundation under every Core Web Vitals score. It's the time between the browser asking for a page and the first byte of the response arriving — and everything else stacks on top of it.
On oversold shared hosting, TTFB swings wildly because your PHP workers are shared with hundreds of other sites. The same page can respond in 300ms at 6am and 2 seconds at lunchtime, and no caching plugin can fix that variance.
This is where isolation matters. On G7Cloud every site runs in its own dedicated container with its own database, so your response time doesn't depend on what anyone else's site is doing. The dashboard's resource metrics (kept for 90 days) let you see exactly when CPU or memory pressure is the real culprit, instead of guessing.
About G7Cloud Engineering
Articles written by the engineers who build and run G7Cloud — UK managed hosting and the AI Website Builder. We write about what we operate every day: containers, backups, databases, and the small-business websites that run on them.
More about G7Cloud →