Key takeaways
- Emergency searchers are on phones, and 16% of US adults rely on a smartphone with no home broadband[1].
- Google's 'good' thresholds: main content within 2.5 seconds, responses to taps within 200 ms, layout shift of 0.1 or less, at the 75th percentile of page loads[2].
- Fix the first screen first: hero images, sliders, chat and review widgets, and tracking scripts cause most slow plumbing sites.
- Test on a real mid-range phone over mobile data, not just on the office desktop.
Why speed is a plumbing problem, not a tech problem
A homeowner with water coming through the ceiling doesn't wait for a slow page. They tap back and call the next plumber. That makes website speed an operations issue as real as answering the phone. Every second the first screen takes to appear is a second when your phone number isn't visible.
Many of those visitors are on mobile data. Pew Research Center reports that 16% of US adults are smartphone-dependent, using a smartphone for internet access without home broadband[1]. Add everyone searching from a basement, a driveway or a job site, and the typical emergency visit happens on a phone with an imperfect connection.
Most plumbing companies don't have a web developer. About 77% of plumbing, heating and AC contractor establishments had fewer than 10 employees in 2023[3]. The good news is that the fixes that matter most on contractor sites are simple and mostly involve removing things.
The three numbers in plain words
Google's Core Web Vitals measure three things a visitor feels. Its guidance says that for a good experience, Largest Contentful Paint should occur within 2.5 seconds, Interaction to Next Paint should be 200 milliseconds or less, and Cumulative Layout Shift should be 0.1 or less. It recommends measuring at the 75th percentile of page loads, segmented across mobile and desktop[2]. Results are rated poor above 4 seconds, 500 milliseconds and 0.25 respectively[4].
| Metric | What the visitor feels | Good | Poor | Common cause on plumbing sites |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content appears | 2.5 seconds or less | Over 4 seconds | Huge hero photo or video, slow hosting, sliders |
| Interaction to Next Paint (INP) | How quickly the page reacts to a tap | 200 ms or less | Over 500 ms | Heavy chat, review and tracking scripts |
| Cumulative Layout Shift (CLS) | Whether things jump around while loading | 0.1 or less | Over 0.25 | Banners and widgets that load late and push content down |
Source: web.dev (Google), 2026[4]
Show the data
| Item | Value |
|---|---|
| Good (at or under) | 2.5 sec |
| Poor (over) | 4 sec |
The 75th percentile matters: it means three out of four real visits should meet the threshold, including visitors on older phones and weak connections, not just your own fast phone on office wifi.
What to fix first
Shrink the first screen
Replace autoplay video and image sliders with one compressed photo of your team or truck, sized for phones. This alone often brings LCP into range.
Put the phone number in text
Make the number and 'text us' button part of the page's text, not an image or a script that loads later, so they appear immediately.
Cut third-party scripts
List every chat widget, review carousel, pixel, heat-map tool and booking embed. Remove what you don't use and delay the rest until after the page has loaded.
Reserve space for late elements
Give banners, review badges and embedded maps a fixed space so they don't push the phone number down when they appear.
Compress every image
Job photos from phones are often several megabytes each. Resize and compress them before upload, and lazy-load images below the first screen.
Check hosting and theme
Cheap shared hosting and bloated multipurpose themes are common on contractor sites. If the server is slow to respond, no other fix will be enough.
Images: the biggest easy win
Plumbing sites are full of photos, and they should be: real job photos build trust. The problem is how they are uploaded. A photo straight from a technician's phone is far larger than any phone screen needs, and a homepage with a dozen of them can take a long time to appear on mobile data.
- Resize photos to the largest size they are actually shown at before uploading, typically no wider than the content area of your page.
- Save them in a modern compressed format your site supports, and check the file size after export.
- Use one well-chosen image on the first screen instead of a gallery or slider.
- Let images further down the page load only when the visitor scrolls to them.
- Give each image fixed dimensions in the page so text doesn't jump when it arrives.
- Remove old images that no page uses anymore; they clutter backups and sometimes still load.
Widgets that slow plumbing sites
Contractor sites accumulate add-ons over the years: every marketing vendor asks for 'just one script'. Each one can add download time and slow down taps. Audit them once a quarter.
- Chat widgets: keep one, and load it after the main content. Two chat tools on the same site is common and pointless.
- Review carousels: a static badge with your rating and a link often does the same job far faster.
- Embedded maps: replace a full interactive map on every page with a static image linking to directions.
- Tracking pixels from ad platforms you no longer use.
- Social media feeds embedded on the homepage.
- Pop-ups and coupon overlays, which also cover the phone number on small screens.
Response time on taps
A page can look loaded and still feel broken when a visitor taps 'Call' and nothing happens for half a second. That is what Interaction to Next Paint captures. Google rates 200 milliseconds or less as good and more than 500 milliseconds as poor[4]. Heavy scripts are the usual culprit, so the script audit above fixes most INP problems on contractor sites too.
Source: web.dev (Google), 2026[4]
Show the data
| Item | Value |
|---|---|
| Good (at or under) | 200 ms |
| Poor (over) | 500 ms |
Hosting, themes and site builders
If the server takes a long time to send the first byte of the page, nothing you do with images will rescue the first screen. Contractor sites often sit on the cheapest shared hosting plan, chosen years ago, alongside thousands of other sites. Multipurpose themes that promise every possible layout also tend to load code for features you never use.
When you next review the site, ask your web provider three questions: how quickly the server responds for visitors in your area, whether pages are cached and served from a content delivery network, and how much code the theme loads on a simple page. If the answers are vague, test a lighter theme or a better host on a copy of the site before switching.
How to test
- Use a mid-range phone, not the newest model, on mobile data rather than wifi.
- Load your homepage, an emergency page and your top service page. Time how long until the phone number is visible and tappable.
- Run the pages through a free page speed testing tool that reports field data from real visitors where available, and note the three metrics for mobile.
- Watch for anything that jumps while loading, especially buttons.
- Tap the phone number, the text button and the booking button, and note any delay.
- Repeat after every change to the site, and monthly even when nothing has changed.
Example: a slow homepage
Example (fictional): a five-truck shop's homepage opens with a full-screen video of a truck driving through town, a slider of three coupons, two chat widgets and a live review carousel. On a mid-range phone over mobile data, the phone number appears after a long wait and the coupon slider pushes it down twice while loading.
The owner replaces the video with a compressed team photo, removes the slider and one chat widget, swaps the review carousel for a static rating badge, and gives the remaining banner a fixed height. The phone number now appears with the first screen and stays put. Field data in the speed tool takes several weeks to update, but calls from the website rise in the first month, which is the number the owner cares about.
Keep it fast
- Make one person responsible for approving any new script or widget, with a speed check before and after.
- Compress photos before every upload, including job photos added each month.
- Recheck the three metrics monthly on your top pages.
- When you redesign, put speed in the brief, with the Google thresholds as targets.
Speed is one item on the website must-haves checklist. Fast city pages also need real content; see city pages without thin content. For the listings that send traffic to your site, see NAP citations, and if lead sites are part of your mix, read whether Angi, Thumbtack and similar sites are worth it.
Frequently asked questions
How fast should a plumbing website load on mobile?
Google's guidance for a good experience is main content within 2.5 seconds at the 75th percentile of page loads; over 4 seconds is rated poor[2][4].
What slows down most contractor websites?
Large hero images or videos, image sliders, multiple chat and review widgets, unused tracking scripts and slow hosting.
Do I need a developer to speed up my plumbing site?
Not for the first fixes: compressing images, removing sliders and unused widgets, and putting the phone number in text. Slow hosting or a heavy theme may need professional help.
Does site speed affect calls?
A slow first screen hides your phone number from visitors who are ready to call. Measure calls from the website before and after speed fixes.
References
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) โ
web.dev (Google) (2026). Web Vitals (opens in a new tab) โ
U.S. Census Bureau (2023). County Business Patterns 2023, U.S. national file (cbp23us) (opens in a new tab) โ
web.dev (Google) (2026). How the Core Web Vitals metrics thresholds were defined (opens in a new tab) โ