Site Speed Is a Revenue Lever, Not a Tech Detail
Performance gets filed under engineering housekeeping. The data says a faster site is one of the most direct levers on conversion and revenue you have. Here's the business case, and where manufacturer catalogs and spec sheets usually lose the time.

Performance gets filed under engineering housekeeping, the thing you tidy up after the "real" work ships. Then you look at what speed does to conversion and revenue, and the filing looks backwards. A fast site is one of the most direct, best-measured levers you have on the number that matters. It just happens to be owned by engineering, so it gets treated as a cost when it's really a growth investment.
Every second has a price
Start with the cost of slow. The BBC found it lost an additional 10 percent of users for every extra second its site took to load (via Google web.dev). That's 10 percent of the audience gone for each second. Those users don't file a complaint. They leave, and you never see them in your funnel because they never entered it.
It's a hidden tax on a slow site. You spend on ads, content and SEO to earn the click, then lose a chunk of those hard-won visitors in the two seconds before your page finishes rendering, upstream of everything your marketing measures. Peter, our co-founder, traces the same leak in your marketing budget has a leak.
Speed shows up on the revenue line, repeatedly
This part should end the debate, because the evidence is causal. These are controlled tests and before-and-after investments, which is a stronger claim than "fast sites also happen to convert well."
When Vodafone ran a proper A/B test and improved its Largest Contentful Paint by 31 percent, it drove 8 percent more sales, a 15 percent better lead-to-visit rate, and an 11 percent better cart-to-visit rate (Google web.dev case study). The site, traffic and offer stayed the same. The only variable was speed, and it moved sales by 8 percent.
One speed test moved three revenue metrics
The pattern repeats across very different businesses. After investing in Core Web Vitals, Rakuten 24 grew revenue per visitor by 53.37 percent and its conversion rate by 33.13 percent, and redBus lifted sales by 7 percent (Google web.dev). Those are different markets and products, and in each one the performance work showed up on the revenue line.
The effect isn't limited to retail. In a Deloitte study for Google of 37 brand sites and more than 30 million sessions, a 0.1 second mobile improvement on four speed metrics, on every page of the journey, was linked on lead generation sites to a 21.6 percent increase in users progressing from the first form step to the form submission page (Deloitte, "Milliseconds Make Millions," via Google web.dev). For a manufacturer whose website's job is to produce quote requests, that's the number to care about. Treat it as directional, since it's one study from 2019 data, but it points the same way as everything else.
If a consultant offered you an 8 percent sales lift with no change to your product, your price, or your ad spend, you'd take the meeting.
A serious performance investment is that meeting.
Why so many sites are quietly slow
If speed pays this well, why are so many sites slow? Mostly because the people who own them almost never feel the problem. You browse your own site on a fast laptop, on office wifi, with everything cached. Your buyer opens it on a mid-range phone, on a patchy connection, cold. The gap between those two experiences is big, and the owner lives on the comfortable side of it. Our docs guide on what slows a website down lists the usual causes.
Slowness also isn't a single switch you flip. It accumulates: oversized images, blocking scripts, heavy third-party tags, fonts that hold up the render, a framework doing too much in the browser. Each is small, and together they add up to the two seconds that cost you the 10 percent. Fixing it takes discipline throughout the build. A plugin at the end won't do it.
Where manufacturer sites lose the time
Manufacturer and distributor sites have their own speed problems, and they tend to sit on the very pages buyers use to decide. A buyer evaluating you is usually filtering a catalog, opening a product, and checking a spec sheet, often from a phone on a plant floor or a job site. These are the places those pages usually get heavy:
- Catalog and category pages. Hundreds of product thumbnails, each uploaded at full camera resolution, and faceted filters that reload the whole page on every click. Serve thumbnails at their display size, lazy-load images below the first screen, and make filters update results without a full reload.
- Product pages built around a PDF. When the dimensions, ratings, and certifications only live in a PDF spec sheet, the buyer waits for a multi-megabyte file to answer a one-line question. Nielsen Norman Group advises against using PDFs for content that could be a web page, and recommends linking any PDF from an HTML page that summarizes it (Nielsen Norman Group, 2020). Put the key specs in an HTML table on the page, and keep the PDF as a download beside it, compressed.
- CAD viewers, 3D models, and configurators. These scripts are often large and load on every product page whether or not anyone uses them. Load them when the buyer clicks "View 3D" or "Configure," instead of on page load.
- Video and image galleries. An autoplaying factory video in the hero can easily be the heaviest thing on the page. Use a poster image and load the video on click.
- Third-party tags. Chat widgets, CRM tracking, and old marketing pixels pile up on B2B sites over years of campaigns. Audit them and remove the ones nobody reads.
Our article on what manufacturing buyers check covers what buyers look for on those pages. Speed decides whether they get to see it.
Performance is conversion work
Speed isn't a technical metric that sits next to conversion. It's part of conversion, because a page can't persuade a visitor who has already left. Every improvement to load time widens the top of the funnel by keeping people who would otherwise have bounced, and it does it before your headline, your proof, or your offer gets a chance to work.
That makes performance one of the most valuable fixes you have, because it compounds with everything else. A sharper message on a slow page still leaks visitors. The same message on a fast page keeps them long enough to land. It's the same logic behind why most A/B tests lose: the biggest wins usually come from removing friction rather than clever tweaks, and nothing adds more friction than a page that hasn't loaded yet. That's why speed is step one of our Conversion System.
What actually moves the numbers
If you want the revenue results above, fix what Google weighs, in the order that pays. The sequence starts with measuring the right thing. Working through these on your own site? Our free B2B website audit checklist is the page-by-page version you can run as you go.
Measure on real-user data, not a lab score
Your Lighthouse score on a fast laptop isn't what a buyer feels on a mid-range phone. Use field data, the Chrome UX Report behind PageSpeed Insights or your own real-user monitoring, and read the 75th-percentile experience on real devices and connections. That's the number tied to revenue, and it's often far worse than the lab score you've been reassured by.
How to do it
- In PageSpeed Insights, enter your URL and read the "Discover what your real users are experiencing" field panel first, not the Lighthouse lab score below it.
- Switch to the Mobile tab and record the 75th-percentile LCP, INP, and CLS against the good thresholds of 2.5s, 200ms, and 0.1.
- Cross-check the origin in the Chrome UX Report so the numbers reflect a 28-day trend, not a one-off reading.
- For low-traffic pages that return no field data, add Google's web-vitals library to capture your own real-user numbers.
See a worked example
A product catalog page can score well in a Lighthouse lab run on a fast laptop, yet its Chrome UX Report field data shows a 75th-percentile LCP well over the 2.5 second threshold on mobile. Treating the field number as the real one is what surfaces the problem the lab score hid.
Tools to use
PageSpeed Insights, the Chrome UX Report docs, and the web-vitals library.
Steal our AI prompt
I'll paste the Core Web Vitals field data from PageSpeed Insights for my page. Tell me which of LCP, INP, or CLS is failing at the 75th percentile on mobile, how far each is from the "good" threshold (2.5s / 200ms / 0.1), and which one to fix first for the biggest real-user gain. Then list any data you still need. Field data: [paste]
Fix Largest Contentful Paint first, it is usually the biggest lever
LCP is how fast the main content appears, and it's mostly down to images, fonts and server response time. Right-size and compress the hero image, serve modern formats, preload it, and get render-blocking fonts out of the critical path. Most of the revenue gain lives in this one step.
How to do it
- Run the URL through PageSpeed Insights and read the "Largest Contentful Paint element" diagnostic to confirm which element is your LCP.
- Drop the hero image into Squoosh, export it as AVIF or WebP at its real display size, and ship responsive
srcsetwidths so no oversized bytes load on mobile. - In the HTML head, preload the LCP image and set
fetchpriority="high"on it so the browser fetches it before lower-priority resources. - Get render-blocking fonts out of the critical path: self-host them, set
font-display: swap, and preload only the weight the hero actually uses.
See a worked example
A product page whose LCP element is a full-resolution photo of the product, uploaded straight from the photographer, is a common case. Exporting it at its real display size as AVIF or WebP, serving smaller srcset widths to phones, and preloading it with fetchpriority="high" attacks the biggest part of the LCP time. Moving a render-blocking web font off the critical path with font-display: swap helps further.
Tools to use
Squoosh for in-browser image compression, web.dev on optimizing LCP, and web.dev on the Fetch Priority API.
Steal our AI prompt
Here is the Largest Contentful Paint breakdown from PageSpeed Insights for my page (TTFB, load delay, load time, render delay): [paste]. Tell me which phase dominates my LCP, the three highest-impact fixes for that phase, and the exact HTML or CSS changes to make (image format and size, preload, fetchpriority, font-display). My LCP element is: [describe]
Cut the JavaScript that delays interaction
Interaction to Next Paint measures how quickly the page responds when someone taps or clicks, and heavy JavaScript is the usual culprit. Defer and split non-critical scripts, delete what you no longer use, and audit third-party tags, which are often the worst offenders and the least noticed.
How to do it
- Run the page through PageSpeed Insights and read the "Reduce JavaScript execution time" and "Reduce the impact of third-party code" diagnostics to see which scripts cost the most.
- Open Chrome DevTools, switch to the Coverage tab, reload, and delete or code-split whatever it flags as unused.
- In the DevTools Performance panel, record an interaction, find main-thread tasks over 50ms, and break them up with
scheduler.yield()orsetTimeout. - Audit third-party tags in the Network panel or your tag manager, then defer, lazy-load, or remove any that first interaction does not need.
See a worked example
On a product page where the main bundle, a 3D viewer, a chat widget, and two analytics tags all execute up front, deferring the non-critical scripts and loading the viewer only when the buyer clicks "View 3D" frees the main thread, so filter clicks and the quote button respond without lag.
Tools to use
Steal our AI prompt
I'll paste my PageSpeed Insights "Reduce JavaScript execution time" and "Reduce the impact of third-party code" diagnostics. Identify the scripts costing the most main-thread time, tell me which are safe to defer, lazy-load, or remove, and how to code-split the rest. Flag any third-party tag that is not needed before first interaction. Diagnostics: [paste]
Reserve space so the page stops jumping
Cumulative Layout Shift is the page lurching as it loads, and it comes from media and embeds with no space held for them. Set an explicit width and height or aspect ratio on images and video, and reserve a slot for ads and late-loading widgets. Once you do, the shifting mostly goes away.
How to do it
- Run the URL through PageSpeed Insights and read the CLS value plus the "Avoid large layout shifts" diagnostic to see which elements move.
- In Chrome DevTools, open the Rendering tab and turn on "Layout Shift Regions" to watch exactly which elements jump as the page loads.
- Add explicit
widthandheightattributes to every image and video, or set a CSSaspect-ratio, so the browser reserves the box before the media arrives. - Give ads, embeds, and late-loading widgets a fixed-height container with
min-heightoraspect-ratio, so injected content fills a reserved slot instead of shoving the page down.
See a worked example
On a catalog page, product thumbnails with no dimensions and a late-loading cookie banner push the grid around as it loads. Adding width and height or a CSS aspect-ratio to every thumbnail and reserving a fixed slot for the banner keeps the grid still, so a buyer doesn't tap the wrong product.
Tools to use
Steal our AI prompt
Here are the elements flagged in my PageSpeed Insights "Avoid large layout shifts" report: [paste]. For each one, tell me the most likely cause (missing dimensions, injected content, a font swap, a late banner) and the exact CSS or HTML fix (width and height, aspect-ratio, or a min-height reservation) to stop the shift.
Re-measure against conversions, not the tool
After each fix, measure again on the devices your buyers use, and grade it against sales, sign-ups and calls rather than a Lighthouse number. Going from slow to fast changes results; chasing a perfect score past that point rarely does. That prioritized work is what website optimization is for, and our web development work builds it into every site from the first line.
How to do it
- Add the web-vitals library to your site and send LCP, INP, and CLS as events into Google Analytics 4.
- In GA4, build an exploration comparing real conversions (form submits, calls, sign-ups) for sessions with good versus poor INP and LCP.
- Re-run the fixed page in PageSpeed Insights and read the field panel on the Mobile tab, not just the lab score.
- Watch the page in Search Console's Core Web Vitals report over the following weeks to confirm real users move into the Good bucket.
See a worked example
A manufacturer lazy-loads the chat widget and a CAD viewer on its product pages, then uses GA4 to compare quote-request submissions from sessions with good versus poor INP and LCP before and after the change. That comparison tells it whether the work paid off. The Lighthouse score can't.
Tools to use
Steal our AI prompt
I want to tie Core Web Vitals to conversions in GA4. Walk me through sending LCP, INP, and CLS from the web-vitals library into GA4 as events, then building an exploration that compares my conversion rate (form submits, calls, sign-ups) for sessions with "good" versus "poor" INP and LCP. My current analytics setup is: [describe]
The honest part
Speed is a means to an end. A perfect Lighthouse score on a page nobody buys from is worth nothing, and past a point the returns flatten: going from slow to fast makes a big difference, while going from fast to slightly faster barely registers. What you're protecting is the sales, sign-ups and calls behind the number in the tool.
So treat speed the way you treat a marketing channel rather than an engineering chore, and it becomes what the data already says it is: one of the most reliable growth levers you own. If you want a quick read on where your site stands, speed included, our free website scorecard is a good place to start.
Keep reading
UX & Web DesignWe Audited the Quote Request Path on 150 Manufacturer Websites
We checked how 150 US manufacturers handle the moment a buyer wants a quote: the form, the file upload, the reply promise, the specs and proof around it, and the email behind it. About half have a dedicated quote form. Only 7% say when they'll reply. Here's what we found, sector by sector, and a 10-point check for your own site.
UX & Web DesignWhat a B2B Website Redesign Really Costs
Published guides put most B2B redesigns between $50,000 and $150,000, and not one shows its data. Here's our own price, what it buys, and a calculator for the bigger number: what your current site costs you every month.
UX & Web DesignFood and Beverage Manufacturer Websites: What Buyers Check Before They Call
Most food website advice is written for consumer brands. This is the supplier side: what a brand's quality, procurement and R&D people check on a co-packer, ingredient supplier or private label site, and the pages, documents and certification details that keep you on their list.
See exactly where your site is losing conversions
Paste your URL and get an instant conversion score. No form to fill out, no sales call.
Strategies for businesses building what's next.
Occasional notes on turning B2B websites into pipeline. Unsubscribe any time.