Why I Build Hand-Coded Websites Instead of WordPress
Every so often, a potential client asks me some version of the same question:
“Why don’t you just use WordPress?”
Completely reasonable thing to ask. WordPress is everywhere. Plenty of developers swear by it, and there’s no shortage of perfectly functional sites built on it. No argument there.
But when I sit down to build a marketing website for a small business, I almost always reach for something else. Specifically, a modern framework like Astro. It’s not a contrarian thing. It’s a deliberate call I’ve thought through a lot, and the short answer is this: most small business websites built on WordPress kind of suck. Here’s the longer answer.
WordPress assumes you need more than you do
WordPress was built to manage content at scale. User accounts, publishing workflows, editorial hierarchies, comment systems. It’s genuinely impressive software for that use case.
But most small business websites aren’t trying to do any of that. They need to explain what the business does, build some trust, rank on Google, and get people to pick up the phone or fill out a form.
Using a full database-backed CMS with a plugin ecosystem for that job is a bit like showing up to assemble flat-pack furniture with an entire workshop. You can make it work, but it’s overkill and you’ll spend half the day setting up tools you don’t need.
Slow websites lose customers. It really is that simple.
Frameworks like Astro output pre-built static files: actual HTML and CSS that loads directly in the browser without any server-side processing happening in between.
WordPress, by contrast, builds each page on the fly. Add a handful of plugins and a bloated theme into the mix, and that process adds up. It might not be catastrophic on day one, but it compounds over time.
The difference shows up in Core Web Vitals, which Google uses as a ranking signal, and in how the site actually feels to use. Fast sites convert better. Slow ones don’t. A website that takes four seconds to load on mobile is a website that doesn’t work.
Plugins are technical debt in disguise
I’ve seen WordPress sites that need a plugin to manage the plugin that handles the feature the theme doesn’t support natively. Every one of those plugins needs updating. Sometimes those updates break things. Sometimes the plugin author just stops maintaining it entirely and you’re left holding a ticking time bomb inside your own website.
None of it is catastrophic on its own, but it stacks up into ongoing work the client never signed up for. Quiet maintenance costs. Surprise breakages. The occasional frantic Friday afternoon where something inexplicably stopped working and nobody knows why.
Less of that, please.
“Hand-coded” doesn’t mean trapped
There’s a version of this conversation where someone assumes hand-coded means fragile or un-transferable. It’s actually the opposite.
A site built with Astro compiles down to plain HTML, CSS, and JavaScript. Those files run on virtually any web host on the planet. No license to maintain, no CMS installation to migrate, no proprietary database format to untangle.
What I keep is my internal development framework, the components and workflow I’ve built up that let me work consistently and quickly. That’s my tooling, the same way any agency keeps their internal processes in-house.
But the client owns the actual website. Domain, hosting, content, production files. Full stop.
I’d rather build something that doesn’t need constant babysitting
The WordPress pitch often leans on portability: “Any WordPress developer can take this over if needed.” Fair enough.
My pitch is that you shouldn’t need someone to take it over every five minutes. The goal is a site that’s stable, fast, and low-maintenance by design, with a developer (me) who’s available when something genuinely needs attention.
For most small businesses, that reliability is worth more than theoretical portability.
To be fair, WordPress has its place
Straight up: I’m not anti-WordPress. For the right project it’s genuinely the right tool. Complex editorial workflows, membership platforms, large e-commerce operations with lots of custom logic. WordPress can handle that well and I’d say so.
But for a clean, fast marketing site that needs to perform well in search and not fall apart six months after launch? The overhead usually isn’t worth it.
The short version
We build with modern frameworks because they produce faster, leaner, more stable websites with less ongoing maintenance baggage. That’s not a flex. It’s just what actually works.
No WordPress. No page builders. No plugins quietly plotting against you at 2am. Just websites that don’t suck.
If you want to talk through what that looks like for your project, get in touch. No pitch, just an honest conversation about what would actually serve your business.