Core Web Vitals for B2B Exporter Websites: A Practical Guide
Core Web Vitals are Google's three user-experience metrics for loading speed (LCP), responsiveness (INP) and visual stability (CLS). For a B2B exporter website, the goal is simple: reach "good" scores on your product, category and contact pages so buyers in any market can open a spec sheet and send an inquiry without friction. Google says relevance still comes first, so treat speed as a way to protect the traffic your content has already earned, not as a ranking shortcut.
In this article
- What are Core Web Vitals, and what counts as "good"?
- Do Core Web Vitals affect Google rankings?
- Why do Core Web Vitals matter more for exporters than for local businesses?
- How do you measure Core Web Vitals correctly?
- How do you fix a slow Largest Contentful Paint?
- How do you improve responsiveness (INP)?
- How do you stop layout shift (CLS)?
- What should an exporter fix first? A priority checklist
- How do Core Web Vitals fit with the rest of your SEO?
- Frequently asked questions
01What are Core Web Vitals, and what counts as "good"?
Core Web Vitals are a small set of field metrics that describe how a page feels to a real visitor. There are three, and each has a published threshold.
Google's web.dev defines the thresholds as follows, each measured at the 75th percentile of page views.
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content appears | 2.5 seconds or less | Over 4 seconds |
| Interaction to Next Paint (INP) | How quickly the page responds to clicks, taps and keys | 200 ms or less | Over 500 ms |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
The 75th-percentile rule matters for exporters. A page earns "good" only when at least 75% of real page views meet the threshold. If your buyers visit from several countries on different networks and devices, the slowest quarter of those visits decides your score.
02Do Core Web Vitals affect Google rankings?
Yes, but with limits that are easy to over-read. Here is what Google actually says.
Google's Search Central documentation says it "highly recommend[s] site owners achieve good Core Web Vitals for success with Search," and that this "aligns with what our core ranking systems seek to reward." The page does not say how much weight the metrics carry.
Google's page experience documentation says there is "no single signal" for page experience, that relevance wins ("Google always seeks to show the most relevant content, even if the page experience is sub-par"), and that "trying to get a perfect score just for SEO reasons may not be the best use of your time."
For an exporter, this points to a clear order of work. First, make sure each page answers the buyer's query better than competing pages: specifications, standards, certifications, lead times. Then make sure the page is fast and stable enough that a buyer reaches that content. Speed helps most when several pages are equally relevant, because Google notes that a great page experience can contribute to success "in such cases".
03Why do Core Web Vitals matter more for exporters than for local businesses?
A local business serves visitors who are near its server. An exporter serves a buyer in Kuala Lumpur, another in Almaty and a third in Houston, all opening the same product page.
Three things make this harder than it looks:
- Distance. Server response time is the first part of loading. If your host sits in one country and the buyer is in another, the first byte takes longer before any of your page can appear.
- Heavy pages. Manufacturer sites often carry large product photos, PDF catalogs, video embeds, chat widgets and tracking scripts. Each one costs loading and interaction time.
- Mixed devices. Procurement staff may browse on an office desktop, but engineers and sourcing agents also check specs on phones between meetings.
We expect these issues to be most visible on pages with large image galleries and third-party embeds, which is exactly where exporters put their most commercial content. We have not measured this across a sample of exporter sites, so treat it as a priority guess to test on your own pages, not as a finding.
04How do you measure Core Web Vitals correctly?
Many teams test once in a lab tool, see a good score and stop. That misses the difference between lab data and field data.
According to Google's PageSpeed Insights documentation, field data comes from real Chrome users through the Chrome User Experience Report over the previous 28 days, reported at the 75th percentile. Lab data comes from a simulated Lighthouse load in a controlled environment, and it can miss real-world bottlenecks.
PageSpeed Insights looks for page-level field data first. If a page does not have enough samples, it falls back to origin-level data for the whole site. If the origin also lacks data, no real-user data is shown. To pass the Core Web Vitals assessment, all three metrics must be "good" at the 75th percentile, and if INP lacks data, LCP and CLS must both be good.
Here is a practical measurement routine:
- Open the Core Web Vitals report in Google Search Console to find groups of URLs that are slow in real use.
- Test one representative URL from each group in PageSpeed Insights, and read the field data section before the lab score.
- Use the lab results to find the cause of each problem, and re-test after every change.
- Wait for the 28-day field window to refresh before judging whether a fix worked.
Low-traffic product pages often have no page-level field data. In that case, group similar pages by template (for example, all product pages) and fix the template, not individual URLs.
05How do you fix a slow Largest Contentful Paint?
LCP is usually the hero image, a large product photo or a headline block. Fixing it means understanding where the time goes.
web.dev breaks LCP into four parts: time to first byte (about 40% of the total in the ideal case), resource load delay (under 10%), resource load duration (about 40%) and element render delay (under 10%). web.dev stresses that these proportions are guidelines, not absolute targets.
Work through the four parts in this order:
- Time to first byte. web.dev says a high value can make a 2.5-second LCP "difficult or impossible", and lists redirects, distant visitors, poor network conditions and URL parameters that prevent CDN caching as common causes. Remove unnecessary redirects (for example, http to https to www chains) and keep tracking parameters from creating uncached URL variants.
- Resource load delay. The main image should start loading together with the first resource on the page. web.dev recommends making it discoverable in the initial HTML and using
fetchpriority="high"on the likely LCP image, sparingly, because using it on more than one or two images makes it less useful. - Lazy loading. Do not lazy-load the LCP image. web.dev says this "will always lead to unnecessary resource load delay".
- Content delivery. web.dev explains that a CDN shortens the distance a resource travels, and that image CDNs also reduce file size. It also notes that serving images from the same origin as the HTML avoids an extra connection cost.
For a product page, the LCP element is usually the first product photo. A single well-compressed, correctly sized image that is not lazy-loaded often does more than any amount of script tuning. Our website development service treats image size, format and loading order as part of the page template, not as an afterthought.
06How do you improve responsiveness (INP)?
INP measures how long the page takes to react after a visitor interacts: opening a menu, switching a product tab, filtering a table or submitting an inquiry form.
web.dev explains that each interaction has three phases: input delay, processing duration and presentation delay, and the total is their sum. Long tasks, heavy scripts at startup and large DOMs can extend these phases.
What helps on an exporter site:
- Remove scripts you do not use, especially old widgets, duplicate trackers and unused plugins.
- Keep event handlers light and split long work into smaller tasks so the browser can respond to the click first. web.dev describes yielding with
setTimeoutfor this purpose. - Keep the DOM small. Very long specification tables or product lists rendered all at once make updates slower; web.dev mentions
content-visibilityas a way to defer rendering of off-screen content.
The inquiry form and the language switcher are the interactions that matter most commercially. Test those two first, on a mid-range phone, because a form that hesitates after the buyer taps "Send" costs real leads.
07How do you stop layout shift (CLS)?
Layout shift happens when elements move after the visitor has started reading. On a product page, a late image or banner can push the "Request a quote" button just as the buyer taps it.
web.dev lists the main causes as images and video without dimensions, ads, embeds and iframes without reserved space, dynamically injected content, web fonts that swap after load, and animations of layout properties. Its fixes include:
- Set
widthandheightattributes on images and video so the browser can reserve space. - Use the CSS
aspect-ratioproperty for responsive content. - Reserve space for embeds and late-loading widgets with
min-heightoraspect-ratio. - Use
font-display: optional, a close fallback font and preloaded critical fonts to reduce font-related shifts. - Animate with
transforminstead of properties that trigger layout.
Cookie banners, chat widgets and language prompts are common sources of shift on multilingual sites. If your site shows a language suggestion banner, reserve space for it or overlay it so it does not push content down. This pairs naturally with a clean hreflang setup, because both are about making each language version predictable for buyers and crawlers.
08What should an exporter fix first? A priority checklist
Use this order. It gives the largest gains for the least effort on a typical product-led site.
| Priority | Action | Metric it helps |
|---|---|---|
| 1 | Compress and correctly size the first product image; do not lazy-load it | LCP |
| 2 | Remove redirect chains and uncacheable URL parameters | LCP (TTFB) |
| 3 | Add width and height (or aspect-ratio) to every image and embed | CLS |
| 4 | Audit third-party scripts and remove anything unused | INP, LCP |
| 5 | Reserve space for banners, chat widgets and language prompts | CLS |
| 6 | Test the inquiry form and menus on a mid-range phone | INP |
| 7 | Consider a CDN, especially if buyers are far from your server | LCP (TTFB) |
| 8 | Re-check field data in Search Console after 28 days | All |
Do these on the template level first (home, category, product, contact). Fixing four templates usually improves hundreds of URLs at once.
09How do Core Web Vitals fit with the rest of your SEO?
Core Web Vitals are one part of a larger system. They protect the value of pages that are already relevant, crawlable and trustworthy. Before spending weeks chasing a perfect score, check that:
- Your product pages contain the facts buyers need. See our industrial product page checklist.
- Your markup is accurate and consistent. See our guide to structured data for exporter websites.
- Your site structure supports each target market and language, which is covered in our SEO service approach.
If you want a template-level speed review of your own site, contact us with your main product page URL.
10Frequently asked questions
Are Core Web Vitals a Google ranking factor?
Google says its core ranking systems seek to reward good Core Web Vitals and recommends achieving them, but it also says relevance comes first and that there is no single page experience signal. Treat them as important, not decisive.
What is a good Core Web Vitals score?
The "good" thresholds are LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less, each at the 75th percentile of real page views.
Why does PageSpeed Insights show a good lab score but a failed assessment?
Lab data is one simulated load. The Core Web Vitals assessment uses field data from real Chrome users over 28 days, so it reflects your actual visitors' devices and networks. The two can differ.
Do I need a CDN for a B2B exporter website?
Not always, but if your buyers are far from your server, a slow first byte can make a 2.5-second LCP hard to reach. web.dev notes that a CDN reduces the distance resources travel. Measure your field TTFB and LCP by market before deciding.
Should I chase a perfect 100 in Lighthouse?
No. Google says trying to get a perfect score only for SEO reasons may not be the best use of your time. Aim for "good" field scores on your key templates, then return to content and trust.
Which pages should I fix first?
Start with the templates that bring and convert buyers: home page, product pages, category pages and the contact page.
Source: How the Core Web Vitals metrics thresholds were defined (web.dev); Understanding Core Web Vitals and Google search results (Google Search Central); Understanding page experience in Google Search results (Google Search Central); Optimize Largest Contentful Paint (web.dev); Optimize Interaction to Next Paint (web.dev); Optimize Cumulative Layout Shift (web.dev); About PageSpeed Insights (Google).
Want results like this for your brand?
Tell us your market, product and goals. We will reply with a clear plan.
Structured Data for Exporter Websites: A Practical Guide
Product Page Checklist for Industrial Equipment Exporters
