WordPress runs a big slice of the internet, so it’s the default answer most people reach for. It’s not a bad tool — but “popular” and “right for your business” aren’t the same thing. Having built sites both ways, here’s an honest look at the trade-offs so you can choose well.
What WordPress is good at
Let’s be fair to it. WordPress earns its popularity:
- Huge ecosystem — a plugin for almost anything.
- Familiar — lots of people have used the dashboard before.
- Fine for content-heavy sites — if you’re publishing constantly and need a big editing team, it can suit.
For the right project, it’s a perfectly sensible choice.
Where WordPress tends to struggle
The problems usually show up over time, not on day one:
Speed
A typical WordPress site loads a heavy theme plus a stack of plugins on every page. That bloat makes sites slower — and speed affects both your Google ranking and how many visitors stick around. You can optimise it, but you’re often fighting the platform.
Maintenance and updates
WordPress core, your theme and every plugin need regular updates. Skip them and things break or become vulnerable. Keep up with them and an update occasionally breaks something else. Either way, it’s ongoing upkeep.
Security
Because it’s so widespread, WordPress is a constant target. Most hacks come through out-of-date plugins. It’s manageable with discipline, but it’s a real, ongoing responsibility.
Plugin sprawl
Every bit of functionality tends to mean another plugin — another thing to update, another potential conflict, another performance hit. Sites accumulate this weight quietly until they feel sluggish and fragile.
What a custom-built site does differently
When I build custom (using modern tools like Astro), the site only contains the code it actually needs — nothing more. That changes a few things:
- Much faster load times, because there’s no bloated theme or plugin stack.
- Far less to maintain — no constant plugin update treadmill.
- A smaller attack surface, so fewer security headaches.
- Built exactly around your goals, rather than bent to fit a template.
The trade-off is honest: a custom site usually costs a bit more upfront and isn’t a drag-and-drop dashboard. So the right choice genuinely depends on your situation.
So which should you choose?
A rough rule of thumb:
- WordPress can make sense if you publish large volumes of content daily with a team, and that workflow is central to your business.
- A custom build usually wins if you want a fast, low-maintenance, secure site that’s built to convert local visitors into customers — which is most small businesses.
For the kind of businesses I work with — trades, local services, ambitious small companies — custom almost always comes out ahead, because they want a site that quietly does its job and doesn’t become a second job to look after.
Not sure which fits you? Get a free, no-obligation site audit and I’ll give you a straight answer based on what your business actually needs — not what’s easiest to sell.
Want a website that actually pulls its weight?
Get a free, no-obligation site audit and an honest take on what your business needs.
Get a Free Site Audit →