Skip to content
Createfirm

Core Web Vitals explained for business owners

Core Web Vitals are three Google measures of loading speed, responsiveness and visual stability. Learn the thresholds, how to check them and what to fix.

By the Createfirm teamPublished 7 min read

Illustration of Core Web Vitals: three gauge dials with gold needles in the good zone and a streak of light

Core Web Vitals are three measurements Google uses to describe how a web page feels to a real visitor: how fast the main content loads, how quickly the page responds when someone taps or clicks, and how stable the layout is. Google’s ranking systems use them, though relevant content still matters most.

What are the three Core Web Vitals?

Google’s Web Vitals overview on web.dev defines three metrics. Each has a threshold for a good experience.

Metric What it measures In plain terms Good Needs improvement Poor
Largest Contentful Paint (LCP) Loading performance How long until the main content appears 2.5 seconds or less Up to 4 seconds Over 4 seconds
Interaction to Next Paint (INP) Responsiveness How long the page takes to react to a tap, click or key press 200 milliseconds or less Up to 500 milliseconds Over 500 milliseconds
Cumulative Layout Shift (CLS) Visual stability How much the content jumps around while loading 0.1 or less Up to 0.25 Over 0.25

The needs improvement and poor ranges come from Google’s PageSpeed Insights documentation.

Two details explain a lot of confusion:

  • The score is based on real visitors. Google assesses each metric at the 75th percentile of page loads, split between mobile and desktop. Put simply, at least three out of four visits need to hit the good mark.
  • The set can change. web.dev says the metrics will evolve over time, though stable metrics will not change more than once per year.

How do you check your Core Web Vitals?

You can check them yourself with two free Google tools.

PageSpeed Insights, for one page at a time

  1. Open PageSpeed Insights and enter a page address. Start with your home page and your busiest landing page.
  2. Look at the top section first. This is field data: real visitor measurements from the Chrome User Experience Report, covering the previous 28 days.
  3. Check the Core Web Vitals assessment. It passes when LCP, INP and CLS are all in the good range at the 75th percentile.
  4. Switch between the mobile and desktop tabs, since each is measured separately.
  5. Scroll down to the lab section. This is a single simulated test with a performance score, where 90 or above is rated good. Use it for the list of suggested fixes.

If your page does not have enough visitors, PageSpeed Insights falls back to data for your whole site. If the whole site lacks enough data, it shows no real visitor data at all. That is normal for small sites, and the lab test is still useful.

Field data and lab data often disagree. The field data is what reflects your actual visitors. The lab test also cannot measure INP, because no real person is clicking.

Search Console, for the whole site

The Core Web Vitals report in Search Console uses the same real visitor data. It groups similar pages together and labels each group Good, Need improvement or Poor, based on its worst metric.

After your developer ships a fix, you can start a validation in the report. Google then monitors the pages for 28 days and marks the issue fixed if it does not reappear.

What causes poor scores, and what fixes them?

Here are the causes Google’s own guides highlight, in plain terms. Hand this list to whoever maintains your site.

Slow loading (LCP)

LCP tracks the largest image, text block or video visible on screen as the page loads. Google’s guide to optimizing LCP points to these common problems:

  • A slow server response. Redirect chains and pages that cannot be cached add delay before anything loads. A content delivery network (CDN), which serves your site from locations near your visitors, helps.
  • The main image is found late. If the hero image is added by a script, set as a CSS background, or lazy-loaded, the browser starts fetching it late. The guide says never to lazy-load the LCP image, and to mark it as high priority.
  • Oversized images. Use modern image formats, compress them, and serve a size that fits the screen.
  • Code that blocks rendering. Large style sheets and scripts in the page head can hold up the first paint. Defer what is not needed right away.

Slow response to taps and clicks (INP)

Google’s guide to optimizing INP explains that a slow interaction comes from the browser being busy with other work.

  • Too much script running at startup. While scripts load and run, the page cannot respond to a tap. Trim what runs on page load.
  • Heavy work tied to a click. When a button triggers a long chain of work, the screen update waits. Developers can show the visual change first and do the rest afterward.
  • Very large pages. Pages with a huge number of elements take longer to redraw after each interaction. Simpler page structures respond faster.

Content that jumps around (CLS)

Google’s guide to optimizing CLS lists these common causes:

  • Images and videos without dimensions. Always set width and height so the browser reserves the space.
  • Ads, embeds and iframes. Reserve space for them before they load.
  • Content inserted after loading. Banners and notices that appear at the top push everything down. Reserve the space, or place late content lower on the page.
  • Web fonts. When a custom font swaps in for a fallback, text can reflow. Developers can preload key fonts and pick a closely matched fallback.

If you are planning a rebuild, write these targets into the project requirements. Our website redesign checklist covers what else to protect during a migration.

Do Core Web Vitals affect Google rankings?

Yes, with limits that Google spells out. This is worth reading closely, because the topic is often overstated.

Google’s page experience documentation says, “Core Web Vitals are used by our ranking systems.” It recommends that site owners achieve good Core Web Vitals for success with Search and for a good user experience generally.

The same page adds several cautions:

  • Good results in Search Console’s Core Web Vitals report or in third-party tools do not guarantee that your pages will rank at the top of Google Search results.
  • There is no single page experience signal.
  • Other page experience aspects beyond Core Web Vitals do not directly help a site rank higher.
  • Google Search always seeks to show the most relevant content, even if the page experience is below par. Where many pages offer helpful content, a great page experience can contribute to success.
  • Chasing a perfect score only for SEO reasons may not be the best use of your time.

Google’s Core Web Vitals page for Search frames it the same way: good Core Web Vitals, along with other page experience aspects, align with what its core ranking systems seek to reward.

The fair reading for a business owner is this. Speed will not rescue thin content, and a slightly slow page with the best answer can still rank. When you and a competitor both have strong content, a faster, steadier page can help. It also helps every visitor, whatever route brought them to your site.

Where should you start?

  1. Run your top five pages through PageSpeed Insights on mobile.
  2. Note which of the three metrics fails, if any. Fix the failing one first.
  3. Ask your developer or agency for a short plan tied to the causes above.
  4. Recheck after 28 days, since field data covers a rolling 28-day window.
  5. Aim for good, not perfect.

Page speed is one part of being found. For the rest, see our guides to schema markup for local businesses and getting cited in AI search results.

The short version

Core Web Vitals measure loading (LCP, 2.5 seconds or less), responsiveness (INP, 200 milliseconds or less) and visual stability (CLS, 0.1 or less) for real visitors. Check them in PageSpeed Insights and Search Console. Google’s ranking systems use them, and Google is equally clear that relevant content comes first and good scores guarantee nothing.

Frequently asked questions

What are the three Core Web Vitals?
They are Largest Contentful Paint (LCP), which measures loading performance, Interaction to Next Paint (INP), which measures how quickly a page responds to clicks, taps and key presses, and Cumulative Layout Shift (CLS), which measures visual stability. Google documents them on web.dev and in Search Central, and reports them in PageSpeed Insights and Search Console.
What is a good Core Web Vitals score?
According to web.dev, a good LCP is 2.5 seconds or less, a good INP is 200 milliseconds or less, and a good CLS is 0.1 or less. Google assesses these at the 75th percentile of page loads, split by mobile and desktop. PageSpeed Insights shows a pass when all three are in the good range.
Are Core Web Vitals a Google ranking factor?
Google's page experience documentation says Core Web Vitals are used by its ranking systems and recommends achieving good scores. The same page says good results do not guarantee top rankings, and that Google always seeks to show the most relevant content even if page experience is below par. Treat them as one contributor, not a shortcut.
How do I check my website's Core Web Vitals?
Enter a page address in PageSpeed Insights to see real visitor data from the previous 28 days alongside a lab test. For a site-wide view, open the Core Web Vitals report in Google Search Console, which groups similar pages and labels each group Good, Need improvement or Poor. Low-traffic sites may show no real visitor data.

Sources

Every fact in this article was checked against these pages on November 14, 2026.

  1. Web Vitals, web.dev (Google)
  2. Understanding Core Web Vitals and Google search results, Google Search Central
  3. Understanding page experience in Google Search results, Google Search Central
  4. About PageSpeed Insights, Google for Developers
  5. Core Web Vitals report, Google Search Console Help
  6. Optimize Largest Contentful Paint, web.dev (Google)
  7. Optimize Interaction to Next Paint, web.dev (Google)
  8. Optimize Cumulative Layout Shift, web.dev (Google)

Keep reading