Core Web Vitals for B2B Marketing Sites: A Practical Guide
A practical Core Web Vitals guide for B2B marketing sites: loading, responsiveness and layout stability, tag discipline and image handling.

The short answer
Core Web Vitals are three field measures of page experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. Published guidance treats a page as good when LCP is within 2.5 seconds, INP is 200 milliseconds or less and CLS is 0.1 or less, measured at the 75th percentile of visits. On B2B sites, heavy hero media, third party scripts and late loading fonts cause most problems.
Key takeaways
- Judge performance on real visitor data, segmented by mobile and desktop.
- Large hero images and videos are the most common cause of slow LCP.
- Third party scripts for tags, chat and widgets often hurt INP the most.
- Reserve space for images, embeds and banners to keep CLS low.
B2B buyers often visit your site on a phone between meetings, then return on a laptop to read properly. If the first visit is slow or jumpy, there may not be a second one. Performance also shapes how search engines assess page experience, so it touches both conversion and visibility.
The Web Vitals guidance on web.dev defines three Core Web Vitals and their thresholds. Accumentum builds to them as part of our web experiences work. Here is what they mean for a typical B2B marketing site.
What each metric measures
- Largest Contentful Paint (LCP). How long it takes for the largest visible element, usually a hero image, video poster or headline block, to render. The guidance treats 2.5 seconds or less as good.
- Interaction to Next Paint (INP). How quickly the page responds visually after someone taps, clicks or types. Good is 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in 2024.
- Cumulative Layout Shift (CLS). How much content moves around unexpectedly while the page loads. Good is 0.1 or less.
The guidance recommends measuring at the 75th percentile of page loads, split by mobile and desktop. In plain terms, most of your real visitors should get a good experience, not only the ones on fast connections.
Field data versus lab tests
Lab tests load a page in a controlled environment. They are useful for catching problems before release. Field data comes from real visitors on real devices and networks, and it is what the thresholds are judged against. Lab tools cannot measure INP directly because there is no real user interacting, so they rely on proxies. Use lab tests while building and field data to decide whether you have succeeded.
The usual causes on B2B sites
Slow LCP usually comes from:
- Oversized hero images or background videos served at full resolution to phones
- Hero media that waits on scripts before it starts loading
- Slow server responses on pages that could be served from a cache
- Web fonts that block text from showing
Poor INP usually comes from:
- Many third party tags for analytics, advertising, chat and heatmaps all running on load
- Heavy scripts for animations, sliders or menus that do too much work on each tap
- Large pages built entirely in the browser rather than sent as ready HTML
High CLS usually comes from:
- Images and embeds without reserved dimensions
- Cookie banners, promo bars or chat bubbles that push content down after load
- Fonts that swap and change line lengths
A fix order that works
- Measure the right pages. Pull field data for your homepage, top service pages, top articles and contact page. Those carry most buyer visits.
- Fix the hero. Serve modern image formats at sizes that match the screen. Give the hero image a high loading priority. Use a light poster image for any background video.
- Audit third party scripts. List every tag. Remove ones nobody uses. Delay the rest until after the page is interactive where possible.
- Reserve space. Set width and height or an aspect ratio on images, videos and embeds. Give banners a fixed slot.
- Handle fonts. Use fewer weights, load them early and choose a fallback with similar spacing.
- Send real HTML. Make sure the main content arrives in the first response, not only after scripts run.
- Cache what you can. Marketing pages rarely change minute to minute and can usually be cached close to visitors.
- Set a budget. Agree limits for page weight and script count so new features do not undo the work.
Tag discipline is the hardest part
On many B2B sites the code the web team writes is fast. The slowdown comes from tags added later by different teams: analytics, advertising pixels, session recording, chat, scheduling widgets, review badges and testing tools. Each one seems small. Together they compete for the same processing time, which hurts responsiveness on mid range phones most.
Set a simple rule. Every third party script needs an owner, a reason and a review date. Once a quarter, list all tags and ask each owner whether the data is still used. Remove what nobody can justify. For the rest, load them after the main content is ready or only on pages where they are needed. A chat widget that only appears on the contact page costs nothing on articles.
Images and video on brand heavy pages
B2B brands increasingly use large photography, motion and video to stand out. That is fine when it is handled well.
- Export images at several widths and let the browser pick the right one for the screen.
- Use modern formats that compress well, with a fallback for older browsers.
- Give every image and video a set aspect ratio so the layout does not shift.
- Load below the fold images only when they are about to come into view.
- Keep hero videos short, muted and compressed, with a poster image that shows instantly.
How to talk about it internally
Performance conversations go better when they are about visitors rather than scores. Show stakeholders what a slow phone connection actually feels like on your top pages. A short screen recording of a hero that appears late or a button that jumps as someone taps it makes the case faster than any chart.
Keep it fixed
Performance tends to decay as teams add tags, plugins and media. Add checks to your release process, review field data monthly and require a reason for every new third party script. A short performance budget, agreed by marketing and engineering together, prevents most regressions.
For an outside review of your site's speed and stability, request a Digital Growth Assessment.
Frequently asked questions
What are the Core Web Vitals thresholds?
Published guidance on web.dev treats a page as good when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of page loads.
Why do lab scores and real visitor data differ?
Lab tests use one simulated device and network. Real visitors use many devices and connections and actually interact with the page. Field data reflects that variety, so it can look better or worse than a lab score.
What usually slows B2B marketing sites the most?
Oversized hero media, many third party tags running on load and layout shifts from banners or images without reserved space. Fixing those three areas usually brings the biggest gains.
Do background videos hurt performance?
They can if they load at full size before anything else. A light poster image, a compressed video sized for the screen and loading the video after the main content usually keep the effect small.




