Glossary

Core Web Vitals

Core Web Vitals are three Google measures of how a page feels to use. Largest Contentful Paint is how fast the main content loads and Interaction to Next Paint is how fast the page reacts to a click. Cumulative Layout Shift is how much things jump around while it loads.

What are Core Web Vitals?

Core Web Vitals are three measures Google uses to judge how a page feels to a real visitor. They cover loading speed, how fast the page responds and whether things jump around while it loads:

  • Largest Contentful Paint (LCP): How long it takes for the biggest piece of content on screen, usually a headline, image or video, to appear. Good is 2.5 seconds or less.
  • Interaction to Next Paint (INP): How long the page takes to respond visibly after a click, tap or key press. Good is 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in March 2024.
  • Cumulative Layout Shift (CLS): How much the layout moves while the page loads. Good is 0.1 or less.

Here's what that looks like on a real B2B page. Let's say a buyer opens your pricing page on their phone between meetings. The plan cards take four seconds to show up, which is a poor LCP. A cookie banner then loads at the top and pushes everything down, so they tap "Enterprise" when they meant "Team", which is a CLS problem. Then the plan toggle freezes for half a second while a chat widget loads, which shows up as a slow INP.

Google judges each measure at the 75th percentile of real visits. So a page passes only when at least three out of four visits get a good experience.

Why Core Web Vitals matter for B2B SaaS

Google's ranking systems use Core Web Vitals, but they're a small factor next to relevance and content quality. A fast page with a weak answer won't beat a slow page with a great one. Where they matter is when two pages are close, and on the pages where buyers decide.

Most sites still have work to do. In the HTTP Archive's Web Almanac 2025, 48% of mobile sites passed all three Core Web Vitals, up from 36% in 2023. That's real progress, and it still means about half of mobile sites fail at least one.

Here's why I check them on every B2B site I audit:

  • Decision pages carry the most scripts: Pricing, demo and product pages are where teams add chat widgets, scheduling embeds, video and tracking tags. Those are the pages where a slow load costs you demo requests.
  • Buyers check you on their phones: A champion often shares your page in Slack, and a colleague opens it on mobile. If it's slow or jumpy there, that's their first impression.
  • They point to deeper problems: Poor scores often come from a bloated tag manager or a page builder that loads everything on every page. Fixing those also helps with technical SEO and crawling.

How to improve Core Web Vitals

Start with the templates your most important pages use, since one fix to a template fixes every page built on it. Here's my process:

  • Find the failing page groups: Open the Core Web Vitals report in Google Search Console. It groups similar URLs, so you can see whether the problem sits on blog posts, product pages or the whole site.
  • Speed up the main content: For LCP, compress and resize the hero image, serve it in a modern format like WebP or AVIF and don't lazy load it. Swap autoplay hero videos for a still image with a play button.
  • Hold space for everything that loads late: For CLS, set width and height on images and embeds, and reserve space for cookie banners, announcement bars and scheduling widgets. Load web fonts in a way that doesn't reflow the text.
  • Cut and delay third-party scripts: For INP, list every script in your tag manager and remove the ones nobody uses. Load chat widgets and heatmap tools after the page is ready, or only on the pages that need them.
  • Recheck after every release: Run PageSpeed Insights on your key templates after each site update. A new tracking tag or page builder block can undo months of work in one deploy.

A Core Web Vitals example

Here's a hypothetical example for an HR software company whose pricing page fails on mobile:

MeasureBeforeWhat the team changedAfter
LCP4.1 secondsReplaced the autoplay hero video with a compressed image2.2 seconds
CLS0.28Reserved space for the cookie banner and set sizes on logo images0.04
INP340 millisecondsLoaded the chat widget and heatmap script after the page finished loading170 milliseconds

All three moved into the good range. The team then watched demo requests from the page in GA4 for the next two months, since that's the number the fix was really for.

Twilio Segment, the customer data platform, is a useful real example of technical SEO done well at scale, and we broke down what it does in our Segment technical SEO post. If you're planning a redesign, our website revamp SEO checklist covers what to test before launch.

How to measure Core Web Vitals

Use field data from real visitors to judge pass or fail, and lab data to find the cause. Here's where to look:

  • Search Console Core Web Vitals report: Shows which URL groups are good, need improvement or poor, split by mobile and desktop. It's the view closest to what Google uses.
  • PageSpeed Insights: Shows field data from the Chrome UX Report when a page has enough visits, plus a lab test with a list of what slows the page down. Many low traffic B2B pages show lab data only.
  • Chrome DevTools: The Performance panel shows which script blocks a click or which element shifts. Use it when the other tools tell you what's wrong but not why.
  • Conversion rate on fixed pages: Compare the conversion rate of each fixed page in GA4 before and after the change. Speed only matters if it helps buyers act.

Common Core Web Vitals mistakes

  • Aiming for a perfect lab score: A PageSpeed score of 100 on a lab test isn't the goal. Passing the field data at the 75th percentile is what counts.
  • Testing only on desktop: Most failures show up on mid-range phones over mobile networks. Check the mobile report first.
  • Fixing one page at a time: If the problem is in a template, fixing pages one by one never ends. Find the shared cause and fix it once.
  • Expecting a ranking jump: Good scores help at the margins. If a page doesn't rank, look at the content and search intent before you spend another sprint on speed.
  • Adding scripts without an owner: Every tag in your tag manager should have a person who knows why it's there. Review the list every quarter and remove what nobody claims.

Here's a first step you can take today. Open the Core Web Vitals report in Search Console and check the mobile tab. Which group of pages is marked poor?

Read more

FAQ

What are the three Core Web Vitals?

Largest Contentful Paint (LCP) measures how fast the main content loads, and Interaction to Next Paint (INP) measures how fast the page responds to clicks and taps. Cumulative Layout Shift (CLS) measures how much the layout moves while it loads.

What are good Core Web Vitals scores?

Google counts a page as good when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less. Each one is judged at the 75th percentile of real visits.

Are Core Web Vitals a ranking factor?

Yes, Google's ranking systems use them, but they carry far less weight than relevance and content quality. Fixing them rarely moves a page from page three to page one, though a slow page can lose out against a similar, faster one.

Why does PageSpeed Insights say there's not enough data?

Field data comes from the Chrome UX Report, which needs a minimum number of real Chrome visits. Many B2B pages get too few, so you see lab data only, and Search Console may group them with similar pages.

Want your brand in the answers your buyers read?

We build the Organic Content Engine for B2B SaaS teams: search content that ranks and gets cited in AI answers, plus LinkedIn thought leadership from your founders.