The main content of your site should show up in 2.5 seconds or less on a phone. That is Google’s target, published on its own web.dev site.
How fast a plumbing site should load on a phone
Borah Labs found the average plumbing site takes 9.6 seconds and scores 52 out of 100 on Google’s PageSpeed test. It also found 85.7% of those sites failed on the biggest thing on the screen taking too long to appear. That is one company’s study, not a law of nature.
A pipe lets go, a man holds his phone over a wet floor with one bar of signal, and three plumbers are on the screen.
Google scores phones and desktops separately. Your desktop score can look fine while the phone score costs you the call. Read the mobile one.
What is making your site slow
Weight.
Web Almanac 2025, measuring the web in July 2025, puts the middle phone page at 2,164 KB. Images are 911 KB of that, and the code running behind the page is another 646 KB.
Now the arithmetic. Google tests on a weak signal, 1.6 Mbps. At that speed, 2,164 KB takes about 11 seconds just to arrive, before the phone does any work. To land inside 2.5 seconds you get about 500 KB, and that assumes no delay at all, so aim well under it.
WordPress gets blamed for this. Web Almanac 2025 puts the middle WordPress phone page at 2,894 KB, and says 45% of them hit Google’s speed target, against 85% for Duda. The platform is not the sin. The weight is. Page builders and plugins pile it on, and we build plain static pages instead.
How to check your own site the way a customer sees it
Open Google PageSpeed Insights, paste in your address, and read the Mobile tab only. Write the number down with the date next to it.
Your own phone on office wifi will lie to you. Google’s phone test assumes 1.6 Mbps down, a 150 millisecond delay before anything starts, and a phone about four times slower than a laptop. Those settings are in Google’s Lighthouse documentation, which calls that roughly the bottom quarter of 4G and the top quarter of 3G.
The second test is free. Turn wifi off, walk to the far corner of your building, load your site, and count out loud.
PageSpeed, GTmetrix and Pingdom will disagree. Pick Google’s mobile number and stick with it. It is the one Google uses.
Tap to call, at the top, big enough for a wet thumb
Your number belongs at the top of the page, visible before anyone scrolls, set up as a link so one tap dials it. Write it as text too, so it can be copied. Never put it inside a picture.
Google’s phone test, Lighthouse, wants tap targets 48 by 48 pixels with about 8 pixels of space around them. The accessibility floor is lower, 24 by 24 pixels under WCAG 2.2 AA. Build to 48.
Normal text needs contrast of at least 4.5 to 1 against its background under that same standard. WebAIM checked a million home pages in 2026 and found low contrast text on 83.9%.
On a desktop that link behaves differently, handing off to whatever calling app is installed, and some machines only offer to save the number.
Name the job the way a customer says it
Give each job its own page, titled in the words a customer uses out loud: snake the drain, water heater replacement, burst pipe, sewer line backup. Not “residential drainage solutions”.
Put your prices, hours and service area on the page in text. A photo of a price list does not count. Neither Google nor ChatGPT can read one.
The page should also carry a hidden label saying this is a plumbing business, with your phone number and hours attached to it. You never see it. Machines do.
Naming the job right will not get you named by ChatGPT on its own.
What a plumbing website should never do
- No hero video. Web Almanac 2025 puts the middle video weight on a phone page at 384 KB, and only about 7% of phone pages carry one. Chrome will not play sound to a first time visitor anyway.
- Never hold back the top image. web.dev says do not lazy load an image that is on screen when the page opens. Web Almanac 2025 found about 10% of phone pages doing that to their main image.
- No popup over your phone number. Google’s page experience checklist asks whether pages avoid intrusive interstitials, its words for a box covering what someone came for.
- No stack of chat widgets, trackers and review badges. Google’s test flags outside code that blocks the page for 250 milliseconds or longer.
- No contact form as your only way in. Nobody fills in a form standing in water.
What a fast site will not do for you
Google Search Central says its speed measurements are used by its ranking systems. The same page says good scores do not ensure ranking at the top. Both are true.
A fast page does not fix wrong hours, an empty review page, or a phone nobody answers. Those beat speed every time. We cannot prove a call number, so we will not claim one.
A rebuild is not always the answer. Compressing your images and cutting the extra scripts may get you inside the target on the site you have.
The only proof we own is our own build: 100 on Google’s PageSpeed test, desktop and mobile. That is our site, not a promise about yours.
We also run a free scan: we ask the questions your customers ask, write down who gets named, and reply by email after a person reviews it. Ask if you want a call.