WordPress runs a large part of the internet, and that's no accident: it solved a real problem at a time when publishing content was hard. But a WordPress site is almost always slower than the same site written from scratch, and not because of bad hosting or because someone didn't set up caching.
The slowness is a consequence of how WordPress works. This post explains how it comes about, what it really costs, and when it makes sense to replace it.
How the slowness comes about
The page is assembled on every visit
When someone opens your WordPress site, the server starts PHP, connects to the database, runs a series of queries, assembles the HTML and only then sends it.
A static site does that work once, in advance. The visitor is sent a finished document. It's the difference between cooking to order and taking a ready meal off the shelf: when there are few guests, both are fine.
Caching softens this, but it's a patch over the design, not a solution. And the first visitor after every change still waits.
Plugins add up
The average WordPress site has fifteen to twenty plugins. Each was written by someone else, each adds its own JavaScript and CSS to every page, including the ones where it isn't used.
A forms plugin loads its files on the home page where there's no form. Ten of those and the browser downloads a few hundred kilobytes of code it doesn't need before the first image.
Page builders produce heavy HTML
Elementor, Divi and similar tools give you editing without code, and they pay for it with structure: six nested div elements where one was needed, and the CSS that comes with them.
Themes do more than you need
A bought theme has to satisfy every buyer, so it carries every feature anyone ever asked for. You use maybe a fifth, and the visitor downloads all of it.
Why it matters
For an internal site nobody searches for, it doesn't.
For a site your customers come through, it does, for two reasons:
People leave. On a phone with a weaker connection, the difference between one second and four is the difference between a visitor and an enquiry.
Google measures it. Loading speed is part of how a page is rated, and it's measured on real visitors, not in a lab. Those measures are explained in Core Web Vitals for business owners.
The cost you don't see in the quote
WordPress is cheap to build and more expensive to keep:
- Hosting that can handle it: €5 to €30 a month, because it needs PHP and a database. A static site is free at a small business's traffic.
- Plugin licences: €30 to €100 a year each, and a serious site has several.
- Updates. The core, the theme and every plugin, regularly. A skipped update is a security hole; an update that's done sometimes breaks the layout.
- Fixes after updates. This is the line nobody plans for.
- Security. WordPress is the most common target precisely because it's the most widespread.
Added up, €300 to €600 a year just to keep the site standing, before a single content change.
What a custom build changes
A site written from scratch on a modern stack:
- Sends finished HTML, assembled when it's published, not on every visit.
- Carries only its own code. No plugins you didn't ask for.
- Is served from a network of servers close to the visitor.
- Has no database on the critical path for pages that don't need one.
- Has no weekly updates that can break something.
In practice that means loading in under a second instead of three to five, and a yearly cost of a few tens of euros instead of a few hundred.
When it makes sense to keep WordPress
The honest side:
- You publish a lot of content with several editors. WordPress's editing side is still good.
- Someone already maintains it and does it well.
- The site is secondary and speed doesn't change the business.
- You rely on a plugin that solves something specific, and replacing it would cost more than it's worth.
If that's you, don't touch it. Moving only makes sense when it solves a real problem.
When it's worth replacing
- The site takes longer than three seconds to load on a phone and it can't be fixed.
- Customers find you through search and the competition is faster.
- Maintenance takes more time and money than the site brings back.
- You need something no plugin does properly.
- Something regularly breaks after updates.
What the switch looks like
The same as from any platform, and one step is key:
- A list of every existing address.
- Moving the content: texts and images aren't rewritten.
- Building and checking the new site before switching.
- One-to-one redirects. Every old address to its counterpart, never everything to the home page.
- Switching the domain and shutting down the old site on the same day.
Without the fourth and fifth steps, the site loses the visibility it built up over years.
Frequently asked questions
Can WordPress be made faster?
Partly. Caching, cleaning up plugins, better hosting and image optimisation bring real progress. The limit is that the page is still assembled from a database and still carries the weight of the theme.
How much does a replacement cost?
Like any custom build: €500 to €2,000 for a business site. The breakdown is in what goes into the price of a website.
Will I lose my Google rankings?
Not permanently, with correct redirects. Expect fluctuation over two to eight weeks.
Can I still publish myself?
Yes. The admin panel is planned around how much you actually publish.
How to check your case
Run your site through PageSpeed Insights and look at the mobile score. If it's below 50, there's room to improve, and whether it's worth it depends on how much business comes through the site.
Send me the address and tell me what bothers you.