For years, WordPress was the default for a lot of websites. It was flexible, affordable, easy to update and gave you control over your own content.

No wonder it powers such a huge chunk of the internet.

But a recent security scare made me question whether it still deserves that default position.

Last week, two critical vulnerabilities were reported in PHP, the programming language that powers WordPress and plenty of other platforms. Several governments and institutions around the globe pulled their websites offline as a precaution. Serious stuff.

It got me thinking about the choices we make. And the assumptions we take for granted.

But it’s not just security. It’s all the other compromises we make when we choose what’s free or familiar.

WordPress has always had a lot going for it. But that flexibility can come with baggage. Plugins to manage, updates to keep on top of, and the occasional headache when things stop playing nicely together.

For a long time, we put up with these quirks because WordPress was cheap, familiar and could do just about anything.

But the landscape has changed.

There are now some excellent alternatives. Tools and platforms built for the modern web make it possible to create fast, polished websites without taking on the baggage of an all-in-one system.

WordPress doesn’t have the same clear advantage it once did.

I’m not saying WordPress is bad. I’ve still got clients using it, and it can be an excellent choice.

I’m saying that it shouldn’t be the automatic choice.

Every website project involves trade-offs. The trick is to understand what the organisation actually needs, weigh up the options, and choose the approach that fits best.

That’s how I’ve been approaching my recent projects, and increasingly, WordPress hasn’t been the answer.

It might be right for your next website. But it’s worth asking the question rather than assuming there’s no other choice.