The web-development mistakes that quietly cost Norfolk businesses jobs
Most local sites aren't broken in ways the owner can see. They look fine on the laptop the owner built them on. The damage shows up on a customer's phone, on a weak signal, at the exact moment they were deciding whether to call — and the owner never finds out, because a lost visitor doesn't fill out a form to complain. Here are the specific traps I see over and over in Hampton Roads, and how to sidestep them.
The first is building the whole site on a heavy drag-and-drop platform and then loading it up. A slider here, a chat widget there, a font from one service, analytics from three others — each one seems harmless, and together they turn a two-second page into an eight-second one. On desktop nobody notices. On a phone near the piers or inside base housing where the signal is thin, that page never finishes loading and your customer is already dialing the next result. The fix isn't a faster host; it's fewer moving parts. Build lean, add a script only when it earns its place, and test on a real phone throttled to a bad connection, not on office wifi.
The second mistake is treating the site as a brochure instead of a conversion tool. A gorgeous homepage with the phone number buried in a header nobody scrolls to, no click-to-call, a contact form with eleven fields — these are self-inflicted. A Norfolk buyer comparing three businesses will book whoever makes it easiest. Tap-to-call in thumb reach on every screen, a short form, and a clear next step beat a beautiful site that hides the ask.
The third is neglecting the technical plumbing that lets Google read the site at all. Missing or duplicated page titles, no local schema, images with no alt text, a sitemap that was never submitted — invisible to a visitor, but they're the difference between ranking and not. This is the quiet foundation under any search work you do later; skip it and you're paying to rank a house with no foundation.
- Building on a bloated template, then piling on scripts until the phone experience crawls
- Hiding the phone number and burying the call-to-action below the fold
- Skipping technical SEO — titles, schema, sitemaps — so Google can't rank the pages
- Never testing on a real, throttled phone, so slow-signal Norfolk customers silently bounce
The through-line is that none of these mistakes announce themselves. The site "works," so nobody investigates why the phone isn't ringing. The fix isn't a redesign for its own sake — it's building with the phone, the weak signal, and the search engine as the three constraints that actually decide whether the site does its one job. If you want a second set of eyes on where your current site is leaking, that's the first thing I look at.