The homepage owes an arrival window before it owes a story
The first question is when someone can be at the house, not how long you have been in business.
Put the answer where the eye lands. Service area in plain suburb names, hours, whether you take emergency calls tonight, and a phone number that dials on tap.
Founding year, family owned, photos of the truck: all fine, all below the fold. Those confirm a decision. They do not cause one.
Be specific about time in a way you can keep. Same day where the schedule allows is honest. A hard promise you break on a Friday afternoon costs more than the vague version ever would have.
One primary action per screen. A number for urgent work and a form for planned work is two actions, not five, and on mobile the urgent one comes first.
After ten at night your website is the dispatcher
A large share of emergency demand arrives when nobody is in the office, and the site is what handles it.
Say plainly what happens after hours. Whether the phone reaches a person, whether there is an after hours rate, whether a form sent at midnight is seen before morning.
Vagueness loses the job. A homeowner in Marietta at eleven at night calls three numbers and stays with whoever tells the truth fastest.
If you use an answering service, make the site match what the service actually says. Mismatched promises turn into complaints and credits.
Keep the after hours path usable with one thumb. A tap to call button pinned to the bottom of the screen is not a design compromise. It is the whole point.
Ask which side of the Perimeter the house is on, and where the shutoff is
The inquiry form should capture what a dispatcher needs to route the truck and stock it, and nothing else.
Ask for the full service address rather than a city. Routing here turns on whether the run crosses I-285 and at what hour, and a city name alone does not settle that.
Ask what the problem is in the customer's own words, whether water is running right now, and whether they know where the main shutoff is. The last question changes the urgency of the callback and gives your intake person something genuinely useful to say.
Ask about the structure: slab, crawlspace or basement, and roughly when the house was built. Truck stock and time estimates depend on both.
Do not ask for anything you will not use. Every extra field is another chance to close the tab. Photo and short video upload is the exception, because an image saves a trip more often than it costs one.
Cut the hero video, because the call comes from a driveway on one bar
Speed on a weak mobile signal is a booking problem, not a technical scorecard.
A background video, a chat widget, three tracking scripts and a webfont loader each cost a second. Seconds decide everything on a phone in a basement, a utility closet, or a shaded yard under heavy tree canopy.
Cut the video. One compressed photo does the same job. Serve properly sized images, defer anything not needed to paint the first screen, and check the result on a real phone away from the office wifi.
Chat widgets are the usual offender. If yours is not staffed by a human who can book a job, it is buying you nothing and costing you speed.
Test on an inexpensive Android handset, not a new phone on a fast connection. The gap between those two devices is where bookings quietly disappear.
A 1940s Decatur bungalow and a new Johns Creek build need different doors
The two dominant house types in this market arrive with different problems and want different reassurance.
Older intown houses bring galvanized supply, cast iron waste, previous owner improvisation, tight crawlspaces and a sewer lateral running under mature roots and red clay.
Newer suburban houses bring fixture failures, water heater age, pressure regulators and an owner who wants a warranty and a clean floor.
Give each a labeled path from the homepage. Two clear entry points beat one page that tries to reassure both readers and convinces neither.
Match the photography. Pictures of a new subdivision on a page written for a prewar intown house tell the reader you have never worked on a home like theirs.
Put a range and a trip fee on the page, or the phone repeats it all day
Price silence is the most common reason a plumbing visitor leaves without calling.
Every visitor is trying to work out whether you are expensive. If the site will not address it, they either call to find out or they do not call at all.
You do not have to publish fixed prices. Publish how you charge: flat rate or hourly, what the diagnostic or trip fee is, and whether it is credited toward the work.
Give ranges for the common jobs where a range is honest, and say plainly what moves it. Access, age of the system, and whether a permit and inspection are likely, which generally varies by jurisdiction and is worth confirming with the local building department.
The trade off is fewer conversations that were only ever about price, and more callers who accepted the number before they picked up the phone.
Questions we actually get
- What belongs above the fold on a plumbing homepage?
- Trade, coverage in named suburbs, whether you handle emergencies now, and a tappable phone number. If a visitor has to scroll to learn whether you come to their part of the metro, the page has already lost some of them.
- Should the inquiry form be short or detailed?
- Short, with the few fields that change dispatch. Full service address, the problem in their own words, whether water is running now, structure type, and photo upload. Anything that does not change what the truck carries or when it leaves should be cut.
- Do we need separate pages for each suburb we serve?
- For the towns you genuinely dispatch to, yes, and they should say something real about the housing and the work there. For towns you rarely reach, no, because a page that ranks in a place you cannot serve creates calls you have to turn down.
- How fast does the site need to be?
- Fast on a weak mobile connection, which is a stricter bar than fast on office wifi. Practically that means no background video, few third party scripts, right sized images, and testing on a mid range Android phone on cellular rather than in a browser on a desktop.
- Is it safe to publish prices?
- Publishing how you charge and a trip fee is usually safe and helps. Publishing hard prices for jobs where access and system age swing the cost is where owners get burned. Give ranges where a range is truthful, say what changes it, and never let the site diagnose a specific property.
