Core Web Vitals are the three performance metrics Google uses to measure how real visitors experience your site — and since 2021, they have been a direct Google ranking signal. A WordPress site with all three in the "good" zone loads fast, feels responsive, and ranks better than slower equivalents. A site failing one or more loses ground to competitors. The good news: on a LiteSpeed-powered host like smartxhosting.uk, passing all three thresholds is genuinely achievable with a few targeted changes. This guide covers what the metrics are, how to measure them, and exactly what to fix to pass each one.
What Core Web Vitals are · The three metrics explained · How to measure your scores · Improving LCP — loading speed · Improving INP — responsiveness · Improving CLS — visual stability · WordPress-specific optimisation tips · The testing workflow · smartxhosting.uk and Core Web Vitals · Frequently asked questions
Core Web Vitals are three metrics defined by Google that measure real-user experience of your site:
Since 2021, Google uses these as ranking signals. A slow, unstable page loses ground to faster competitors even if the content is identical. For UK SMEs competing for organic search traffic, Core Web Vitals are a free performance channel you cannot afford to ignore.
Google evaluates Core Web Vitals based on field data — actual Chrome users visiting your site. To pass, you need "good" scores on at least 75% of real visits over a rolling 28-day window.
| Metric | Good threshold | What it measures |
|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5 s | How quickly the largest visible element (hero image, main heading) finishes loading |
| INP (Interaction to Next Paint) | < 200 ms | How quickly the page responds when a visitor clicks, taps or presses a key |
| CLS (Cumulative Layout Shift) | < 0.1 | How much the layout shifts unexpectedly during load |
INP replaced First Input Delay (FID) as of March 2024 — it is a stricter metric measuring the worst interaction latency during the entire visit.
Visit pagespeed.web.dev, enter your URL. Provides both field data (real Chrome users, when available) and lab data (simulated test). Field data at the top shows your actual pass/fail status. Lab data below offers specific recommendations.
Test your homepage and most-visited pages. Scores differ dramatically per page — a fast homepage does not guarantee a fast category archive.
If your site is connected to Search Console, Experience > Core Web Vitals. Groups URLs into Good / Needs Improvement / Poor separately for mobile and desktop. Authoritative — this is how Google actually evaluates you over a rolling 28-day period.
Open your site in Chrome, F12, Lighthouse tab. Run in Mobile mode for most relevant results. Performance score out of 100 plus actionable diagnostics. Ideal for testing changes before deploying.
For ongoing monitoring, services like Cloudflare Web Analytics, SpeedCurve or the free CrUX dashboard expose real-user metrics over time. More useful long-term than one-off PageSpeed tests.
LCP is how long before the largest visible element (hero image, main heading, featured image) finishes loading. On most WordPress pages it is a hero image or a featured image at the top of a post.
<link rel="preload"> tag for the hero image in the <head>.fetchpriority="high" to the image element.LiteSpeed Cache on smartxhosting.uk serves pre-built HTML pages without executing PHP or querying the database on every visit. Time to First Byte (TTFB) drops from 500–1500 ms to under 200 ms. This alone often fixes LCP.
Redis stores frequently used database queries in memory. Further reduces TTFB, particularly for WooCommerce product pages and other query-heavy content.
Analytics, chat widgets, social buttons do not need to load before main content is visible. Use the defer attribute or LiteSpeed Cache's JS Defer option.
LiteSpeed Cache's Critical CSS feature extracts above-the-fold CSS, inlines it into the page head, and loads the rest asynchronously. Dramatic LCP improvement on some sites.
No optimisation compensates for a slow server. smartxhosting.uk uses NVMe SSD, LiteSpeed Web Server and Redis — a stack purpose-built for fast TTFB.
INP measures the slowest interaction (click, tap, keypress) during the entire page visit. A single slow response spoils the score.
Heavy JavaScript is the primary INP killer. Every script competes for the browser's main thread. When a long-running script runs, user clicks wait until it finishes.
Audit in Chrome DevTools > Performance tab. Look for tasks longer than 50 ms. Investigate which plugins or scripts cause them.
Analytics, live chat, social embeds and ads frequently block the main thread. Use defer/async, or delay until user interaction (plugins like WP Rocket or Flying Scripts do this automatically).
Some plugins inject large JS bundles on every page even when their functionality is only needed on specific pages. Audit active plugins; deactivate unused; consider lightweight alternatives (e.g. Fluent Forms instead of heavier form builders).
Scripts that read layout (e.g. getBoundingClientRect()) and write styles in rapid succession cause layout thrashing. Rare in typical WordPress sites but shows up in custom theme code.
Pages with 1,500+ DOM nodes stress the browser's main thread more. Simplify page builder output, consolidate unnecessary wrappers, reduce deep nesting.
CLS measures unexpected layout shifts during page load. A visitor about to click a button; an image finishes loading above it; the button moves; the visitor clicks the wrong thing. That is a layout shift.
Always set width and height attributes (or CSS aspect-ratio). The browser reserves space for the image before it loads, preventing shift. WordPress does this automatically for images inserted via the Block Editor.
Google AdSense, YouTube embeds, social media widgets often load asynchronously and push content down when they arrive. Use CSS min-height or aspect-ratio containers to reserve space.
Fonts loaded after text renders can cause visible shift as text re-flows. Use font-display: swap for minimal impact; font-display: optional is stricter but may leave users seeing system fonts if the web font is slow. Self-host fonts locally (WordPress 6.1+ does this for Google Fonts added via Global Styles).
A cookie banner that appears after 2 seconds and pushes the whole page down is a CLS disaster. Either render it server-side so it is present from the start, or use CSS to overlay rather than push content.
"Related posts" widgets, ad slots, comment sections that are injected via JavaScript post-load can all cause shift. Render server-side where possible.
Twenty Twenty-Five, GeneratePress, Kadence, Blocksy, Astra are all lightweight. Avoid bloated multipurpose themes that bundle every feature; their weight hurts LCP even on fast hosting.
Every active plugin is code loading on every page. A site with 40 plugins usually has significantly worse Core Web Vitals than a functionally equivalent site with 10. Remove plugins you do not actively use.
Set your workflow to compress and convert images to WebP before uploading, or let LiteSpeed Cache + QUIC.cloud handle it automatically. Never upload a 5 MB phone photo directly.
Performance improvements ship regularly. Keeping everything current means better Core Web Vitals over time without effort on your part.
Both are enabled on smartxhosting.uk by default. They multiplex requests and reduce latency on modern connections — particularly helpful on mobile.
Old post revisions, auto-drafts, expired transients slow database queries over time. LiteSpeed Cache's database optimisation tab cleans them up; see our database optimisation guide.
A repeatable process for improving Core Web Vitals:
Server infrastructure choices on smartxhosting.uk directly support good Core Web Vitals:
On top of this, the Plesk WordPress Toolkit's staging and Smart Update features let you test performance changes without risk to production.
Are Core Web Vitals really a ranking factor?
Yes, confirmed by Google since 2021. The weight is small relative to content quality and backlinks, but they tip the scales in competitive niches and affect whether Chrome's "slow" badge appears next to your URL.
What if I have no field data in PageSpeed Insights?
Field data is only available once your site has enough Chrome traffic (typically a few hundred visits per day for the URL in question). For smaller sites, rely on lab data and Search Console's Core Web Vitals report (which aggregates data across URL groups).
How long do improvements take to reflect in rankings?
Lab data (PageSpeed Insights synthetic test) updates immediately. Field data (actual user experience) updates over a rolling 28-day window in Search Console. Ranking impacts typically follow field data improvements by 1–3 weeks.
Is it worth passing Core Web Vitals if my content is poor?
Great content on a slow site outranks poor content on a fast site. Fast content on a slow site outranks fast content on a poor site. Ideally: good content, good performance. Performance alone will not rescue a weak site.
My lab score is 100 but field data says "Needs Improvement". Why?
Lab tests run from a specific location with a specific simulated network. Real users are on varied devices, networks, and around the world. Lab = best case; field = reality. Both matter.
Which is more important, mobile or desktop Core Web Vitals?
Mobile. Google uses mobile-first indexing, and most UK web traffic is mobile. Focus mobile scores first.
Will switching to a new theme help?
Often yes. Switching from a heavy multipurpose theme to a lightweight block theme can improve Core Web Vitals by 20–50% without any other changes. Test on staging before switching on production.
Can I pass Core Web Vitals without a caching plugin?
Theoretically yes; practically very hard. Even on fast hosting, dynamic PHP generation per request typically overruns the LCP budget. LiteSpeed Cache or equivalent is a near-requirement.
Does WordPress core itself need optimising?
WordPress 6.x is much more performance-conscious than earlier versions. Still, core rarely the bottleneck — themes and plugins are. Keep WordPress up to date and focus optimisation effort on themes and plugins.
How much performance improvement can I realistically expect?
Typical WordPress site on decent hosting with LiteSpeed Cache, lightweight theme, optimised images: LCP 1.0–2.0 s; INP 50–150 ms; CLS 0.05–0.08. All comfortably in the green. Starting from an unoptimised site, 50–80% improvement in LCP is common.
Launch your WordPress site on smartxhosting.uk
UK hosting with the Plesk WordPress Toolkit, LiteSpeed Cache, Redis object caching, free Let’s Encrypt SSL, free CDN and daily backups — from £2/month.
View WordPress hosting plans →