Your SEO provider or web developer mentioned “Core Web Vitals” and you’re not sure whether it matters or what to do about it. Here’s the direct answer: Core Web Vitals are three specific page speed and interaction metrics that Google uses as a ranking signal. Poor scores have measurable effects on your search rankings, your bounce rate, and your conversions. This guide explains each metric in plain terms and tells you exactly what poor scores cost a business like yours.
What Core Web Vitals Are — and Why Google Cares
Core Web Vitals are a set of measurements Google introduced in 2021 to quantify real user experience on web pages. The idea: instead of ranking pages purely on content and links, Google wanted to reward pages that were actually fast and usable. The “Page Experience” update made CWV an official ranking factor in May 2021.
The History: Why Google Made This a Ranking Factor
Before Core Web Vitals, Google had speed signals (PageSpeed, mobile-friendliness) but no standardized, user-focused measurement framework. CWV changed that by anchoring the measurement to what real users experience — not what a developer sees in a controlled lab test. Google collects CWV data directly from Chrome browsers visiting real pages (called “field data”), which makes the metrics inherently tied to actual user behavior.
Field Data vs. Lab Data: What Google Actually Measures
This distinction matters. Lab data (from tools like PageSpeed Insights or Lighthouse) simulates a page load under controlled conditions. Field data comes from the Chrome User Experience Report (CrUX) — real Chrome users visiting your real site. Google’s ranking algorithm uses field data, not lab data. Your Lighthouse score is a diagnostic tool; your CrUX field data is what Google actually evaluates for rankings. Both are useful, but they measure different things.
The Three Core Web Vitals Metrics Explained
Each metric measures a different dimension of page performance. Each has a specific threshold. Each connects to a specific business consequence.
LCP — Largest Contentful Paint
What it measures: How long it takes for the largest visible element on the page to appear on screen. This is usually a hero image, a large heading, or a video thumbnail. LCP is the primary indicator of perceived page load speed — how fast the page “feels” to a user.
Google’s threshold: Under 2.5 seconds = “Good.” 2.5–4 seconds = “Needs Improvement.” Above 4 seconds = “Poor.”
Common causes of failure: Unoptimized hero images (2MB+ JPEGs), render-blocking JavaScript from page builders, slow server response times (TTFB above 600ms), and third-party scripts loaded in the document head.
Business impact: LCP above 4 seconds correlates with a 123% higher bounce rate than LCP under 1 second (Google research). Users don’t wait. They leave. Every second above 2.5 seconds is costing you visitors who would otherwise have seen your content.
CLS — Cumulative Layout Shift
What it measures: Visual stability — how much the page layout shifts unexpectedly as it loads. A CLS event happens when an element loads late and pushes other content down, sideways, or off-screen. You’ve experienced this: you’re about to click a link and an ad loads above it, pushing the link down, and you click the wrong thing. That’s a CLS event.
Google’s threshold: Under 0.1 = “Good.” 0.1–0.25 = “Needs Improvement.” Above 0.25 = “Poor.”
Common causes of failure: Images without declared width and height dimensions (the page doesn’t know how much space to reserve), fonts that load late and cause text reflow, banner ads that inject into the layout after initial load, and dynamically loaded content that pushes existing elements.
Business impact: High CLS causes users to misclick, lose their place in content, and experience the site as unstable and low-quality. It’s the metric that directly correlates to “this site feels broken” user reactions. CLS above 0.25 is often the difference between a site that feels professional and one that feels like it was built on a free platform.
INP — Interaction to Next Paint
What it measures: How quickly the page responds to user interactions — clicks, taps, keyboard inputs. INP measures the worst-case response time across all interactions during a page visit. It replaced FID (First Input Delay) in March 2024.
Google’s threshold: Under 200ms = “Good.” 200–500ms = “Needs Improvement.” Above 500ms = “Poor.”
Why it replaced FID: FID measured only the time to process the first interaction on a page. INP measures responsiveness across all interactions — it’s a harder threshold to pass. A page that responds quickly to the first click but lags on the third or fourth is now captured by INP, where it wasn’t by FID.
Common causes of failure: Heavy JavaScript execution (particularly from page builders like Elementor or Divi), third-party scripts (chat widgets, ad systems, analytics), and long tasks that block the browser’s main thread from responding to user input.
Business impact: A page with poor INP feels sluggish and unresponsive. Users interpret this as a broken or low-quality site. For e-commerce, poor INP on product pages or cart interactions directly costs conversions — a user who taps “Add to Cart” and waits 600ms for feedback often abandons.
What Happens to Your Business When CWV Scores Are Poor
The connection between CWV scores and business outcomes is not theoretical. It’s documented.
The Ranking Impact
Core Web Vitals act as a tiebreaker in Google’s algorithm. When two pages have similar content quality and backlink profiles, the faster page with passing CWV scores wins. This effect is most visible in competitive local markets — “dentist in Austin,” “web designer in Miami,” “accountant in Chicago” — where dozens of pages are competing for the same query. Position differences of 2–5 spots separate the businesses on page 1 from those on page 2. CWV can determine which side of that line you’re on.
Sites with “Good” CWV scores across all three metrics rank 24% higher on average than equivalent content with “Poor” scores, according to Searchmetrics CWV analysis.
The Bounce Rate Impact
53% of mobile sessions are abandoned if a page takes more than 3 seconds to load (Google). LCP above 4 seconds correlates with a 123% higher bounce rate than LCP under 1 second. If your site’s mobile LCP is 4.5 seconds and 60% of your visitors are on mobile, you’re losing more than half your potential audience before they’ve read a single word.
The Conversion Rate Impact
Every 100ms improvement in load time improves conversion rates by approximately 1%, based on the Google and Deloitte mobile shopping study. That sounds small — 1% per 100ms — but it compounds. A site that improves its LCP from 4 seconds to 2 seconds has saved 2,000ms. At 1% per 100ms, that’s a 20% improvement in conversion rate from load time alone. If your site currently converts at 2% (20 leads per 1,000 visitors), a 4-second LCP improvement to 2 seconds could move that to 2.4% — 4 additional leads per 1,000 visitors at zero additional marketing cost.
How to Check Your Core Web Vitals Score
You can do this right now, in under 5 minutes.
Go to PageSpeed Insights, enter your URL, and click “Analyze.” Select the Mobile tab (this is what Google uses for ranking). You’ll see two sections: Field Data (real user experience — this is the ranking signal) and Lab Data (Lighthouse simulation — this is the diagnostic tool).
In Field Data, each metric shows a color: green = “Good,” orange = “Needs Improvement,” red = “Poor.” A fully green result is passing Core Web Vitals. Any orange or red metric is a failure.
A score below 50 on the Lighthouse Performance scale is “Poor.” 50–89 is “Needs Improvement.” 90+ is “Good.” Most page-builder-based WordPress sites score 35–60 on mobile without optimization. Hand-coded WordPress sites built for performance score 85–98.
For a combined SEO and speed diagnostic with more context than PageSpeed Insights alone, run a check at honest.designodin.com.
What Causes Poor Core Web Vitals Scores
Most CWV failures on WordPress sites trace to a small set of root causes.
Page Builders: Structural Overhead
Elementor-based WordPress sites average CWV “Needs Improvement” or “Poor” on mobile in 60–70% of cases. The cause is architectural: page builders load their complete JavaScript and CSS library on every page, regardless of which widgets are used. That overhead adds 200–400ms of render-blocking delay and 300–600ms of Total Blocking Time, which directly causes LCP and INP failures. This is covered in depth in our page builder performance breakdown.
Unoptimized Images and Fonts
A 3MB JPEG hero image on a mobile connection is a 3-second LCP problem on its own. WebP format at equivalent visual quality runs 700KB–1MB. Images should have declared dimensions in HTML (to prevent CLS), be compressed before upload, and load lazily if they’re below the fold. Custom fonts that load from Google Fonts or a type foundry add 200–400ms of font-swap delay if not preloaded correctly — causing both LCP delay and CLS events.
Third-Party Scripts
Every third-party script — Google Tag Manager, chat widgets, Facebook Pixel, HubSpot tracking, heatmap tools — adds load time and increases TBT. A single misconfigured Google Tag Manager container that loads synchronously can add 300–600ms of Total Blocking Time alone. Audit your third-party script load with WebPageTest’s waterfall view and remove anything that doesn’t have a measurable business justification.
Slow Hosting
Time to First Byte (TTFB) — how long the server takes to respond — is the foundation everything else is built on. Google’s TTFB threshold is under 800ms for “Good.” Shared hosting typically returns TTFB of 400–800ms. Managed WordPress hosting (Kinsta, WP Engine) returns TTFB of 80–200ms. No amount of frontend optimization can compensate for a slow server — if the server is slow, the page is slow.
How to Improve Core Web Vitals on a WordPress Site
The full ranked-by-impact guide is in our WordPress page speed optimization post. The short version, in order of impact:
- Switch to managed WordPress hosting if you’re on shared hosting
- Install a caching plugin (WP Rocket) and configure page caching, browser caching, and GZIP compression
- Convert all images to WebP format and compress before uploading
- Declare image dimensions in HTML (fixes CLS from images)
- Defer non-critical JavaScript (reduces TBT and improves INP)
- Audit and remove unused third-party scripts
If your site is built on a page builder and Lighthouse on mobile is below 50 after full optimization, the structural overhead is the ceiling. A hand-coded rebuild removes the floor problem entirely and produces LCP under 2 seconds and Lighthouse 90+ before any optimization layer is applied.
Frequently Asked Questions
Do Core Web Vitals directly affect Google rankings?
Yes, as an official ranking signal since May 2021. They function primarily as a tiebreaker — two pages with similar content quality and backlinks will be differentiated by CWV performance. In competitive queries, this tiebreaker determines page 1 vs. page 2 positioning. CWV is not the dominant ranking factor (content quality and authority still matter more), but it is a real, measurable one.
What are the three Core Web Vitals metrics?
LCP (Largest Contentful Paint) — measures how fast the main content loads, threshold: under 2.5s. CLS (Cumulative Layout Shift) — measures visual stability, threshold: under 0.1. INP (Interaction to Next Paint) — measures responsiveness to user interactions, threshold: under 200ms. All three must pass for Google to classify a page as having a “Good” page experience.
What is a good Core Web Vitals score?
“Good” means all three metrics are in the green range: LCP under 2.5s, CLS under 0.1, INP under 200ms — all measured in field data (real user experience). For Lighthouse, 90+ on mobile is the target. Many hand-coded WordPress sites built for performance score 90–98. Most page builder sites score 35–65 before optimization.
How do I check my website’s Core Web Vitals?
Go to pagespeed.web.dev, enter your URL, and check the Mobile tab. The Field Data section shows your real CWV scores from Chrome users. Green = passing, orange = needs improvement, red = failing. If your site is new or low-traffic, there may not be enough field data yet — the Lab Data (Lighthouse) scores will be shown as an approximation.
What is the difference between LCP and INP?
LCP measures load performance — how fast the page content appears. INP measures interactivity — how fast the page responds to user actions like clicks and taps. LCP is about the initial load experience; INP is about the ongoing interaction experience. INP replaced FID (First Input Delay) in March 2024 because FID only measured the first interaction, while INP measures all interactions across the page visit.
Can a WordPress site pass Core Web Vitals with a page builder?
Some can, particularly on desktop. On mobile, passing all three CWV metrics with Elementor or Divi requires aggressive optimization: managed hosting, caching plugin, WebP images, CSS purging, CDN. Even with all of that, approximately 30–40% of optimized page builder sites still fail at least one metric on mobile (typically LCP or INP). Hand-coded WordPress sites pass all three metrics at much higher rates as a baseline.
How much does a poor Core Web Vitals score hurt my search traffic?
The ranking impact is most visible in competitive queries where multiple pages are fighting for page 1. A site that fails CWV (particularly LCP above 4s) while competing against faster sites with similar content quality can expect to rank 2–5 positions lower. The traffic difference between position 3 and position 8 on a query with 500 monthly searches is approximately 200 organic visits per month — at a 2% conversion rate, that’s 4 leads per month, or 48 leads per year, that the faster site captures and yours doesn’t.
Core Web Vitals are a scoring system for something that was always true: fast, stable, responsive websites perform better. Google made it measurable and tied it to rankings. If your scores are poor and your site runs on a page builder, the hand-coded WordPress builds we deliver are built to 90+ Lighthouse on mobile as a baseline — not an optimization target, a floor. See our fixed-price packages to understand what that investment looks like.