The Fire Hose for the Houseplant

A web designer told me how he spent five minutes changing the opening hours on a client's website.

The client had WordPress. Full access to the Content Management System (CMS). Could theoretically have done it himself.

In practice? He called the designer and paid for it. Had he tried it himself, it would have taken 45 minutes — just to figure out how it even works.

That wasn't a one-off. That's the pattern.

The Familiarity Trap Nobody Questions

You hear "WordPress" often enough.

Everyone uses it. So it must be what you need too.

I've seen this dozens of times. A client comes in, already decided. "I need WordPress."

The best example came from another designer's client. A real estate guy. Insisted on WordPress. Had to have it. The site went live with full CMS capabilities.

Then he emailed the designer every time he wanted to change content.

Never logged in. Never touched the CMS. Just paid someone else to do what he was supposedly able to do himself.

The tool justified itself by existing. The need never materialised.

What You're Actually Building

Most businesses update their website content two or three times a year at most.

Maybe you update your services. Add a new team member. Change your opening hours.

You're building a system designed for daily publishing — but using it only every few months. WordPress was built for blogs. For people who publish multiple times a day. The software architecture assumes a constant stream of new content.

You're using a fire hose to water a houseplant.

The overhead doesn't disappear just because you're not using the features. You're running a server. Managing a database. Maintaining software that's exposed to the internet through forms. Keeping an eye on plugin updates. Hoping nothing breaks.

All that complexity just sits there. Waiting. Decaying. Creating attack surface for problems.

The Real Costs Nobody Calculates

WordPress is free the same way a puppy is free.

The software costs nothing. Everything else costs plenty.

Professional maintenance costs £700–2,800 per year. Premium themes add another £50–90. Essential plugins add up to £350–900 annually.

Then there are the invisible costs. Your time.

You spend 2 hours a month on WordPress maintenance. Your hourly rate is £100. That's £200 in labour costs you're not billing. Suddenly DIY isn't cheaper. You're just not counting your own time.

The Plugin Problem

Here's what the WordPress ecosystem doesn't advertise: 96% of vulnerabilities come from plugins.

Not from WordPress itself. From the stuff you add to make it actually useful.

Nearly 8,000 new vulnerabilities hit the WordPress ecosystem last year. 43% of them don't even require authentication. Attackers can potentially compromise your site without logging in.

WordPress faces 90,000 attacks per minute. Most of those attacks target outdated sites.

Know what happens if you don't update? You become a target.

Know what happens if you do update? Sometimes plugins break. Sometimes they conflict. Sometimes the developer stopped maintaining the plugin two years ago and now you're stuck on an outdated PHP version that's a security risk.

That's the maintenance trap. You need plugins to make WordPress functional. Plugins create vulnerabilities. Vulnerabilities require updates. Updates create conflicts. Conflicts require developer time.

The cycle never ends.

The Performance Tax

Static sites (pre-built HTML files with no database) load faster than CMS-driven sites. Always.

That's not an opinion. That's physics.

A CMS has to process every request server-side. Query the database. Assemble the page. Send it to your browser. That processing time is never zero.

The average WordPress site loads in 2.5 seconds on desktop. On mobile? 13.25 seconds.

You're making people wait. For content that changes three times a year.

A static site serves pre-built files. No processing. No database queries. No assembly required. Just files sitting on a server, ready to be delivered.

The speed difference compounds. Faster sites rank better. Convert better. Static sites need fewer server resources — hosting costs less.

You're paying a performance tax for flexibility you're not using.

A €19 Billion Ecosystem Built on a Shaky Foundation

The WordPress ecosystem is projected to reach €19.38 billion by 2028. This isn't a niche market. It's a massive industry.

But here's the problem: WordPress was built as a blogging platform. For people who write daily. For content creators who publish constantly.

Over time it became the all-purpose CMS for everything — e-commerce, membership sites, business websites, portfolios, booking systems.

The foundation hasn't changed. Only the expectations have.

WordPress itself does relatively little out of the box. You need extensions for almost everything. SEO? Extension. Contact forms? Extension. Online shop? Extension. Security? Extension. Backups? Extension.

That's not a flaw. That's the business model.

A vast ecosystem of developers builds extensions. Theme sellers sell designs. Hosting providers optimise for WordPress. Maintenance services offer monthly packages.

Everyone makes money. The system works.

But it only works if you keep adding extensions. Keep buying themes. Keep paying for maintenance.

The problem isn't that WordPress is bad. The problem is that most people use it without careful consideration.

When WordPress Actually Makes Sense

I'm not saying WordPress is always wrong.

Sometimes it's the right tool.

You publish content multiple times a week. You have a team managing different areas. You need membership functionality out of the box. You run an online shop and WooCommerce fits your budget.

Those are legitimate use cases.

The problem is that most businesses don't fit those patterns. They use WordPress because everyone else uses WordPress. Because it's familiar. Because they think they might need to update content frequently at some point.

That point never comes.

I ask clients about their update frequency. Most can't answer. They think they'll be active. They imagine regular updates. They picture themselves logging in every week.

Then reality hits. They're busy running their actual business. The website stays unchanged for months. The CMS gathers dust. The plugins need updates. The security gaps accumulate.

The overhead remains. The usage never materialises.

The Alternative Nobody Considers

Static sites exist.

Hand-coded websites. Bespoke solutions. Managed platforms. Headless CMS when you actually need content management.

These options get dismissed immediately. "But how do I edit it myself?"

Wrong question.

Right question: "Is my time best spent editing my website?"

You run a business. You have projects to find. Clients to serve. Revenue to generate.

Your website is a marketing tool. A carefully crafted business asset. Not a hobby project you tinker with when you're bored.

The businesses that succeed treat their websites strategically. They bring in expertise. They delegate execution. They focus their time on activities that actually generate revenue.

The Question That Changes Everything

Before you default to WordPress, ask yourself one question.

How often will you actually update your content?

Not how often you think you should. Not how often you imagine you might. How often will you actually do it?

If the answer is "a few times a year," you don't need a CMS.

If the answer is "I'm not sure," you don't need a CMS.

If the answer is "well, I want the option," you're paying for flexibility you won't use.

The overhead is real. The maintenance is real. The security risks are real. The performance tax is real.

The usage? That's theoretical.

You're building infrastructure for a publishing frequency that doesn't exist. You're accepting complexity for convenience you won't use. You're choosing familiarity over fit.

The tool doesn't care whether you use it. It just sits there. Demanding updates. Creating vulnerabilities. Slowing your site down. Costing you money.

WordPress isn't evil. It's just misapplied.

Simple doesn't sell. Familiar sells. Control sells. The illusion of empowerment sells.

The actual results? That's your problem.

What This Means for You

You have options.

You can keep using WordPress because everyone else does. Accept the overhead. Pay for the maintenance. Hope nothing breaks.

Or you can question the default.

Look at your actual needs. Your real update frequency. Your genuine technical capacity. Your honest availability of time.

Match the tool to the job. Not the job to the tool everyone else uses.

The businesses that win aren't the ones with the most powerful CMS. They're the ones who allocated their resources strategically. Who focused their time on revenue generation. Who brought in expertise instead of buying tools.

That might mean WordPress. Probably it doesn't.

The question isn't what everyone else uses. The question is what actually serves your business.

Most people never ask that question. They just default to WordPress and live with the consequences.

You can do better.

Before committing to a platform: get your requirements properly assessed. An experienced web designer will prescribe the right tool — like a doctor who listens before writing a prescription.