Core Web Vitals for SaaS marketing sites
Written by Olayinka Olayokun·Published ·Updated ·Verified
Core Web Vitals for SaaS is the practice of monitoring and optimising real-user LCP, INP, and CLS — sourced from CrUX field data — on the marketing templates that actually drive ranking and revenue.
Summary and key takeaways
Google's CWV ranking signal uses CrUX field data — real Chrome users' LCP, INP, and CLS over a rolling 28 days. PageSpeed Insights' lab score is a diagnostic, not the signal. On a SaaS site, fix CWV on the home page, pricing page, and top three landing pages; ignore the blog posts that get under 50 visits a month. The thresholds: LCP <2.5s, INP <200ms, CLS <0.1.
- •Google's ranking signal is field data from CrUX, not the PageSpeed Insights lab score.
- •LCP threshold is 2.5s, INP threshold is 200ms, CLS threshold is 0.1 — all at the 75th percentile of real users.
- •CrUX is reported per origin and per URL when the URL has enough traffic; small SaaS sites usually have only origin-level data.
- •Fix CWV on the home page, pricing page, and top three landing pages; ignore low-traffic blog posts.
- •INP replaced FID in March 2024 — most SaaS sites that 'passed' FID now fail INP because INP measures all interactions, not just the first.
In plain English ·Core Web Vitals for SaaS marketing sites means measuring LCP, INP, and CLS from CrUX field data on the templates that drive ranking — home, pricing, comparison, feature, integration — and optimising those specifically. Lab scores diagnose; field data ranks.
How this compares
| Metric source | What it measures | When to use | Google ranks on this? |
|---|---|---|---|
| PageSpeed Insights lab | Single simulated load on a throttled device | Diagnosing why a page is slow | No |
| CrUX field data (28-day rolling) | Real Chrome users' actual experience | Confirming a page passes CWV | Yes |
| Search Console Core Web Vitals report | CrUX data grouped by URL pattern | Monitoring per-template health over time | Yes (this is the same CrUX data) |
Part of the Technical SEO for SaaS: The Founder's Checklist guide
Core Web Vitals for SaaS is the practice of monitoring and optimising real-user LCP, INP, and CLS — sourced from CrUX field data — on the marketing templates that actually drive ranking and revenue.
Most SaaS teams chase the wrong CWV number. PageSpeed Insights returns a single lab score that's easy to optimise toward but isn't what Google ranks on — and that gap is why teams can ship 'green' Lighthouse scores and still fail CWV in Search Console. The fix is to measure what Google measures: 28-day CrUX field data, at the 75th percentile, on the templates that actually drive ranking.
What this chapter covers: lcp, inp, cls, field data, 75th percentile.
Lab data is a diagnostic; field data is the signal
PageSpeed Insights reports two sets of numbers: the lab score (one simulated load) and the field data (real users over 28 days). Google ranks on the field data. The lab score is useful for diagnosing what's slow, never for proving a page passes.
PageSpeed Insights reports two sets of numbers: the lab score (one simulated load) and the field data (real users over 28 days). Google ranks on the field data. The lab score is useful for diagnosing what's slow, never for proving a page passes.
On a typical SaaS marketing page the lab and field numbers diverge: lab LCP shows 1.8s, field LCP shows 3.4s. The difference is usually a third-party script that doesn't fire in the lab environment but absolutely fires for real users.
Which pages to fix, in which order
Fix the home page, the pricing page, and the top three landing pages first. These five templates produce 80–95% of organic ranking signal on a typical B2B SaaS site, and they're the pages where a CWV tiebreaker actually matters.
Fix the home page, the pricing page, and the top three landing pages first. These five templates produce 80–95% of organic ranking signal on a typical B2B SaaS site, and they're the pages where a CWV tiebreaker actually matters.
Ignore CWV on blog posts under 50 visits per month. The traffic is too small to generate field data, the URL-level signal doesn't accumulate, and the engineering time produces no measurable rank lift.
INP is the new failure mode
INP replaced FID in March 2024 and is meaningfully harder to pass. FID measured only the first interaction; INP measures all of them. SaaS sites with heavy JavaScript bundles and DOM-mutating third-party scripts routinely passed FID and now fail INP.
INP replaced FID in March 2024 and is meaningfully harder to pass. FID measured only the first interaction; INP measures all of them. SaaS sites with heavy JavaScript bundles and DOM-mutating third-party scripts routinely passed FID and now fail INP.
The three highest-leverage INP fixes for SaaS: (1) code-split routes so the JS bundle is smaller per page, (2) defer non-critical third-party scripts past first interaction, (3) avoid controlled inputs (React state on every keystroke) in any form longer than three fields.
Reading the Search Console Core Web Vitals report
Search Console → Experience → Core Web Vitals shows CrUX data grouped by URL pattern, split by mobile and desktop. The Status column ('Good', 'Needs Improvement', 'Poor') is what Google uses for ranking — read it monthly and prioritise patterns where 'Poor' is over 10% of impressions.
Search Console → Experience → Core Web Vitals shows CrUX data grouped by URL pattern, split by mobile and desktop. The Status column ('Good', 'Needs Improvement', 'Poor') is what Google uses for ranking — read it monthly and prioritise patterns where 'Poor' is over 10% of impressions.
Small SaaS sites often see 'Insufficient data' for individual URLs because per-URL CrUX requires enough traffic. The origin-level CWV still applies — Google rolls it up — but the fix prioritisation has to come from PageSpeed Insights lab data plus the templates Search Console flags.
The checklist for this chapter
- ✓Search Console Core Web Vitals report reviewed monthly for mobile and desktop
- ✓PageSpeed Insights field data spot-checked for home, pricing, and top 3 landing pages quarterly
- ✓LCP element on every commercial template marked with fetchpriority='high'
- ✓Third-party DOM-mutating scripts deferred or loaded on interaction
- ✓INP measured across the full session, not just first interaction (FID is deprecated)
- ✓Code-splitting at the route level on the marketing frontend
- ✓Blog posts under 50 visits/month explicitly de-prioritised for CWV work
Where this chapter sits in the guide
rendering — SSR/SSG decisions directly affect LCP and INP. Read the javascript rendering for saas: ssr, ssg, and the empty-shell bug chapter →
Search Console's Core Web Vitals report (CrUX data, grouped by URL pattern). → Chrome User Experience Report (CrUX)
PageSpeed Insights lab score — lab is diagnostic, field data ranks. → PageSpeed Insights
third-party scripts (chat, analytics, A/B tools) more than by application code on most SaaS sites.
web.dev's Core Web Vitals definitions and Google's thresholds for Good / Needs Improvement / Poor. → Core Web Vitals
Quick answers about core web vitals for saas: field data, not lab scores
- How much do Core Web Vitals affect SaaS rankings?
- Modestly — Google uses CWV as a tiebreaker among pages of similar relevance. Passing CWV on a low-relevance page won't rank it; failing CWV on an otherwise winning page can hold it just outside the top five. The leverage is on already-competitive pages.#
- Should I optimise for the PageSpeed Insights score or for CrUX data?
- CrUX. The PageSpeed score is a single-run lab simulation; CrUX is what real Chrome users experienced over 28 days. Google ranks on CrUX. The lab score is useful for diagnosing why field data is bad, not for proving it's good.#
- How do I fix poor INP on a SaaS site?
- INP measures interaction responsiveness across the entire session. The top three SaaS causes are (1) heavy JavaScript bundles that block the main thread, (2) third-party scripts (chat widgets, analytics) that hijack input, and (3) React re-renders triggered by every keystroke in form fields. Code-split aggressively, defer third-party scripts, and use uncontrolled inputs for high-frequency forms.#
- What's the most common LCP problem on SaaS marketing pages?
- A hero image or hero animation that loads after the JS bundle. Mark the LCP element with `fetchpriority='high'`, serve it from the same origin (no third-party CDN redirects), and avoid layering it behind a client-rendered component. On most SaaS sites this single change moves LCP from 3.5s to under 2.0s.#
Questions about core web vitals for saas: field data, not lab scores
- Different datasets. PageSpeed lab is one simulated load; Search Console uses 28-day CrUX field data from real users. The lab score doesn't capture third-party scripts, slow networks, or low-CPU devices the field data does. Trust the field data; Google does.
- Core Web Vitals as a ranking signal. Google Search Central — Core Web Vitals
- INP replaced FID as a Core Web Vital on 12 March 2024. web.dev — INP becomes a CWV
- CrUX dataset and field-data methodology. Chrome — CrUX
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Related concepts
Adjacent entities this chapter touches on. Each is a separate concept worth knowing even if it isn't a chapter on its own.
- Largest Contentful Paint (LCP)
- Time until the largest above-the-fold element is rendered. Good ≤2.5s at the 75th percentile.
- Interaction to Next Paint (INP)
- Latency between any user interaction and the next visual update. Good ≤200ms. Replaced FID on 12 March 2024.
- Cumulative Layout Shift (CLS)
- Sum of unexpected layout shifts during page life. Good ≤0.1. Usually fixed by reserving image and ad space.
- CrUX (Chrome User Experience Report)
- The public dataset of real-Chrome-user performance that Google ranks on. 28-day rolling window, 75th-percentile aggregation.
What's changed on this page
- First published with the field-data-over-lab framework and the five-commercial-templates prioritisation.
- Updated to reflect Google's March 2024 swap of FID for INP and added the three high-leverage INP fixes for SaaS.
- Bound CWV to web.dev's official thresholds and added neighbouring-concept block (CrUX, LCP, INP, CLS).
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
CWV is the last 10% of technical SEO leverage on a SaaS site — meaningful, but only after indexation and rendering are solved. The next chapters cover sitemaps and canonicalisation, the two structural decisions that determine which URLs Google considers in the first place.
See the full guide at technical seo for saas: the founder's checklist. The commercial bridge above is the canonical path from this chapter to your URLs.