Website speed for plumbing and trade sites

Why speed matters for plumbing firms in particular

Plumbing customers often search at the worst possible moment, with water on the floor and one hand free. They are on a phone, sometimes in a basement or loft with a weak signal. Every second the page takes to show your phone number is a second in which they might press back and try the next result.

Ofcom's Online Nation 2025 research found that smartphones account for most of UK adults' time online.^[1][2] Speed on a phone, over a mobile connection, is the version of your site that matters most.

What Core Web Vitals measure

Core Web Vitals are three measurements Google uses to describe the experience of loading and using a page. Google's web.dev documentation sets out a "good" threshold for each:^[3]

Google recommends measuring each at the 75th percentile of real page loads, separately for mobile and desktop. A page passes only if it meets all three at that level.^[3] In other words, the target is that most real visitors, not just the lucky ones on fast wi-fi, get a good experience.

Where to see your numbers

If your site has enough visitors, Google Search Console shows a Core Web Vitals report based on real visits from Chrome users. It groups pages as good, needing improvement or poor. For smaller sites without enough data, lab tools that simulate a phone load can still point to problems, although their numbers are estimates rather than real-world measurements.

Look at the mobile report first. Many trade sites look fine on desktop and fail badly on phones.

The usual causes of a slow trade site

Oversized images

A photo straight from a phone camera can be several megabytes. Placed on a page without resizing, it may take longer to load than everything else combined. Images should be resized to the largest size they are displayed at, compressed and served in a modern format where possible. Hero images at the top of the page should be loaded first, while images further down can wait until the visitor scrolls.

Too many scripts

Each script, whether for analytics, chat, reviews, maps or social media, has to download and run. Many come from third parties, adding extra connections. They are a common cause of poor responsiveness, because the phone's processor is busy running scripts when the visitor taps.

Page builders and heavy themes

Drag-and-drop page builders and multi-purpose themes are convenient, but they often load code for every feature they offer, used or not. A simple plumbing page can end up loading as much as an online shop.

Web fonts

Several font families in many weights add weight and can cause text to flash or shift as fonts arrive. One or two families, limited weights and self-hosting help.

Layout jumps

Images without set dimensions, adverts or banners that push content down, and fonts that change size as they load all cause layout shift. The classic example is a visitor about to tap the call button when a cookie banner appears and moves it.

Fixes in order of impact

1. Resize and compress images. Usually the biggest single win.
2. Remove what you do not need. Unused plugins, widgets, embedded maps and chat tools.
3. Load third-party scripts late or not at all. Nothing should load before your phone number appears.
4. Set image dimensions and reserve space for anything that loads late, so the layout stays still.
5. Limit fonts to what the design really needs, and host them yourself.
6. Use good hosting with HTTPS and compression switched on.

Hosting and server settings

Even a well-built page will feel slow on poor hosting. For a small plumbing site, the hosting does not need to be expensive, but a few settings make a real difference:

• HTTPS with modern protocols. Current hosting usually supports newer connection protocols that load several files at once more efficiently.
• Compression. Text files such as HTML, CSS and JavaScript should be compressed before sending. Most hosts can switch this on with a simple setting.
• Caching rules. Files that rarely change, such as fonts, logos and stylesheets, can be cached by the visitor's browser so repeat visits load almost instantly.
• Server location. Hosting in or near the UK keeps the distance data travels short for UK customers.
• No unnecessary redirects. Each redirect, for example from an old address or from www to non-www, adds a round trip. Keep chains to a single step.

Your developer or hosting provider can check all of these in under an hour. They are some of the cheapest speed improvements available.

Why we hand-build plumbing sites

We build plumbing websites as plain HTML and CSS with a small amount of JavaScript and a self-contained form handler. That choice is mostly about speed and reliability. There is no page builder adding code and no plugin stack running in the background. Fonts are self-hosted. Images are sized for the screen. Nothing loads before the content.

It also helps accessibility. The same discipline that keeps pages light, such as clear structure and few moving parts, makes them easier to use with a screen reader or keyboard. We build to WCAG 2.2 level AA alongside the speed targets.^[4]

Speed is not the only thing

A fast page with weak content will not bring calls. Speed removes a reason to leave. It does not create a reason to stay. The pages still need clear services, honest coverage, checkable credentials and an obvious way to call. Get both right and the site does its job. The website essentials guide covers the content side.

Common questions