When most people decide to build a WordPress site, picking a theme feels like the obvious first step. Browse a marketplace, find something that looks close enough, and start customising. It’s how WordPress has worked for years, and for a long time, it was a reasonable approach.
But a pre-built theme isn’t a neutral starting point. It’s a decision that shapes everything that comes after, including how fast your site loads, how much you can customise it, and how much code you’re carrying around for features you’ll never use.
For a lot of small businesses, it’s the wrong starting point entirely.
What a WordPress Theme Actually Does
A theme controls how your WordPress site looks and behaves: layout, typography, colours, page structure. That much is straightforward.
What’s changed is the landscape around it. WordPress now supports block themes, built on the native block editor, which are significantly leaner than their predecessors. A default theme like Twenty Twenty-Four carries almost no bloat because the design is handled natively rather than through a separate framework.
The problem is that the marketplace is still dominated by old-school multipurpose themes. These ship with built-in page builders, demo content, sliders, portfolio sections, and dozens of other features bundled in, whether you want them or not. Every one of those features adds code that loads on every page visit, whether it’s being used or not.
This is the overhead problem. You pay for a theme that does a hundred things. You use five of them. The other ninety-five are still there, quietly slowing your site down and complicating every update.
When a Pre-Built Theme Is a Reasonable Choice
Themes aren’t always the wrong answer. There are situations where they make sense.
If you’re running a straightforward site on a tight budget, need to manage content yourself, and aren’t particularly concerned about squeezing out maximum performance, a well-chosen lightweight theme is a perfectly reasonable call. Something like GeneratePress or Kadence, or one of WordPress’s native block themes, fits this description. Minimal, well-supported, not dependent on a heavy page builder.
The keyword is lightweight. A theme that installs cleanly, doesn’t bundle features you didn’t ask for, and lets WordPress do what WordPress does well is a different thing entirely from the bloated multipurpose themes that dominate the popular charts.
If that’s the category you’re in, a good theme chosen carefully is fine. The issue is that most people don’t choose carefully. They choose by screenshot.
When a Pre-Built Theme Is the Wrong Tool
The overhead problem becomes a real liability in a few specific situations.
When performance is your top priority. If your site is slow, a heavy theme is often the anchor holding it back. Stripping out unused features from a pre-built theme is harder than it sounds. In many cases, it’s easier to start fresh than to undo what a theme has already done.
When your brand requires a truly custom identity. Pre-built themes are designed to be flexible enough to suit anyone, which means they aren’t designed specifically for you. Getting a theme to reflect a distinct brand often involves fighting the theme’s assumptions at every turn. The result is a site that looks almost right, but never quite.
When updates keep breaking your design. This happens more than it should. A theme update ships, conflicts with a plugin or your customisations, and suddenly your site looks wrong or stops working. The more you’ve customised a pre-built theme, the more exposed you are. It’s a maintenance risk that compounds over time.
When WordPress itself might not be the right platform. Sometimes the real answer isn’t a better theme — it’s questioning whether WordPress is the right tool at all. A static site generator like Astro doesn’t use themes in the traditional sense. Pages are built from components, custom to your site, with no unused code shipped by default. The performance difference can be significant.
What the Alternatives Actually Look Like
Path 1: A custom-coded WordPress theme. Instead of buying a bloated marketplace theme, a developer builds a lean, custom theme exclusively for your business. You still get the familiar WordPress dashboard your team already knows, but with zero unnecessary code underneath it. It won’t break on updates because you own the codebase, not a third party.
Path 2: Going headless. This is where WordPress steps back to become a content management tool only. Your team edits content in the WordPress admin as normal. But the front end — what visitors actually see and load — is built separately, using a static site generator like Astro. No theme overhead at all. At Hobart Website Design, this is how we build most sites now. The performance and flexibility gains are significant enough that it’s become our default recommendation for businesses where those things matter.
Neither path is right for every situation. But both are worth understanding before you default to a theme marketplace.
A Quick Decision Framework
Before committing to a pre-built theme, ask yourself:
If you’re not confident in the answers, it’s worth a conversation before you commit.
Have a project in mind or just want a second opinion on your website? We'd love to hear from you.
