WordPress vs. custom code for a Utah business

“Should I just use WordPress?” I hear this at least once a week. It’s a fair question. WordPress is everywhere. It’s the default, and it’s what most agencies sell because it’s what they know.

But default and optimal aren’t the same word. WordPress is a great tool for some jobs and an expensive, slow, fragile choice for others. The deciding factor is narrower than most people expect.

What WordPress actually is

WordPress started in 2003 as blogging software and grew into a full content management system: a dashboard where you log in, create pages, publish posts and manage content without touching code.

Its power comes from the ecosystem — tens of thousands of plugins for forms, SEO, e-commerce, booking, image optimization, caching, security, and thousands of themes controlling how it all looks. That ecosystem is genuinely useful. If you run a content operation with several writers publishing weekly, or a store that needs inventory and payment processing, WordPress with WooCommerce is a proven, battle-tested answer.

The problem is that most Utah service businesses aren’t running content operations or online stores. They’re running plumbing companies, HVAC shops and landscaping crews, and their website needs are a different shape.

Where it costs service businesses

Speed

The average WordPress site loads in three to four seconds. That doesn’t sound catastrophic until you remember that a large share of mobile visitors abandon a page that takes longer than three.

The reason is the chain: the browser requests the page, the server runs PHP, PHP queries MySQL, the database answers, PHP assembles the HTML, and then the response ships alongside a theme framework, a page builder’s CSS and JavaScript, and scripts from a dozen or more plugins. You can mitigate all of it with caching, a CDN and managed hosting — you’re just spending time and money optimizing around a problem that didn’t need to exist. A static site skips the chain entirely.

Security

WordPress is the most-attacked CMS on the internet, and it’s not because the core is badly written. It’s because the plugin ecosystem is enormous and inconsistent. Every plugin is third-party code — some maintained by professional teams, some abandoned two years ago. When a vulnerability lands in a popular one, attackers can scan and exploit automatically before most owners know there’s a problem.

Keeping it safe means updating core, themes and every plugin, monitoring for vulnerabilities, and usually paying for a security service. A static site has no database to inject, no admin login to brute-force and no plugins to exploit.

Code you didn’t ask for

Install a popular theme, add a page builder and a handful of plugins, then view source. You’ll find thousands of lines of CSS and JavaScript the page never uses but the browser still downloads, parses and executes. Core Web Vitals measure exactly that, and it shows up in rankings.

Ongoing cost

WordPress is free. Running it is not. A typical small business site: managed hosting $240–$600 a year, theme or page builder license $50–$200, premium plugins $200–$500, maintenance $500–$1,500 if outsourced. Call it $990–$2,900 a year, every year. A static custom site hosted properly is often under $100 a year. (The fuller breakdown is in what a website costs in Utah.)

You don’t entirely own it

This one catches people. If your site is built in a page builder, your layouts and styling live in that builder’s proprietary format inside a database. Move hosts, switch tools or rebuild, and you effectively start over. With custom code, your site is a folder of HTML, CSS and JavaScript. Any editor opens it, any server hosts it, any developer can pick it up.

When WordPress is the right call

I’m not here to tell you WordPress is always wrong. It’s the better tool when:

• You have a content team. Multiple writers, editorial workflow, draft management, user roles — the CMS features are worth their weight.
• You sell products. Inventory, payments, shipping calculations and customer accounts. WooCommerce is mature and well supported.
• Non-technical staff edit weekly.If the people running the site can’t work with code and change things constantly, the visual editor is real value.

Notice the thread: in all three, the CMS is actually being used. When it is, WordPress earns its complexity and you should hire someone who builds on it well.

When custom code wins

For most of the service businesses I work with through Utah web design, the site is five to fifteen pages, gets updated a few times a year, and exists to do one job: generate leads. In that case the CMS features aren’t just unnecessary — they’re deadweight you pay for in speed, security and renewals.

Custom is the better choice when the site is small, when speed and local SEO are the point, when you want the code to be yours with no proprietary format in the middle, and when you’d rather spend nothing on maintenance. The numbers back it up: BK Toolbox shipped at 100 for SEO and 99 for performance on Lighthouse, with no plugin stack to maintain afterward.

How to decide in one question

Will someone log into a dashboard and change content most weeks?

If yes, use WordPress. It was built for that and it does it well. If no — and for most Utah service businesses the honest answer is no — you’re paying for an editor nobody opens, plus the performance, security and maintenance bill that comes with it. It’s not about which technology is better. It’s about which one matches what you’re actually doing.