payless.host
Core Web Vitals: Which Ones Your Host Can Fix
Updated Nov 22, 2026
What Core Web Vitals measure
Core Web Vitals are three measurements Google uses to judge how a page feels to use: how fast the main content loads (LCP), how quickly the page responds when you click something (INP), and whether elements jump around as the page loads (CLS). Your hosting can fix the first two. It cannot fix the third.
Check what your scores are now
Go to PageSpeed Insights and enter your site's URL. The tool will test your page and show three scores, each marked pass or fail. If LCP and INP both pass, your hosting is not the problem. If one or both fail, continue.
Write down the numbers. You will need them to confirm whether a change worked.
LCP: Largest Contentful Paint
This measures how long the biggest visible element takes to load — usually an image or a block of text. A passing score is 2.5 seconds or less. A slow server is the most common cause of a slow LCP.
Step 1: Check server response time
PageSpeed Insights breaks LCP into stages. Look for "Time to First Byte" (TTFB). If it is over 600 milliseconds, the server is taking too long to respond. Shared hosting on an overloaded server will show a TTFB above one second.
If TTFB is the problem, you need faster hosting or a content delivery network. Upgrading within the same provider sometimes helps; moving to a provider with better infrastructure helps more reliably.
Step 2: Confirm the fix
After moving or upgrading, test the same page again. TTFB should drop by half or more. If LCP improved but still fails, the server was part of the problem but not all of it — check image sizes next.
INP: Interaction to Next Paint
This measures how long the page takes to respond when you click, tap, or type. A passing score is 200 milliseconds or less. A slow INP usually comes from JavaScript running on the page, but an underpowered server can make it worse.
Step 1: Identify the delay
PageSpeed Insights will list the scripts causing the delay. If the delay is small — under 300 milliseconds — and your hosting is basic shared hosting, the server may be holding back a page that would otherwise pass.
If the delay is large — over 500 milliseconds — the problem is almost certainly in the code, not the hosting. Upgrading your server will not fix it.
Step 2: Test on a faster server
If you are on shared hosting and INP is close to the 200-millisecond threshold, a VPS or managed WordPress plan may bring it under. The difference will be measurable but modest — expect 50 to 100 milliseconds, not 500.
Test again after upgrading. If INP drops below 200, the server was the bottleneck. If it stays above 300, the code is.
CLS: Cumulative Layout Shift
This measures how much elements move around as the page loads. Your hosting cannot fix this. CLS is caused by images without dimensions, ads that push content down, or fonts that load late. The fix is in the code, not the server.
What can go wrong
You upgrade and nothing changes. You fixed the wrong thing. A slow LCP caused by a 5MB image will stay slow on any server. Go back to PageSpeed Insights and check what it identifies as the largest element. If it is an image, compress it first.
Scores vary between tests. PageSpeed Insights tests from different locations and network conditions. Run three tests and take the median. A score that flips between pass and fail is a sign the page is close — a small improvement will likely push it over.
TTFB is fast but LCP still fails. The server responded quickly, but something else is holding up the content. Check for render-blocking CSS or JavaScript. These are code problems, not hosting problems.
When hosting is not the answer
If TTFB is under 600 milliseconds and INP is under 200, your hosting is adequate. Further improvements will come from optimising images, reducing JavaScript, or fixing layout shifts — work that happens in the code, not on the server.
