Why We Don't Build WordPress Sites in Durango (And When You Should Use One Anyway)

We did a site audit last year for a business that had been with their agency for three years.

The site had 51 plugins installed. Eleven of them hadn't been updated in over six months. The page load time on mobile was 4.8 seconds. Two weeks before we looked at it, a plugin conflict had taken the contact form offline — the owner found out because a customer mentioned they couldn't reach her. The agency hadn't noticed.

The site was built on WordPress.

We're not here to bury WordPress. It powers roughly 43% of the internet, and that number isn't an accident — there are real reasons it took over. But there are also real costs that most Durango agencies don't tell you about when they quote you a WordPress build, and there are real situations where WordPress is still the right call.

This is the honest version.

Why WordPress Took Over

To understand why WordPress has problems, you have to understand why it was so good.

In 2003, publishing something on the internet required technical knowledge most business owners didn't have. Coding, server configuration, database setup — the web was built for engineers. WordPress changed that. It gave non-technical people a way to manage their own content: update a page, publish a blog post, add a photo, without touching code.

That was revolutionary. For a decade, it was the best tool available for small businesses who wanted a web presence they could actually run.

The plugin ecosystem made it even more powerful. Somebody built a WordPress plugin for nearly every feature you'd ever need — e-commerce, booking systems, SEO, memberships, contact forms, analytics. You didn't need a custom build. You just needed the right plugins. At its peak, this flexibility was WordPress's defining advantage.

The internet kept moving. WordPress moved with it — but the weight of twenty years of backward compatibility, plugin dependencies, and an aging architecture came along for the ride.

The Four Costs Most Agencies Don't Itemize

When an agency quotes you a WordPress build, the proposal usually leads with the features and the price. Here's what tends not to show up until later.

Security. WordPress is the most attacked CMS on the internet, not because it's particularly insecure by design, but because it's everywhere. When you build a tool that powers 43% of websites, hackers optimize for it. The plugin ecosystem — the same one that made WordPress flexible — is also the primary attack surface. A vulnerability in a popular plugin can compromise hundreds of thousands of sites at once. Your site included. Staying secure on WordPress means constant vigilance: plugin updates, theme updates, PHP version management, security scanning. Most small business owners don't do all of that. Most agencies don't remind them to.

Performance. Out-of-the-box WordPress is slow. Every page request hits a database. Plugins add overhead. Themes add scripts. The fix is caching — storing static versions of your pages so the server doesn't have to rebuild them on every visit. Caching plugins work, but they add another layer of complexity and another thing to break. The site we audited loaded in 4.8 seconds on mobile. Google starts penalizing sites in search rankings at around 3 seconds. Under 1 second is where conversion rates stop taking a hit.

Maintenance. WordPress requires active upkeep. Core updates, plugin updates, theme updates — and they don't always play nicely with each other. A plugin update can break your layout. A PHP version change required by your host can make plugins incompatible. We've seen perfectly functional WordPress sites go down because a hosting provider upgraded their server environment and three plugins stopped working. Maintenance isn't a set-and-forget task. It's a recurring cost — in time, in money, or both.

Hand-off. This is the one most agencies don't mention at all. The WordPress dashboard looks friendly — until something breaks and you have to figure out why. Every client who's "comfortable editing their own WordPress" has a story about the day they accidentally published a half-finished draft to the homepage, or moved the wrong block and couldn't get it back, or clicked update and watched their site go blank. The promise of editability is real. The reality of it is messier than the demo.

The flexibility that made WordPress powerful is also what makes it expensive to maintain.

What "Modern Stack" Actually Means If You're Not a Developer

When we say we don't build WordPress sites, the next question is usually: "What do you use instead?"

The honest answer is: it depends on what you're building. Here's what the options actually mean for a business owner — no jargon.

Next.js on Vercel. Next.js is the framework we use for most client websites. The short version: instead of your site being rebuilt by a server every time someone visits, it's pre-built — the pages are ready before anyone asks for them. The result is a site that loads in under a second, has almost no attack surface (there's no database exposed to the internet, because the build happens before it goes live), and costs nearly nothing to host for most business-size traffic. Vercel is the hosting platform built for it — deploys in 30 seconds, scales automatically, and the site goes in your account under your control from day one.

Shopify. For e-commerce, we build on Shopify — not WordPress with WooCommerce bolted on. Shopify is purpose-built for selling. It handles payment processing, inventory, shipping integrations, and the security requirements of taking money online, without requiring a plugin stack you have to babysit. It's also built to be edited by the business owner — the theme editor is genuinely usable. When Kahlil's client Reins Western Goods needed a digital store that matched the brand and actually converted, we built it on Shopify. Custom sections, brand-true product pages, launched into revenue in its first month.

Headless setups. For clients who need a lot of content editors or very complex content structures, there's a middle path: a modern CMS (Contentful, Sanity, Notion-based) connected to a custom front-end. You get the editorial flexibility of a CMS without the security and performance costs of WordPress serving the site itself. This is less common for small businesses, but it's the right call when the team publishing content is larger than one or two people.

None of these are harder to edit than WordPress. In many cases they're easier — because the editing interface is purpose-built instead of a generic dashboard with 51 plugins stacked on top of it.

The Honest Side-by-Side

Same business. Same five pages. Here's how the two approaches compare on the things that actually matter:

Load time. A well-optimized WordPress site with good caching: 1.5–3 seconds. A Next.js site on Vercel: 0.2–0.8 seconds. The difference matters for SEO and for conversion — visitors who wait more than 3 seconds leave at dramatically higher rates.

Security surface. WordPress: a live database, a public-facing admin login at /wp-admin, and however many plugins you've installed, each with its own vulnerability history. Next.js static build: no exposed database, no admin login endpoint, almost nothing to attack at the server level. This doesn't mean it's impenetrable — nothing is — but it's a fundamentally smaller target.

Hosting cost. WordPress needs a server running around the clock, with enough resources to handle database queries and plugin overhead. Decent managed WordPress hosting runs $25–$80/month depending on traffic. Vercel for a Next.js site with normal business traffic: $0–$20/month. Shopify has a fixed monthly cost that includes hosting, security, and payment infrastructure — usually more expensive than Vercel but purpose-built for what it does.

Ongoing maintenance burden. WordPress: real and recurring. Someone needs to update plugins, monitor for conflicts, and respond when something breaks. Modern stack: much lower. The site doesn't have a plugin ecosystem to babysit. Vercel updates infrastructure automatically. The main maintenance task is keeping dependencies in the codebase current — which, for a five-page business site, is quarterly at most.

Editability. This one is genuinely close, and it depends on the CMS layer. WordPress has a real advantage here for teams who are already comfortable in it. A Next.js site with a visual CMS layer (we've set these up with Sanity and with Notion-based systems) can be just as easy to edit — sometimes easier. The difference is that on WordPress, you're editing inside a system with 51 plugins. On a modern stack, you're editing inside a tool built for exactly what you need.

When WordPress Is Still the Right Answer

We're not going to pretend there are no good reasons to use WordPress. There are.

You have a large existing blog with years of content. Migrating a hundred posts, all their URLs, their categories, their internal links, their comments — that's real work. If the site is running fine and the content is the main asset, the migration cost usually outweighs the performance gain. SEO equity lives in URLs. Moving them is a risk even when you do it right.

Multiple people publish content regularly. WordPress's editorial workflow — draft, review, publish, schedule — is genuinely mature. It was built for newsrooms and content teams. If you have five people contributing content every week, WordPress's admin experience is hard to beat without a dedicated headless CMS setup.

You have a specific plugin you genuinely can't replicate. A few WordPress plugins are deeply functional, well-maintained, and have no real equivalent in other ecosystems. If your business process depends on one of those, evaluate the full tradeoff before migrating.

The site works and you're not growing into its limitations yet. If your WordPress site loads fast, stays secure, and you can edit it without issue — leave it alone. We don't recommend migration for its own sake. We recommend it when the cost of staying on the old tool outpaces the cost of moving to a better one.

The question isn't whether WordPress is bad. The question is whether it's still the right tool for the job you're asking it to do.

If You're Already on WordPress and Ready to Leave

The two most common migration paths we've seen work well:

The LePlatt's Pond model. Krii had a site that was working against her — hard to update, not built to her brand, eating time she didn't have. We rebuilt it clean: a fresh foundation, right technology for the job, handed over with full training. By the end of the first session, she was editing her own content using AI tools she'd never touched before. The migration wasn't just a technical move. It was a capability transfer. She left the project more dangerous on her own than she'd been before. That's the LePlatt's Pond story.

The Mortenson Ranch model. Sometimes the right move isn't a static site rebuild — it's a purpose-built platform for what the business actually does. Mortenson Ranch needed e-commerce, a booking flow, and an editorial "our story" experience that matched the brand of a real working ranch. WordPress with WooCommerce would have been five plugins held together with crossed fingers. Custom Shopify gave them infrastructure built for selling and a front-end built for storytelling — both in one place, both editable, both owned by them. See Mortenson Ranch.

The question to ask before any migration: what's the cost of staying on what I have, and what's the cost of moving to something better? Not just the one-time build cost. The ongoing maintenance, the performance tax, the time you spend on it or paying someone else to. When that math tips, it's time.

More on how we think through technology decisions for Durango businesses at /services, and we cover the "what platform do I actually need" question in the FAQ.

The Part That's Actually About You

Here's the thing about the WordPress debate that most think pieces get wrong: it's not a religious war and it's not really about the technology.

It's about total cost of ownership, long-term editability, and whether the tool you're on still serves the business you're becoming.

Most Durango businesses landed on WordPress because it was the default choice in the year they built their site. Not because someone looked at the alternatives, weighed the tradeoffs, and made a case for it. It was just what the agency used. What the freelancer knew. What the tutorial was written for.

That's fine for where you were. The question is whether it's still the right answer for where you're going.

If you're not sure — if your site has been slow and you've been told "that's just WordPress," or if your maintenance fees are creeping up and you're not sure what you're getting for them — we'll give you a straight answer. Not a pitch. Not a proposal. An honest read on whether the platform you're on is the problem, or whether the problem is something else entirely.

That conversation starts at /contact.

Not ready to reach out yet? Start with the Brand World Blueprint — a free 14-page guide that scores your brand across five pillars. The clearest picture you'll get of where you actually stand without paying anyone anything.