Is Your Contractor Website Too Slow? How to Find Out

The homeowner is standing on a wet basement floor at ten at night. Water is coming through the cold joint, the carpet is gone, and they are on their phone with one bar of cell service. They search, they tap the first three results, and they call whichever page loads first.

That is the whole argument. Your site is not being compared to nothing. It is being compared to two other waterproofing companies in the same tab strip, on a bad connection, by somebody who has no patience left. Slow does not read as slow. It reads as broken.

Why speed matters more for a contractor than for most businesses

Your traffic arrives at the worst possible moment, on the worst possible connection.

Nobody researches foundation repair from a desk over a leisurely week. They notice the stair-step crack, or the mold smell, or the water, and they look it up right then, standing where the problem is. Basements have terrible signal. Crawl spaces have worse. The phone drops off wifi and onto cell data exactly when the search happens.

Compare that to a business whose customers browse at home on fibre with a laptop. Same website, completely different experience. A page that feels fine in your office is being served to somebody at the bottom of a set of stairs.

The second thing is that they are comparison shopping in parallel. Three tabs open, three companies. They do not evaluate your load time in isolation and decide it is acceptable. They close the one that is still spinning while another one is already showing a phone number. You never appear in any report as a lost job. You just never existed.

How to measure it instead of guessing

Do not test on your office wifi. That is the single most common mistake, and it is why owners think their site is fast.

Your site is cached on your own devices. You have visited it a hundred times, so your phone and your desktop already hold most of it, and you are sitting fifty feet from a router on a business connection. You are the least representative visitor your website has.

Two ways to get an honest number:

The phone test. Take your own phone, turn wifi off so you are on cell data, open a private or incognito browsing window so nothing is cached, and type your company name into Google. Tap through to your site the way a homeowner would. Count out loud. One thousand one, one thousand two. Do it from a job site, not from the shop. That number is what you actually ship.

PageSpeed Insights. Google runs a free tool at pagespeed.web.dev. Paste your homepage URL in. Ignore the coloured score out of 100, which is a lab simulation, and look at the section reporting field data from real Chrome users if your site has enough traffic to show it. That section is what real people on real phones experienced over the last 28 days. Read the mobile tab. The desktop tab flatters everyone.

Test the homepage, your main service page, and one job photo gallery. Galleries are usually the worst page on the site and the one nobody checks.

Core Web Vitals in plain English

Core Web Vitals are three measurements Google publishes to describe how a page feels to use. There are only three, and one of them is almost always the one breaking on a contractor site.

Largest Contentful Paint. How long until the biggest thing on the screen actually shows up. Usually your hero photo or your headline. This is the one that breaks. It is the “why is this still white” measurement.

Interaction to Next Paint. When somebody taps something, how long before the page visibly responds. This replaced an older metric called First Input Delay in 2024.

Cumulative Layout Shift. How much the page jumps around while it loads. The homeowner goes to tap your phone number, a photo finishes loading above it, everything slides down, and they tap a link to your privacy policy instead.

Google’s published thresholds, current at the time of writing and subject to change, are 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift, measured at the 75th percentile of visits. That last part matters: you are graded on the visitor having a bad day, not the average one.

On contractor sites, Interaction to Next Paint and layout shift are rarely the issue. Largest Contentful Paint is, and the reason is almost always photographs.

The usual culprits, in the order they usually cause it

Roughly ordered by how often each one turns out to be the cause.

Enormous unresized job photos. A photo straight off a modern phone camera is commonly several megabytes, and it goes onto the site at full size because nothing in the process resizes it. Put a dozen of those on a gallery page and the homeowner on one bar of cell service is downloading all of it before they see anything. This is the answer most of the time.

A page builder loading everything at once. Drag-and-drop builders ship the code for every feature they support, whether your page uses them or not. You built a simple page. The visitor downloads the whole toolbox.

Embedded widgets. The review carousel pulling live from Google, the chat bubble, the booking calendar, the Facebook feed. Each one is a separate piece of someone else’s site loading inside yours, and each one can be slow independently of anything you control.

Video backgrounds. A looping clip of a crew pouring a slab behind your headline is the most expensive decoration available. It is also usually autoplaying, muted, and ignored.

Fonts and tracking scripts. Four font weights nobody can tell apart, plus analytics, plus a pixel, plus a heatmap tool somebody installed in 2022 and forgot.

Fix them in that order. The first one is usually most of the problem.

Your job photos are the biggest cause, and fewer photos is not the fix

This is the contractor-specific version of the problem, and it has a trap in it.

Your job photos are the most valuable thing on your website. The bowing wall before and after the carbon fibre straps. The open trench along the footing. The black mold behind the drywall and the same wall finished. Homeowners scroll those and nothing else. A waterproofing site with real photographs beats a prettier one with stock images every time.

Those same photos are also why the site takes nine seconds to load.

The wrong conclusion is to cut down to four photos. The right one is to keep all forty and stop serving them at full camera resolution. A photo displayed 800 pixels wide on a phone does not need to be 4,000 pixels wide in the file. Resized and properly compressed, the same image can be a fraction of its original size with no visible difference on the screen it is being viewed on. Lazy loading handles the rest: images further down the gallery only download when somebody scrolls to them.

You should never have to choose between a fast site and showing your work. If somebody tells you to delete job photos for speed, they are solving their problem, not yours.

Which fixes are worth doing yourself

Some of this is genuinely a fifteen-minute job.

Resizing photos before you upload them is the one to own. Set a habit: every photo that goes on the site gets exported at a sensible width first. Your phone can do it, your laptop can do it, and it stops the problem coming back every time a crew sends in new work. Removing widgets you do not use is the other one. The chat bubble nobody answers, the Facebook feed, the tracking script from a vendor you fired.

Leave the rest alone. Image formats, lazy loading, caching, deferring scripts, what the page builder ships: those are not settings, they are how the site is built. Half-following a tutorial into your live site at nine at night is a good way to turn a slow website into a broken one. That layer is where properly built high-converting websites for contractors either hold up or do not, and it is decided long before you get the login.

When speed is not the problem

Speed is the easiest thing to blame because it produces a score, and a score feels like an answer.

If your site loads in three seconds on cell data and the phone still is not ringing, speed is not your problem and making it two seconds will not change anything. The far more common causes are that nobody can find the phone number without scrolling, the site never says which towns you cover, there is nothing proving you have done this work before, or barely anybody is landing on the page in the first place. A fast page with nothing convincing on it is just a quick disappointment. That diagnosis is a bigger subject, and it is worked through in why your website doesn’t get calls.

The test is simple. Run the phone test on cell data. If you are waiting long enough to be annoyed, fix it, starting with the photos. If the page comes up before you finish counting to three, close the speed tab and go look at what the page actually says when it arrives.