When someone asks what a WordPress site costs, the answer is usually the hosting price - and it is off by a factor of several. Over a three-year horizon, a typical corporate site runs about 2000-7500 € in direct costs plus 36-108 hours of developer time. Most of that total never shows up on a monthly invoice, which is why nobody budgets for it.
In migration projects we see the same picture again and again. A company is convinced the site costs it 20 € a month. When you go through the past year, it adds up to around 2000 € and three weeks of someone’s working time, spread thin across small tasks.
Some of these costs appear not because anyone is doing a bad job, but because the ecosystem has a life of its own. According to the Patchstack State of WordPress Security in 2025 report, 1614 plugins and themes were removed from the official repository during 2024 over unpatched vulnerabilities. For a site owner that is not abstract statistics: if one of the removed plugins was installed on your site, you have to replace it and rebuild the related functionality - for money, and on a deadline you did not choose.
Below is a breakdown of every cost item over three years, an honest comparison with a headless stack, and a separate section on when migration does not pay off.
The problem looks mundane. A founder opens the hosting invoice, sees 20 €, and concludes the site costs almost nothing. The real money sits in four places that never end up in a single document: license renewals on the marketing manager’s personal card, contractor hours buried in a lump-sum invoice for “improvements”, unplanned cleanup after a hack, and the leads you never got on days when the site was down or stopped submitting forms.
Total cost of ownership: everything the site costs over a chosen period, including not just subscriptions but also the team’s working hours, unplanned work, and losses from downtime.
Why Your Hosting Bill Is Not What the Site Costs
The hosting bill pays for disk space and CPU time, but it does not pay for a single one of the reasons the site needs attention in the first place. It is roughly a third of the real cost, and the most predictable third.
WordPress is built so that a site consists of someone else’s code. The core updates itself, and two or three dozen plugins each update on their own schedule, at their own author’s discretion. Any one of those updates can conflict with another, with the theme, or with your own customizations.
That produces the first invisible cost item: someone has to install the updates, check them, and roll them back. On a site with 20 plugins this is not five minutes a quarter. It is recurring work that either eats a marketer’s time or gets billed by a contractor by the hour.
The second invisible item is licenses. Paid plugins and a premium theme renew every year, and without renewal you stop receiving security updates. Formally the site keeps working; in practice it starts accumulating risk.
The third is consequences. A hack, a broken layout after an update, a form that quietly failed to send leads for six months. Episodes like these are never planned into a budget, but they happen with predictable frequency, and each one costs money.
What Makes Up the Cost of Ownership Over Three Years
Here is the breakdown for a typical corporate site: 30-60 pages, 15-25 plugins, a premium theme, content edits a few times a month. The ranges come from our experience with projects of this size; check the specific license prices on the vendors’ own sites.
| Cost item | Over three years | Makes it into the budget |
|---|---|---|
| Hosting with WordPress support | 600-2100 € | yes |
| Paid plugins, licenses and renewals | 900-2700 € | partly |
| Premium theme and license renewal | 150-300 € | rarely |
| Backups, monitoring, protection | 300-900 € | rarely |
| Developer hours for updates and conflicts | 36-108 hours | almost never |
| Incident investigation and recovery | 0-1500 € per case | no |
| Losses from downtime | counted separately | no |
Direct subscriptions add up to roughly 2000-6000 € over three years. This is the part a company can actually see, provided it collects every payment into one spreadsheet.
Developer hours almost never make it into that spreadsheet. One to three hours a month on updates, layout checks, and conflict debugging gives you 36-108 hours over three years. Multiply that by your contractor’s rate: at Exceltic.dev, ongoing site maintenance starts at 50 € per month, and one-off work is billed hourly.
The key point is that updates are not optional. Skipping them does not save money; it moves the expense into the “recovery after a hack” line, where it is higher and arrives without warning.
Hidden Cost Items That Never Make It Into the Budget
Hidden costs differ from visible ones not in size but in the fact that they have no invoice - there is only a consequence that someone has to clean up. There are four main types.
An update that breaks the layout. The page builder plugin ships a major version and some of the blocks on the site fall apart. The fix takes between two and eight hours and gets done urgently, because customers are already seeing the site in that state. Over three years there are two or three such episodes on average.
A plugin that stopped being maintained. The author abandoned the project, or the plugin was pulled from the WordPress directory over an unpatched vulnerability. From there you have two options: keep it and live with the hole, or find a replacement and migrate the data. The second option on a complex plugin means dozens of hours, and sometimes rebuilding a section of the site.
Speed you have to buy separately. Stock WordPress with a couple dozen plugins rarely delivers good Core Web Vitals on its own. In come a caching plugin, an image optimizer, a CDN - and each one is another subscription and another point of conflict. We covered why this is a systemic architecture problem rather than a settings problem in a separate piece on why WordPress slows your site down; what matters here is the other side of it - on WordPress, speed costs money every month.
Security. The public Wordfence Intelligence vulnerability database grows continuously, and the risk rises along with the number of installed extensions. A single incident investigation with database cleanup and restore from backup means 300-1500 € and several days during which the site is either unavailable or flagged as dangerous by browsers.
Downtime: a period when the site is unavailable or has stopped accepting leads, while the traffic you have already paid for goes nowhere.
Comparison With a Headless Stack Over the Same Horizon
A headless stack does not change the total so much as its structure: most of the money goes into the initial build rather than into monthly payments. Here is the comparison over the same three-year horizon.
| Cost item | WordPress | Headless stack |
|---|---|---|
| Initial development | 0 if the site already exists | from 1200 €, the main item |
| Hosting | 600-2100 € | close to zero on static |
| Plugin and theme licenses | 1050-3000 € | 0, or a CMS subscription |
| Updates and conflict debugging | 36-108 hours | a handful of hours |
| Security and recovery | a probabilistic item | no public executable code |
| Structural layout changes | partly done in the admin panel | needs a developer |
| Text and image edits | in the admin panel | in the CMS admin panel, if one was built in |
Where headless is honestly more expensive. First, the start: a migration from WordPress at Exceltic.dev starts at 1200 €, and you pay that sum up front. Second, dependence on a developer: adding a new block type or rebuilding a page template on your own is no longer possible.
Where headless is cheaper. A static site is served from a CDN, and for a marketing site most platforms’ free or very cheap tier is enough. As of Q3 2026, platform limits and prices change often - check them before you run your numbers.
License renewals disappear, the recurring plugin update cycle disappears, and an entire class of incidents disappears with them. On a site with no executable code on the public server, there is nothing to break into through a plugin. We covered the technical side of such a move in our guide to migrating from WordPress to Astro - that one is about SEO and URL structure, this one is about money.
When WordPress Is Cheaper and Migration Does Not Pay Off
WordPress stays cheaper in three scenarios, and in those, migration genuinely makes no sense over a three-year horizon.
- A small site. 5-15 pages, 3-5 plugins, a stock theme with no deep customization. Direct costs rarely exceed 700-1500 € over three years, and in that configuration there is almost nothing to conflict.
- Infrequent edits. Content gets updated once a quarter, the structure does not change for years. Maintenance hours are close to zero - and those hours are exactly where the main savings from migration come from.
- No paid traffic. If no ads point at the site, speed does not convert into money directly. Improving Core Web Vitals will have an SEO effect, but it will not lower your cost per click, because there are no clicks.
The arithmetic is simple. If migration saves you 400 € a year, over three years that is 1200 € - exactly the cost of the migration. There is no return; you are just moving money from one line item to another.
Migration is worth calculating when the savings exceed 700-900 € a year, or when team hours and recurring downtime losses stack on top of the direct costs. On a site with a couple dozen plugins and paid traffic, that threshold is easy to clear; on a five-page brochure site, it is not.
How to Calculate What Your Own WordPress Site Costs
The calculation takes an hour and requires no special tools - a card statement and a calendar are enough. Here is the order of operations.
1. Collect Your Direct Costs for the Past Year
Export 12 months of payments from the card the site is paid with. Look for hosting, the domain, plugin license renewals, the theme, a CDN, a backup service, monitoring. Check employees’ personal cards separately: some of the subscriptions are almost always sitting there.
2. Estimate Your Maintenance Hours for the Year
Count by tasks, not by gut feel. Take a year of correspondence with your contractor or tickets in your tracker and add up everything that touched the site: updates, fixes after updates, conflict debugging, restoring a form. Multiply by your contractor’s hourly rate or by the hourly cost of an employee.
3. Add the Cost of Downtime
You need three numbers: how many leads the site produces per month, what share of them reaches a deal, and the average deal size. For example, 20 leads, a 20% lead-to-deal conversion rate, and a 3000 € average deal give you 12000 € in revenue per month. Divide that by the working hours in a month and you get roughly 75 € per hour of unavailability. Eight hours of downtime twice over three years is 1200 €.
4. Project It Onto Three Years
Multiply the annual totals by three and add the one-off events: one security incident, one replacement of an abandoned plugin, one rebuild after a major update. Compare the resulting figure with the cost of migration plus minimal maintenance for the new stack. The three-year difference is your answer.
Who This Calculation Matters For
The calculation is worth doing for companies of 15 people and up whose site takes part in acquiring customers rather than just existing. These are founders and CMOs who see the contractor invoice and do not understand why a “site on an off-the-shelf CMS” needs regular investment. Companies running paid traffic are especially sensitive to the numbers: for them, cost per click stacks on top of the cost of ownership, and it rises along with load time. If the site brings in no leads and gets no ad spend, you can skip the calculation - the answer is almost certainly “leave it as is”.
Frequently Asked Questions
What does a WordPress site cost for a small company over three years?
For a site with 5-15 pages and 3-5 plugins, direct costs usually fit within 700-1500 € over three years: hosting, the domain, one or two paid licenses. Maintenance hours in that configuration are minimal, because there is almost nothing to conflict. For a corporate site with 30-60 pages and 15-25 plugins the figure is different - 2000-7500 € in direct costs plus 36-108 developer hours. The difference is not the size of the site as such, but the amount of third-party code you have to keep up to date.
Can you lower the cost of ownership without migrating?
Yes, and it is the first thing worth trying. Audit your plugins and remove every one whose function is unused or duplicated: usually a third to a half of them go. Replace bundles of several plugins with a single one, or with a built-in feature of the theme. Drop paid licenses wherever the free version covers the job. This kind of cleanup genuinely reduces both subscriptions and the frequency of update conflicts. It does not remove the maintenance model itself, but it often produces savings that make migration unjustified.
How many hours a month does WordPress maintenance actually take?
In our experience on corporate site projects with 15-25 plugins, it is one to three hours a month in a quiet period. That covers installing core, theme, and plugin updates, checking key pages after an update, and small content edits. The peaks come with major page builder releases and with reacting to vulnerabilities: a month like that can take 8-15 hours. Over three years this adds up to 36-108 hours, assuming no serious incidents.
Which costs more, a hack or downtime?
It depends on how much money the site brings in. An incident investigation with database cleanup and restore from backup means 300-1500 € and usually several days. Downtime is counted differently: take the monthly revenue the site generates and divide it by the working hours in a month. At 12000 € a month, an hour of unavailability costs around 75 €, which means three days of downtime is already comparable to the cost of the investigation. On a site with no leads, the hack costs more; on a site with paid traffic, downtime almost always costs more.
Does migrating to headless pay off within three years?
It does, if the difference in annual costs exceeds 700-900 €, or if noticeable team hours stack on top of the subscriptions. Migration starts at 1200 €, and that sum has to come back as savings on licenses, updates, and incidents. On a corporate site with a couple dozen plugins and paid traffic, the threshold is usually cleared in the second year. On a small brochure site with rare edits it does not pay off even in the fifth - there the honest answer is “do not migrate”.
What to Do Next
- Collect a year of site payments into one spreadsheet, including subscriptions on employees’ personal cards.
- Write out, as a separate line, the hours spent on updates and conflict debugging over the year.
- Calculate the cost of an hour of downtime from your own lead volume and average deal size.
- Compare the three-year total with the cost of migration plus minimal maintenance for the new stack.
If the calculation shows that your site eats more than it brings in, and most of the total goes into updates and licenses, describe your situation to Exceltic.dev. We will review your current stack, calculate the cost of migration on your own numbers, and tell you honestly whether it pays off over three years or not.