The hidden cost of WordPress is everything the invoice leaves out: the permanent update duty, a performance ceiling on mobile, and the migration debt that grows until leaving safely costs more than staying. The visible bill covers hosting, plugin licenses, and the occasional developer invoice; those are the cheap part.
On a website webvise took over from a previous provider, the privacy policy named a completely different company as the data controller.
If you run your business on WordPress, the invoices you pay probably look reasonable, and the site works. This article prices the costs that never appear on those invoices. The receipts come from a WordPress replacement webvise shipped for MP Bau, from the audit of that inherited site, and from the go-live runbook webvise follows to leave WordPress without losing rankings.
- The update duty is a security obligation. WordPress runs on PHP and gets scanned by automated attacks around the clock; skipping core, theme, and plugin updates turns a maintenance cost into an incident cost.
- The recurring items renew forever: PHP hosting, plugin licenses, and SEO tooling come back every year, and BFSG accessibility duties add legal exposure for German businesses.
- Migration debt is real and can be counted. One inherited site carried copy-pasted slugs, roughly 30 catalogued typos, and a privacy policy naming the wrong company as data controller.
- Leaving safely is a documented process. A pre-flight day plus a 30 to 45 minute cutover, with a 301 map for every old URL, is how rankings survive the move.
- The upside is measurable. MP Bau's Next.js rebuild took 3 weeks and now scores 95 on Lighthouse, loads in under 1.5 seconds, and ranks #1 for "Generalunternehmer Wildau".
If you are weighing an exit, webvise's WordPress migration service handles the rebuild and the ranking continuity work this article describes.
The Update Duty Never Ends
Every WordPress site carries a permanent obligation: core updates, theme updates, and plugin updates, with no end date. That duty exists because the stack runs on PHP and automated attacks scan WordPress installations around the clock; unpatched plugins are the standard way in. The specific attack patterns are documented in WordPress security risks.
The duty converts into money three ways. Someone patches on a schedule and bills for it, or you patch yourself and pay in hours, or nobody patches and you pay for the incident later. None of those three lines appears on the hosting invoice.
On top of the duty sit the renewals: PHP hosting, plugin licenses, and SEO tooling all recur yearly. For German businesses, BFSG accessibility obligations now add legal exposure on top, and retrofitting accessibility onto an aging theme and plugin stack costs more than building it into a new site.
The Performance Ceiling on Mobile
A theme, a page builder, and a dozen plugins each ship their own CSS and JavaScript, and every visitor's phone downloads all of it. You can tune that stack for weeks and still hit a ceiling, because the weight is structural. Why the ceiling exists, and what caching plugins can and cannot fix, is covered in why WordPress sites are slow on mobile.
The ceiling is easiest to see from the other side. After webvise rebuilt MP Bau's WordPress site in Next.js, the same content loads in under 1.5 seconds and scores 95 on Lighthouse. Those numbers were the day-one baseline of the new stack, with no plugin tuning involved.
Migration Debt: What One Inherited Site Carried
Migration debt is everything on the old site that nobody owns anymore: URLs, half-finished pages, legal texts, third-party embeds. It grows quietly, because no invoice ever prices it.
A concrete example, anonymized: webvise recently took over a page-builder site a previous provider had built. The platform was not WordPress, and the debt category is identical. The audit found slugs copy-pasted between pages, roughly 30 catalogued typos, and that privacy policy naming a completely different company as the data controller.
In Germany the last finding is an Abmahnung risk: a defective privacy policy can draw a paid cease-and-desist letter from a competitor's lawyer. The text had clearly been copied from another project at some point and never adapted. Every year a site runs without an audit, this list gets longer, and the eventual migration inventory grows with it.
What Leaving Safely Takes: The Go-Live Runbook
The single biggest trap when replacing WordPress is losing rankings because old URLs return 404 on the new site. A 301 redirect map covering every old URL is mandatory on every webvise migration; it is the first deliverable, before any design work. The cutover itself is a short, scripted block.
| Step | What happens | Time |
|---|---|---|
| 301 redirect map | Every old URL mapped to its new destination | Before cutover |
| Pre-flight day | DNS TTL lowered, mail DNS records collected, Search Console domain property registered, SSL prepared for apex and www | 1 day |
| Cutover | DNS switches to the new site, the 301 map answers every old URL | 30 to 45 minutes |
The questions that usually come up before a migration are answered in the WordPress to Next.js migration FAQ. If the runbook above looks like more than your current provider has planned, webvise's migration service runs it as a fixed part of every project.
What One Exit Returned: The MP Bau Numbers
MP Bau, a general contractor in Wildau, ran its business on an aging WordPress site. webvise replaced it with a Next.js build in 3 weeks, redirects included, following the runbook above.
| Metric | Result after the rebuild |
|---|---|
| Build time | 3 weeks |
| Lighthouse score | 95 |
| Load time | Under 1.5 seconds |
| "Generalunternehmer Wildau" | #1 on Google |
| Two more local search terms | Google page 1 within a month of go-live |
The ranking rows carry the migration-debt argument. The 301 map moved the old URLs' authority to the new site, and within a month Google listed the rebuilt pages on page 1 for two more local terms. The technical comparison behind the stack decision is in React vs WordPress in 2026.
The visible WordPress bill is the cheap part. The hidden part, update duty, mobile ceiling, and the migration debt already sitting on your domain, can be priced in one audit. webvise runs that audit at the start of every migration; book a call if you want the numbers for your own site.