Why I Left WordPress After 15 Years
Photo by Shang Zhou
I have used WordPress since 2009. Fifteen years. Over that time I built dozens of sites for clients and for my own businesses. WooCommerce stores. Membership sites. Landing pages. Blogs. If it existed on the internet between 2009 and 2024, there is a good chance I built it on WordPress.
And I am done with it.
This is not a hate post. WordPress powered my career. But the platform I relied on in 2012 is not the platform I am dealing with in 2026.
The Four Breaking Points
1. Plugin Dependency Hell
Every WordPress site I manage has 15 to 30 plugins. That is the only way to get real functionality:
- SEO plugin
- Speed/cache plugin
- Backup plugin
- Security plugin
- Contact form plugin
- Image optimization plugin
- And another 10-20 on top of those
Each one is a potential security hole. Each one can conflict with every other plugin. Each one has a different developer, different coding standards, different update schedule.
Real examples that cost me hours:
- WooCommerce update broke a payment gateway mid-checkout
- Contact form stopped sending emails because a PHP dependency changed on the server
- Security plugin conflicted with caching plugin, brought the site down on a Saturday night
You are not building a website. You are babysitting a collection of third-party code that was never designed to work together.
2. Theme Bloat
What a typical $59 WordPress theme loads on a simple page:
| What loads | Why it is a problem |
|---|---|
| 47 JavaScript files | Most of them unused on that page |
| CSS for sliders never enabled | Dead weight on every request |
| Font files for 10 weights | You use maybe 2 |
| Full jQuery library | For a hover effect |
| Total: ~2MB before the user sees a word | PageSpeed score: embarrassing |
Clients ask why their site is slow. The answer is always the theme. "Optimizing" with caching plugins is a band-aid on a broken leg. You are fighting the platform.
3. PHP in 2026
Nothing against PHP. It works. A large part of the internet runs on it. But the ecosystem has moved:
| Then | Now |
|---|---|
| PHP + jQuery | React + TypeScript |
| Server-rendered pages | Static generation + edge computing |
| FTP deployments | Docker + CI/CD pipelines |
| WordPress themes | Component-based frontends |
The AI tools I use daily - Claude, Cursor, Antigravity - generate React and Node.js natively. Asking them to generate WordPress PHP feels like asking an architect to use materials from 1995.
4. The Security Surface
WordPress powers 40%+ of the web. That makes it the biggest attack target on the planet.
What I see daily:
- Brute force login attempts every minute
- xmlrpc.php attacks in the logs
- Probes for known plugin vulnerabilities
- Automated scanners testing every common exploit
The security plugins I install to protect my sites are themselves WordPress plugins that could be compromised. It is a cycle that never ends.
On the modern stack: my frontend is static HTML. No database to attack. No admin login to brute force. Attack surface is close to zero.
The CMS Search
When I decided to leave, I needed a headless CMS. Somewhere to manage content that is not WordPress.
| CMS | What Happened |
|---|---|
| Payload CMS (tried first) | Hours of config issues. Build errors. Deployment problems the docs did not cover. After the third attempt I stopped. Wrong tool. |
| Directus (switched to) | Sits on top of your existing database. Clean UI. Powerful API. No plugins, no themes, no magic. Collections and fields map directly to database tables. Worked. |
Directus felt like someone built the CMS that WordPress should have become.
What I Moved To
| Layer | Old Stack | New Stack |
|---|---|---|
| Frontend | WordPress + PHP themes | Next.js + React |
| CMS | WordPress admin | Directus (headless) |
| Database | MySQL (WordPress managed) | PostgreSQL (I own it) |
| Hosting | Managed WordPress ($30-50/mo) | Self-hosted VPS ($8/mo) |
| Deployment | FTP or cPanel | Coolify + Docker |
| WordPress plugins | CyberPanel (Postfix + Dovecot) | |
| Page speed | 3-8 seconds | Under 200 milliseconds |
The results:
- Pages load in under 200ms. No PHP execution. No database queries on page load.
- Complex layouts that took days in WordPress themes take hours in React.
- New sites and databases spin up in minutes.
- Total server cost: $8/month for everything.
The Honest Trade-off
Leaving WordPress means learning things the dashboard hid from you:
- Docker containers and how they network
- Reverse proxy configuration
- Database connection strings (different inside vs outside containers)
- CORS policies
- SSL certificate management
- DNS propagation
WordPress hides all of this. That is why it is popular. But it also means you never learn how your website actually works.
Every problem I solved moving off WordPress is knowledge I keep forever. It does not disappear when a plugin changes pricing or a host shuts down.
WordPress taught me how to build websites. Leaving WordPress taught me how the internet actually works.
Who Should Stay on WordPress
This is not a blanket recommendation to leave. WordPress is still the right choice if:
- You are a small business that needs a basic site
- You do not have a developer or technical partner
- You need to be live in a weekend with minimal budget
- Your site does not need to be fast, just functional
Who Should Consider Leaving
You should look at the modern stack if:
- You are spending more time maintaining than building
- Plugin conflicts cost you hours every month
- Page speed matters to your business
- You want to use AI tools for development
- You want full control over your infrastructure
- You are tired of the security maintenance cycle
The Point
The builder outgrew the tool. I wanted more control. More performance. A workflow that works with AI. A stack that does not fight me every week.
The stack I have now is faster, more secure, cheaper to run, and more enjoyable to build with. If you are spending more time maintaining your WordPress site than building your business, it might be time to look at what is on the other side.
driftingdesk.com