WordPress has a reputation problem. Mention it to anyone who has had a bad website experience and you will hear about the plugin that broke everything, the theme update that scrambled the layout, the page builder that made every page load in six seconds. That reputation is not entirely unfair — but it is not the full picture either.

I build on WordPress deliberately. Not because it is the default, not because every client asks for it, but because when it is built correctly it is one of the best platforms available for small business websites. Here is what “built correctly” actually means — and why it is so different from what most people have experienced.

The real source of WordPress’s bad reputation

Almost every WordPress horror story has the same root cause: page builders and off-the-shelf themes. Divi, Elementor, Avada — these tools let anyone build a website without writing code, which sounds like a feature until you realize what you are actually buying. You are buying a layer of abstraction between your design intent and the rendered HTML, a dependency on a third-party plugin for every pixel on your site, and a maintenance liability that compounds with every update.

The bloat is not WordPress. The bloat is the stack built on top of it. Strip that away and WordPress is a mature, stable, well-documented CMS with an excellent editor, a robust plugin ecosystem for the things that actually need plugins (forms, SEO, e-commerce), and hosting options at every price point.

“The bloat is not WordPress. The bloat is the stack built on top of it.”

What I do differently

Every site I build on WordPress starts with a custom theme — written from scratch, in clean PHP and CSS, with no page builder involved at any stage. The HTML I design in the browser is the HTML that ships to WordPress. There is no translation layer, no abstraction, no mystery box of auto-generated markup.

This approach has three direct benefits for clients:

  • Performance. Custom-built themes load fast because they only load what the site needs. No 400KB of page builder CSS. No JavaScript framework powering a five-page brochure site.
  • Stability. When a plugin updates and something breaks, it is because that plugin touches functionality I chose to include — not because a page builder had a bad release day and now your entire site is down.
  • Maintainability. The code is readable. If I hand the site off to another developer, they are reading standard PHP and CSS, not reverse-engineering a page builder’s proprietary data format.

The content editing experience clients actually get

One of WordPress’s strongest arguments is its editor. The block editor is genuinely good for content — well-structured, accessible, and familiar to anyone who has used a modern writing tool. For blog posts, service pages with structured content, or any page where a client needs to make regular updates, it works well.

For pages with complex, design-specific layouts — homepages, landing pages, proposal documents — I use Advanced Custom Fields to create simple, purpose-built editing interfaces. The client sees labeled fields for their headline, their bio, their testimonial. They do not see the underlying template at all. The design stays intact; the content stays editable.

When I do not use WordPress

WordPress is not always the right tool. For a simple five-page brochure site with no content management needs, a static build is faster to deliver, cheaper to host, and has zero maintenance overhead. For a project with very specific technical requirements — complex filtering, real-time data, custom application logic — WordPress may not be the right foundation regardless of how it is built.

The platform should follow the requirement. What I try to avoid is choosing a platform by default — in either direction. WordPress because everyone uses it, or avoiding WordPress because of a bad experience with someone else’s implementation.

When I recommend WordPress, it is because it is the right fit for what the site needs to do and how the client needs to manage it. That deliberateness is the difference between a site that works well for years and one that becomes a liability.