Core Web Vitals for B2B: the short answer
Core Web Vitals for B2B websites boil down to one commercial question: does your page load fast enough, respond on time, and stay still long enough for a busy buyer to trust you with an enquiry? The three metrics that answer it are LCP, INP, and CLS, and in 2026 their thresholds are stricter than ever: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. For B2B companies this is not a technical footnote. A slow page does not merely annoy visitors; it quietly removes qualified prospects from your funnel before they ever see your offer, your case studies, or your contact form. Because B2B buyers research multiple vendors across multiple sessions, they compare your pages against competitors in real time. If yours stutter while a competitor pages load instantly, the comparison is over before it begins. The rest of this guide covers the 2026 thresholds, the buyer-behavior reasons speed matters, and the fixes in priority order.
The 2026 thresholds: LCP, INP, and CLS
The 2026 scoring uses three metrics, and the most important change to understand is that INP has replaced FID. Largest Contentful Paint (LCP) measures when the main content of the page, usually the hero headline or image, actually becomes visible. A good LCP is 2.5 seconds or less; between 2.5 and 4 seconds it needs improvement; above 4 seconds it is poor. Interaction to Next Paint (INP) measures how responsive the page feels when a user clicks, taps, or types, and it superseded First Input Delay in March 2024. A good INP is 200 milliseconds or less; 200 to 500 milliseconds needs improvement; above 500 milliseconds is poor. Cumulative Layout Shift (CLS) measures how much content jumps around as the page loads. A good CLS is 0.1 or below; up to 0.25 needs improvement; anything above is poor. Google classifies a page as passing only when at least 75 percent of real-visit experiences over the last 28 days are green; a fast median visit still fails when one buyer in four has a slow experience.
Why B2B buyers are unusually sensitive to speed
B2B buyers behave differently from consumer shoppers, and speed affects them more, not less. A typical buyer evaluating an industrial product or a software vendor opens five to ten tabs, comparing specifications, case studies, pricing pages, and contact forms across competing sites. Each tab load is a chance to leave. Research-based decisions also happen increasingly on mobile, where networks are weaker and patience is shorter. A page that loads in four seconds on a fast office connection can take eight seconds or more on a mobile network, and for a buyer in that moment your site simply looks broken or irrelevant. Unlike a consumer who can impulse-buy after one slow visit, a B2B buyer has internal stakeholders to convince. If your site frustrates them during research, they will not fight to make the case internally; they will add a smoother competitor to the shortlist instead. Speed, in other words, is part of how buyers judge your competence.
Speed, rankings, and paid advertising costs
Speed is also a distribution problem, not just a usability one. Core Web Vitals are an official Google ranking signal, bundled into the page-experience assessment that determines which pages earn top organic positions. Sites that pass all three metrics consistently tend to hold their rankings; sites that fail lose positions to faster competitors, and the natural traffic that B2B pipelines depend on shrinks month by month. Paid advertising compounds the effect: landing pages with poor experience scores are served less often and charged more per click, because the ad auction rewards pages that keep users on the site. A slow landing page therefore costs you twice: fewer organic visitors and a higher price for each paid visitor you do get. Teams that monitor CrUX data weekly watch this trade-off directly: when field metrics dip, impressions and form starts usually dip with them within a few weeks.
How speed affects conversion and your enquiry forms
The direct commercial effect shows up in your funnel numbers. Every extra second of load time pushes more visitors to hit the back button; industry measurements consistently show conversion-rate drops of several percent per additional second on mobile, and B2B forms are the most exposed element of all. A contact form, a quote request, or a catalog download that appears late, stutters on input, or shifts layout the moment the user taps it will be abandoned at a higher rate. INP failures are especially damaging here, because they strike exactly when the buyer is committing: the button that feels dead after a tap tells the prospect that your company is unreliable, even when the code eventually submits. CLS failures are just as subtle: a reader reaches the end of a case study, the layout shifts by sixty pixels, and they tap the wrong link and leave. Multiplied across thousands of research visits, these invisible losses are often the difference between a pipeline that grows and one that stalls despite steady traffic.
How to measure Core Web Vitals correctly
You cannot fix what you do not measure correctly, and the most common mistake is trusting a single number. Start with PageSpeed Insights, the free Google tool that scores any URL in minutes and splits its results into field data and lab data. The field data comes from the Chrome User Experience Report (CrUX), which aggregates real visits from actual Chrome users over the previous 28 days; this is the data Google itself ranks on. The lab data comes from a controlled Lighthouse test in a simulated environment; it is excellent for spotting issues before launch but cannot capture your real audience devices and networks. For pages that already matter, add Real User Monitoring (RUM), a script that measures every visitor actual LCP, INP, and CLS in production and lets you slice results by device type, country, and browser. The practical routine is weekly PSI checks on your five most important pages, plus a monthly review of RUM trends, and never a one-off audit treated as a verdict.
Lab data versus field data: which one to trust
Lab and field data will disagree, and that disagreement is a clue rather than a contradiction. Lab tests run on clean, fast machines with fast networks and cached assets; field data includes every visitor on a three-year-old device on a crowded train. If PageSpeed Insights says your LCP is fine in the lab but poor in the field, the problem is almost certainly something that only appears on real mobile networks: render-blocking scripts, large uncompressed images, or a slow server response that a fast test connection hides. Conversely, a page that fails in the lab but passes in the field means real users are not yet feeling the worst of it, so fix it before your mobile traffic grows. Always diagnose against the 75th-percentile field value, because that is the number Google uses and the number your slowest segment of buyers actually experiences. Optimizing for a perfect lab score while the field data stays red is wasted engineering effort.
What to fix: a checklist ordered by impact
The fixes that move B2B numbers cluster in five places, ordered by typical impact. First, images: serve modern formats such as WebP or AVIF, compress aggressively, set explicit width and height attributes so space is reserved, and lazy-load everything below the fold. Hero images and case-study photos are usually your LCP bottleneck. Second, fonts: use font-display: swap, preconnect to the font host, and self-host only the weights you actually use; invisible font swaps are a classic CLS and LCP culprit. Third, server response: target a Time to First Byte under 800 milliseconds, use a CDN for static assets, enable browser caching, and upgrade hosting if your response time is above one second; no amount of front-end tuning fixes a slow origin server. Fourth, JavaScript: defer non-critical scripts, remove unused libraries, and audit every third-party tag, because analytics, chat widgets, and marketing pixels are responsible for a large share of INP failures by running long tasks on the main thread. Fifth, layout stability: reserve space for embeds, videos, ad slots, and dynamically injected banners, so nothing shifts after the first paint.
Prioritize fixes by impact and effort
Not every fix is worth doing immediately, so rank them by impact and effort. Start where your 75th-percentile field data is red: if LCP is the failing metric, attack images, fonts, and server response first; these are cheap wins. If INP is failing, audit long main-thread tasks, throttle JavaScript, and lazy-load or async-load third-party scripts; many teams discover a single misbehaving tag is responsible for most of the damage. If CLS is failing, the fix is almost always structural: add dimensions to media, reserve space for banners, and avoid injecting content above existing content after load. A practical two-week sprint covers the cheap wins; the next sprint tackles caching, CDN configuration, and JavaScript budgets. Re-measure with RUM, not just lab tools, and wait for four weeks before judging, because the 28-day field window updates slowly. Prioritize pages by business value: your homepage, product pages, and the page your ad spend points to are where speed pays back fastest.
Faster pages, more qualified leads: the business case
The business case is simple arithmetic once you measure it honestly. A B2B website exists to convert research traffic into qualified enquiries, and speed is the multiplier on every other marketing investment. Slow pages waste the ad spend that bought the visit, erode the SEO gains earned over months, and make the company behind the page look less competent than competitors whose sites feel instant. Faster pages improve ranking, reduce bounce, lift form completion, and shorten the path from first research to first conversation, with no change to your offer, pricing, or sales team. The 2026 thresholds are demanding, but they are also generous to well-built sites: hit LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 for 75 percent of visitors, and you will see the results in rankings, cost per lead, and pipeline within a quarter. Treat Core Web Vitals as a lead-generation metric, not a developer chore.
Get a Free Quote
Run PageSpeed Insights on your three highest-traffic pages and check them against the 2026 thresholds above. Get in touch with your results, and you will learn which fixes are likely to improve your lead conversion first, with no commitment required.