Imagine ordering a car and being handed a folder with thirty manuals on collection day. The engine is from one maker, the brakes from another, the navigation from a third. Each releases updates at a different time. Skip one and the brakes stop working. Install them all and the radio occasionally dies. And better not touch the dashboard, because nobody knows exactly what each button does.
This is not an exaggeration. It is what a typical company website built on WordPress looks like today. When I ask business owners whether they are happy with it, almost nobody says yes. Usually I hear a resigned „it works, but...“.
What happened over twenty years
WordPress launched in 2003 as a blogging tool. It was a great thing: anyone could finally publish online without a developer. Over time it became a universal platform for everything. Online shops, booking systems, company sites, product catalogues. All in one.
And that is the core of the problem. A tool meant to do everything cannot be good at all of it. When your WordPress site loads, it brings code for hundreds of features you will never use. Your customer's browser has to download, parse and run all of it just to show one contact page.
A theme is a suit tailored for somebody else. You can take it in, but it will never fit
Why it will always be slow
This is not about hosting. A faster server does not fix the problem, it only postpones it. The slowness is built into how WordPress works.
When someone opens your page, the server has to assemble it first. It queries the database, walks through every installed plugin and asks each whether it wants to add something. Only then does it start sending the result. On a custom built site the page is prepared in advance and the server just hands it over, like a waiter carrying a finished dish instead of starting to cook when you sit down.
WordPress: database query, plugin pass, page assembly, only then a response. Typically 400 to 2000 milliseconds before it starts answering.
Custom site: the page is ready in advance and the server just sends it. On this site 60 to 150 milliseconds.
Then there is the sheer weight. An average WordPress company site downloads two to four megabytes across a hundred to two hundred files. Most of them are scripts and styles for features that are not even on that page. On a phone with average signal that means five to ten seconds of waiting.
Read that number again. It is not a few percent. Of three people who meant to contact you, one does. The other two close the tab before your offer has a chance to appear. You will never know about them, because they show up in no report as a loss. They show up as someone who simply left.
Why it will always be exposed
WordPress powers roughly two fifths of all websites. That makes it the most attractive target on the internet. An attacker does not look for your company. They write a program that visits millions of sites and tries one known hole. Your site is not a target because you are interesting. It is a target because it runs the same system as millions of others.
The main weakness is not the core system but the plugins. Each is code written by a stranger. Some was written in someone's free time, some has not been maintained for years, and with some you do not even know who is behind it. Every one of them has full access to your site and your database.
- An average WordPress company site runs fifteen to thirty plugins
- Each is a separate program with its own bugs
- One neglected plugin is enough for an attacker to get in
- Updates occasionally break the layout, so many companies stop updating
That creates a trap. Updating is necessary but risky. Not updating is comfortable but dangerous. Most of the companies I meet sit in the second option without knowing it.
A site that has not been updated for a year is not outdated. It is open
Why it makes you harder to find
Google confirms in its documentation that site speed feeds its ranking systems. Specifically it watches how long it takes for the main content to appear, how quickly the page responds to a tap, and whether content jumps around while loading. It measures real loads by real people, not a lab test.
So a slow site does not only lose customers who leave. It loses those who never arrive, because it ranks below the competition.
And something new has been added. People now ask language models: ChatGPT, Perplexity, the assistant in their phone. Those read structure, not pictures or looks. A site buried under theme bloat reads worse to them than a cleanly written page. Ignore this layer and you lose customers who never even reach Google.
Why nobody dares open the admin
This is what I hear most often and it may be the saddest part. A client wants to change one photo. They open the admin, see two hundred menu items, ten content types and an editor with thirty buttons. They close it and email me asking whether I could do it instead.
They paid for a site they are afraid to touch. That is not their fault. It is the fault of a tool designed to do everything for everyone, and therefore unable to be simple for anyone.
It takes so little. When the admin holds exactly the fields that particular site needs and nothing more, changing a photo takes ten seconds and there is nothing to break. Heading, text, image, done. No training needed.
When WordPress does make sense
I am not against it on principle and I am not writing this to knock it down. There are situations where it is the sensible choice:
- You publish a lot, have several authors and need an editorial workflow
- You need something standard launched in a week on a genuinely small budget
- You have your own person handling updates and backups
- The site is a blog or a personal page where tenths of a second do not matter
But if the site is mainly there to bring enquiries, represent the company and run for years without care, the maths changes. A custom site costs more at the start and less over three years, because it needs no monthly maintenance, does not break after an update, and does not cost you visitors.
What to do if you already have WordPress
Do not panic and do not throw it away today. Do three things in this order:
- 1Measure the site in Google PageSpeed Insights. It takes a minute and gives you numbers you can work with.
- 2Check how many plugins you run and when they were last updated. Anything older than a year is a risk.
- 3Add up what the site costs you per year in maintenance, fixes and your own hours. Only then compare it with the price of a new one.
If it turns out the site serves you well, leave it alone. If it turns out you are paying for something that costs you customers, you know what to do.

