Side by side
| Web design | Web development | |
|---|---|---|
| In plain words | How it looks and feels | How it works |
| Examples | Layout, colors, photos, where the call button goes | Pages that load fast, forms that send, booking and payments |
| You notice it when | The site looks dated or confusing | The site is slow, broken, or the form never arrives |
| Affects | Whether people trust you and call | Whether the site works and Google can read it |
What a local business actually needs
Not “a designer” and “a developer” as two hires. You need:
- A plan: which services and towns get a page, and what each page says.
- Design: your real photos and reviews up front, and a call button on every screen.
- Development: fast, secure pages, with forms, booking or payments that work on a phone.
- Writing: words that sound like you and answer what customers ask.
- Upkeep: someone keeping it current every month.
Most of the trouble owners have comes from the gaps between people: the designer who hands off to a developer who doesn’t write, and nobody who updates it afterward.
Tip: ask anyone you hire who writes the words. If the answer is “you”, count those hours too.
An example: one page, both jobs
Take the page a plumber needs most: emergency service. Here is who does what on that one page.
- Design decides that the phone number sits at the top in big type, that a call button stays on the screen as you scroll, and that the photo is the plumber’s own van, not a stock picture of a smiling model with a wrench.
- Development makes that call button actually dial when you tap it, makes the page load quickly on a phone in a flooded basement with one bar of signal, and makes sure the “send us a message” form lands in the owner’s inbox instead of a spam folder nobody checks.
- Writing answers what the customer is asking at 11 pm: do you come out after hours, which towns do you cover, what happens when you get here.
If any one of those is missing, the page fails. A beautiful page whose form never arrives loses the job quietly. A fast page with nothing useful on it loses it too. The same goes for a roofer’s storm damage page, an HVAC company’s furnace repair page, or a cleaner’s move-out cleaning page.
What “fast” and “works on phones” mean to Google
These are development jobs, and Google publishes the numbers it looks at. Its Core Web Vitals ask for the main content to load within 2.5 seconds, the page to respond to a tap in under 200 milliseconds, and the layout not to jump around as it loads (a shift score under 0.1) (Google Search Central).
Google also looks at the phone version of your site first. It says it uses the mobile version of a site’s content for indexing and ranking, and that only the content shown on the mobile site is used (Google Search Central). So if your service list or reviews only show on a computer screen, Google may not count them.
There is a limit to how much speed buys you. Google says it always tries to show the most relevant content, even if the page experience is poor (Google Search Central). A fast site with thin pages won’t beat a slower site that answers the question. That is why the plan and the writing matter as much as the build, and why nobody can honestly promise you a ranking. Google’s own guide says there are no secrets that will automatically rank a site first (Google Search Central).
Which one goes wrong more often?
Both, in different ways. In October 2026 we checked the websites of 409 independent Utah trade businesses, the ones Google shows in its map results for roofers, plumbers, HVAC, electricians, landscapers, painters, cleaners and more. Here is how often each kind of problem showed up:
Design and development problems on Utah trade websites
Share of 409 independent Utah trade websites with each problem. Speed results are out of 404 sites.
The development problems are the most common, and owners rarely see them, because they test the site on a fast office computer. The design problems are the ones that quietly cost calls: a visitor who has to scroll back to the top to find your number sometimes doesn’t bother. Neither list gets fixed by someone who only does half the job.
Where the line blurs
The split isn’t always clean. A few cases:
- A DIY builder. The template is the design and the platform is the development. What’s left for you is the plan, the writing and the upkeep, which is most of the work. See website builder vs. custom.
- A restaurant with online ordering. This leans on development: the menu, the order flow and the payment all have to work every time, on every phone.
- A cleaner or painter with a simple service site. This leans on design and writing: good photos of real jobs, clear prices or ranges, and pages that explain what each service includes.
- Real software. A customer portal tied to your scheduling system, or a tool your crew uses in the field, is a development project of its own. It should be scoped and quoted on its own, not slipped into a website job.
Accessibility: where design and development meet
Some customers read your site with weak eyesight, an old phone in bright sun, or a screen reader. Making the site work for them takes both jobs, and the web’s own rulebook, the W3C’s accessibility guidelines, puts numbers on it.
- Design picks colors that can be read. Normal text needs a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1 (W3C). Light gray on white often fails.
- Design sizes the buttons. Tap targets should be at least 24 by 24 pixels, or have room around them (W3C). A tiny “call” link next to a tiny “directions” link gets the wrong tap.
- Development makes it readable to machines. Photos get descriptions, form fields get labels, and the page works with a keyboard. A screen reader can’t read a phone number baked into a picture.
A plumber’s customer who can read the number and hit the button is a customer who calls.
Common mistakes when hiring
- Paying for mockups only. Some designers hand over pictures of a website. Someone else still has to build it, and that is a second bill.
- Hiring a developer and writing it yourself. The site works, but it says “Welcome to our website” and lists your services in one line.
- Never checking it on a phone. Most of the problems that cost calls show up on a phone first: a call button that doesn’t dial, a menu that won’t open, text too small to read.
- Nobody owns the upkeep. Hours change, prices change, the special from last spring is still on the homepage.
- Not asking who holds the domain and the code. If it’s not you, find out before you sign. See who owns my website.
How we handle it
One team, start to finish: research, plan, design, build, and the monthly upkeep. We’re based in Lehi and build websites for local businesses. Our founder’s whole career in IT means your site is fast, secure, and built right. The build is $5,000, one time, and it includes the research and the written plan behind the site. Looking after it is from $99 a month, month to month. You see the whole site working before you pay anything, your domain is in your name, and once the build is paid the website and its code are yours. See how to choose a web designer for the questions to ask anyone you hire, and what a website costs in Utah County for the price.
What your website really needs
0 / 5
Tap to tick. Your ticks stay on this device.