Who your mobile visitor actually is
Picture the real person. A homeowner is standing in the driveway. The AC quit, or there is water at the base of the water heater, or a shingle is in the yard after last night's storm. They pull out their phone. They are outside, in sun, on one bar of cell service, holding the phone in one hand because the other is pointing at the problem. They have maybe fifteen seconds of patience.
This is not the person a lot of contractor sites are built for. A lot of sites are built for the version of the buyer who sits at a desk with two monitors and reads a hero paragraph. That buyer barely exists in the trades. Your buyer is standing up, distracted, and half-decided already. They are not reading. They are scanning for two things: does this shop do my problem, and how do I reach them right now.
Everything else on the page is in the way of those two answers. That is the whole design principle. It is not that the desk visitor does not matter. It is that if you design for the hardest case, the driveway, the desk takes care of itself. A site that works one-handed in the sun also works fine on a laptop. The reverse is not true, which is why so many good-looking contractor sites lose the call.
The intent is different from a desk visitor's, too, and that changes the design. A homeowner searching from a laptop on a lunch break might be planning a project for spring, browsing, comparing, in no hurry. A homeowner on a phone in the driveway usually has a problem right now. They are closer to buying and shorter on patience, which is a good combination for you if the site does not waste it. The mobile visitor is often your best lead of the day, and a slow or cluttered page throws that lead away before you ever knew it existed.
One more thing about this visitor: they are often comparing. They tapped your site, and they have two competitor tabs open behind it. Whoever answers the two questions fastest gets the call, and the other two never hear from them. Speed here is not a nicety. It is the whole contest.
Speed is the first thing they judge, before a word
On a phone, on cell service, the first thing a homeowner experiences is not your copy or your photos. It is the wait. A slow site tells them something about your shop before they read a single word, and it is not flattering. If they are staring at a white screen while the water spreads, they hit back and open the next tab.
The number that matters is time to something useful on screen. We build hand-coded static sites that load under 2 seconds, and on mobile that gap is the whole game. The reason so many contractor sites are slow is not mystery, it is bloat: a page-builder theme dragging in dozens of scripts, four tracking pixels, a giant unoptimized hero photo, a chat widget, a font pack, a slider nobody asked for. Each one is fine alone. Stacked, they turn a two-second page into an eight-second page on a phone.
Here is what actually moves mobile load time, in order of payoff:
- Image weight. A single 4 MB hero photo straight off a phone camera is the most common killer. Sized and compressed right, it should be a small fraction of that with no visible loss.
- Script bloat. Every widget, tracker, and plugin is code the phone has to fetch and run. On a static, hand-coded site there is almost none of it.
- The platform itself. WordPress with a page builder ships a lot of weight before your content even loads. That is the tax you are trying to get out of.
You cannot copy your way out of a slow site. The homeowner in the driveway never reads the copy, because they are already gone. Speed is not a technical footnote here. It is the front door, and on a phone it is a narrow one.
The one-thumb rule: reach, taps, and the phone number
Watch how a homeowner holds a phone and one thing jumps out: they use a thumb, and the thumb only reaches so far. The comfortable zone is the bottom two-thirds of the screen. The top corners are a stretch. A site designed for the thumb keeps the things that matter, the number, the form button, the service they need, inside that reach.
The single most important element is your phone number, and it has to do two things. It has to be visible without scrolling, and it has to be tappable. Tappable means it is a real click-to-call link, so one tap dials, no copying, no typing. On our builds the number rides the top of every screen and a fixed call-and-text bar sits at the bottom, in the thumb zone, on every page. The homeowner never has to hunt for how to reach you, because the answer is always one tap away, top or bottom.
A few mechanics that separate a mobile-usable site from a frustrating one:
- Tap targets at least 44 pixels. Buttons and links smaller than a fingertip get mis-tapped. Fat, obvious targets, spaced apart, are a mobile requirement, not a style choice.
- Click-to-call and click-to-text both. Some homeowners call. Plenty would rather text, especially younger owners and anyone who does not want to talk while the family is around. Offer both.
- No tiny menus or hover tricks. Hover does not exist on a phone. Anything that depends on it is invisible to your busiest visitor.
The test is simple and you can run it yourself right now. Pull up your site on your own phone, one hand, and try to call yourself in one tap from the top of the page. If you have to scroll, pinch, or hunt, so does every homeowner standing in a driveway, and a good share of them will not bother.
Forms a homeowner can finish at a red light
Every field you add to a mobile form is a reason to quit. On a desk, filling out ten fields is mildly annoying. On a phone, one-handed, tapping between fields and fighting autocorrect, ten fields is a wall. Most contractor form abandonment on mobile is not lack of interest. It is the form being too long to finish standing up.
The fix is to ask for the least you need to call them back and quote the rest by phone. For most trades that is name, phone, and a one-line note about the problem. Email is optional. Address, budget, and preferred time can wait for the call. Every field past the essential three is buying you a slightly better lead in exchange for a real chance of losing the whole thing.
There is a temptation to add fields to pre-qualify, to weed out tire-kickers before you spend a minute on the phone. On a desk that math can work. On a phone it backfires, because the fields that scare off a tire-kicker also scare off the busy homeowner who was ready to book. You do your qualifying on the callback, where it costs you two minutes, not on the form, where it costs you the lead. Let the short form catch everyone and sort them out when you call.
How a mobile form should behave, not just look:
- Right keyboard per field. The phone field should pop the number pad, the email field the email keyboard. Making a homeowner switch keyboards by hand is friction you control.
- Big, spaced fields and one clear button. Fields sized for a thumb, a single obvious submit, no competing buttons stealing the tap.
- Instant, in-place confirmation. No full page reload, no bounce to a blank thank-you page that looks broken on a slow connection. The form confirms right where they are.
- A phone number as the fallback. If the form ever errors, the number is right there so the lead is not lost to a glitch.
The other half of forms is trust, and it is quick to earn: a short form next to a real service photo and a plain sentence about what happens next ("we call you back same day") converts far better than a long form floating on its own. The homeowner is deciding whether to hand a stranger their number. Short, honest, and one tap from your phone line is how you make that easy. A form that respects the driveway visitor's fifteen seconds is the form that rings your phone.
Photos and proof that load fast and prove the work
Contractors live and die on proof, and on mobile that is mostly photos: the finished roof, the clean install, the before-and-after of the driveway. The tension is that photos are the heaviest thing on the page, and heavy is exactly what kills a mobile site. The job is to keep the proof and lose the weight.
The mistake is uploading straight from the phone. A photo off a current phone camera is several megabytes and far larger than any screen needs. Ten of those in a gallery is a page that crawls on cell service, and the homeowner is gone before the first one paints. Sized and compressed properly, those same photos look identical on screen at a tiny fraction of the file size. That is not cutting corners. It is the difference between a gallery that loads and one that does not.
What proof actually earns the call on a phone:
- Your own job photos, not stock. A homeowner can smell a stock photo, and it proves nothing about your shop. One real photo of your crew's work beats ten polished stock shots.
- Before-and-after, matched. Same angle, same framing, the problem and the fix side by side. That pairing does more selling than a paragraph ever will.
- Photos that load only when needed. Images below the fold should load as the homeowner scrolls to them, not all at once up front. That keeps the top of the page fast while the proof waits its turn.
Reviews and trust marks belong here too, and the same rule applies: real and light. A couple of genuine quotes with a name and town do more than a wall of badges, and they cost the page nothing to load. The point of proof on mobile is to answer "can this shop actually do my problem" fast enough that the homeowner taps call instead of the tab behind you. Proof that arrives after they have left is proof that did not count.
What to cut: the desktop habits that sink a phone
Most of designing a good mobile site is subtraction. A lot of what looks impressive on a big screen is dead weight or an outright obstacle on a phone. Knowing what to cut is half the craft.
The usual suspects, and why they hurt the driveway visitor:
| Desktop habit | What it does on a phone | Do instead |
|---|---|---|
| Giant hero slider | Slow to load, taps get eaten, nobody swipes | One sharp photo, headline, phone number |
| Long intro paragraph | Wall of text, homeowner scrolls past or leaves | One line: trade, town, and how to reach you |
| Auto-popup or chat bubble | Covers the screen, hard to close one-handed | A visible number and a short form |
| Fancy hover menus | Invisible; hover does not exist on touch | A plain tap menu with big targets |
| Video autoplay in hero | Eats data and load time, often muted anyway | A still photo that proves the work |
There is a pattern in that list. Every item is something added to impress a person who is not your buyer, at the cost of the person who is. The homeowner in the driveway did not come to be impressed. They came to solve a problem and reach a shop. Anything that stands between them and those two things is a candidate for the cut, no matter how good it looks on the laptop it was designed on.
Cutting is also where a hand-coded site pulls ahead of a template. A template ships with all of this built in, and you spend your time fighting to turn it off. A site built by hand starts empty and only adds what earns its place, so the phone stays fast because nothing unnecessary was ever loaded onto it. The finished page is not a stripped-down version of a desktop site. It is a site built the right way around from the start, for the person actually holding the phone.