Why We Left WordPress: How Our Elementor Agency Adapted to the AI Era

Over the past year, I've personally struggled with what to do about WordPress. Every new leap in AI made WordPress a little less necessary, and the sales for WordPress just weren't coming in.
According to W3Techs, for the first time in its 23-year history, WordPress is steadily losing market share. Proxy was no exception as we saw some really great clients move on to other, more AI focused platforms. As a WordPress developer, I felt about as useful as a cab driver in a town full of Waymos.
Add this to the fact WordPress and Elementor are not keeping up with the market''s demand for speed and security, and a support ticket that proved it wasn't just unlikely, but impossible.
So we made the call. Proxy is officially moving away from WordPress and Elementor for all new builds. Here's why we left, what we switched to, and why I think a lot of businesses are about to follow.
Elementor helped launch Proxy
Proxy really kicked off back in 2020, when Elementor named us one of their Sites of the Month, a super motivating community showcase they ran until 2022. They were intrigued by the idea of an Elementor-focused agency, which was new in those days. Elementor's former Growth Lead even reached out about a possible content collaboration. We weren't camera ready at that time (still might not be!), so it never panned out, but it was a thrill just to be asked.
If we'd stayed on the Elementor path and built our new website on version 4.0, we just might have gotten their attention (and exposure) again. Yet, even that wasn't enough of a perk to keep us on Elementor.
It's not their fault though. Elementor was built on WordPress, which was originally designed as a simple blogging platform, not the full site building platform it eventually became. It was fun seeing how far we could push its limits, but I think the old girl has had enough. Let's put her out to pasture.
To their credit, Elementor introduced their own AI agent, Angie, which can do some very neat things like customizing your wp-admin dashboard or building mini-quizzes (one example I saw them promoting). However, at this point, I feel it's a bit like rearranging deck chairs on the Titanic. AI features are handy, but they're just a fun distraction that ignores the issues with WordPress and PHP's execution model in general. That's the root of the WordPress attack surface and why a plugin flaw can escalate to full site compromise.
To be fair, even Elementor already built their own life raft. It's called Sticklight, Elementor's own vibe-coding platform that generates production-ready projects that it can deploy as static sites. Available stacks are React, Vite, Vue, SvelteKit, and plain HTML, none of which rely on a coupled database like WordPress does with MySQL.
Abandoning WordPress in favor of static builders makes perfect business sense, but it still feels like the captain left us rearranging those deckchairs while we can all see him slowly paddling away on that life raft.
Developers all over are leaving WordPress
The developer sentiment number is brutal: 74% of devs currently working in WordPress would rather switch, and this is up from an already unhealthy number of 53% in 2022.
Here's the part that's interesting. The share WordPress is losing isn't going to Wix or Webflow or even newer builders like Framer. It's going to the "no detectable CMS" category: static generators and modern stacks. You see it every day on the forums. Developers would rather just pack up and wing it. They can make changes with their LLM setups, but then they're left scrambling when the client inevitably asks, "How can I make changes?". (more on that later)
The speed never came
Over the years, we waited for performance improvements that either never showed up or, when they did, were nothing to write home about. Version 4.0 was no exception. Elementor rolled it out this spring, promising "cleaner output and improved Core Web Vitals," but never published a single benchmark to back that up.
The security never came either
Elementor did a tremendous job eliminating the plug-ins one needs to make a site, but it couldn't eliminate all of them sadly. WordPress's unrestricted third-party plugin ecosystem is a landmine for maintenance and security issues. The WordPress plug-in library is like a sketchy torrent site where any plug-in could potentially act as a backdoor for attackers all on its own. In 2025, researchers found 91% of WordPress vulnerabilities were from plugins.
As developers, we need a crystal ball to tell us whether a plugin's author will keep maintaining their plugins or let each day bring that WordPress site closer to an attack. If a plugin author stops updating for any reason (out of business, just didn't feel like it, etc), that site is now a sitting duck.
And sometimes the hole isn't even in a plugin. Just a week prior to writing this, PHP, the language every WordPress site runs on, shipped emergency fixes for two critical flaws nicknamed "PHP2Shell." They let an attacker take over the server a website lives on, no password needed. Several major global companies, high-profile platforms, and some national governments preemptively took down their websites, restricted operations, or entered extended emergency maintenance mode.
Bottom line, if you're staying on WordPress, maintenance is not optional, it's critical. The only way to truly eliminate the ongoing maintenance war is switching to a static framework like next.js, Astro, or even just plain html.
The support ticket that broke the camel's back
Then came the support ticket that would make the decision to switch final. One of our SaaS clients was getting flagged by SecurityScorecard, one of the rating services big companies use to vet vendors before they sign. Their WordPress site was stuck at a B, which doesn't sound terrible, but that one letter was costing our client real contracts as enterprise clients passed them over due to this score.
We fixed everything that could be fixed, but Elementor requires two exceptions the scanners flag ("unsafe-inline" and "unsafe-eval") just to function. Any attempt to remove them broke the site's layout on the front end and completely froze the Elementor editor for our client. (Elementor's editor builds itself from templates that need "unsafe-eval," and it previews the live page inside the editor, so the live site's security rules apply there too.)
The only way to clear those flags was to rip out Elementor and give up visual editing... so we needed to rebuild their site on something else pronto.
WordPress couldn't get us enterprise-ready
Before a big company signs with a vendor, its procurement team wants to see:
- A SOC 2 Type 2 report from an outside auditor, covering the last 12 months
- A recent penetration test (a report from hackers you hired to break in)
- A long security questionnaire (the industry-standard SIG has 855 questions, and the "Lite" version still has 126)
- A data processing agreement for privacy laws like GDPR
- Proof of cyber insurance
- Business continuity and disaster recovery plans
- Single sign-on, multi-factor authentication, and audit logs
- An accessibility report (a VPAT) showing you meet WCAG standards
And before anyone reads any of that, your website has to pass their automated security scan. That's exactly where WordPress let us down.
On top of that, I was looking down the barrel at a $20,00-$150,000 bill to get Proxy SOC 2 Type 2 verified. Was I really going to bet the equivalent of a small island nation's GDP that we could even get there with WordPress builds? No. No, I was not.
Then I started vibe coding
Ever since I began coding with AI, I just can't force myself to use Elementor anymore, no matter how hard I try. It had its strong suits, but the editor always found a new way to frustrate me.
The last time a client asked for WordPress, I ended up coding the site with AI and then exporting to WordPress as a final launch step. As it turns out, converting an html site to Elementor is much simpler than doing it the other way around! (more on what goes into converting Elementor to Astro later)
See our early tests comparing Astro to Elementor
What we switched to
| Before | Now | |
|---|---|---|
| CMS | Elementor | Proxy CMS, built in-house (or Cloudflare's EmDash, for clients who want a more established name) |
| Codebase | WordPress (PHP) | The Astro framework (lean HTML, CSS, and JavaScript) |
| Hosting | xCloud servers | Cloudflare's global edge network |
| Plugins and extra features | The WordPress plugin library | Cloudflare's own tools, or features we build ourselves |
What it did for our own site
Before we moved our own site, we rebuilt madebyproxy.com in Astro with the same design, the same copy, and the same structure, then measured both versions with Google PageSpeed Insights:
| madebyproxy.com homepage | WordPress + Elementor | Astro |
|---|---|---|
| Performance score, mobile | 65 | 99 |
| Main content on screen (LCP) | 9.9s | 2.1s |
| First content on screen (FCP) | 3.5s | 1.2s |
| Page fully drawn (Speed Index) | 4.7s | 1.2s |
| Time the page froze while loading | 123ms | 0ms |
| Page weight | 5.7 MB | 1.0 MB |
| HTML elements on the page | 684 | 215 |
Page-builder boxes (<div>s) | 382 | 34 |
| Elementor code in the page | 1,199 mentions | None |
Same design, same content. Google PageSpeed Insights, mobile, median of 7 to 9 runs, September 25, 2026.
382 boxes became 34, and nothing left the page. All that nesting was there for Elementor's drag handles, not for your visitors.
Static sites built on Cloudflare's edge network are the winning combo
Astro is the framework we build every site on now. Its defining idea is that it renders your pages to plain HTML at build time, before anyone visits, and ships zero JavaScript by default. Nothing is assembled while your visitor waits. The page is already finished before anyone asks for it, and it's served as a file from Cloudflare's edge rather than built by a server on demand.
When a page genuinely needs interactivity, a gallery or a multi-step form, Astro sends just that one component and leaves the rest of the page as static HTML. That approach is called islands, and it's why an Astro page stays fast even when it's doing something clever.
The practical effects are worth spelling out. There's no database to hack, because the site is compiled ahead of time and has nothing for an attacker to query. There's no plugin bloat, so you're not running thirty third-party add-ons just to make the site work, which closes off the most common route into a site. And because Cloudflare caches the whole site at the edge, close to each visitor, it absorbs a viral traffic spike without breaking a sweat or costing a fortune in hosting.
What Will be Left for Web Designers?
Even a third grader can generate a halfway decent brochure site with AI in 2026. But brochure sites are now the floor. What clients need; client portals, live booking systems, quote calculators, dashboards wired to their real data has all never shipped in a template. That's software, not a website, and that's where design work is going. Today's site needs to be not only a sales engine, but it's taken it's place and the hub for their digital transformation. As one of my teammates put it: "In 2020 clients were seeking out design. Now, they want real numbers."
Plus, we've dived much more into apps. Where websites were in 2020 is where apps are today. Anyone can technically make one, but few have the patience, dedication, and skill. We're still many years away from being able to ask AI to make a fully finished app in just a single session. Most AI developers / vibe coders I know work until 3 or 4am every night. It's becoming a meme.

So we built our own apps: Proxy CMS + the Proxy Portal create a dashboard full of tools our clients use to run their Astro sites on Cloudflare. It was actually client of mine who turned me on to everything you can do with Claude and Cloudflare these days. (Thank you, RJ. You rock, man!)
For example, the new madebyproxy.com might look the same, but it's packed with app-ish features like the complex customer ordering form and a host of automations that eliminate tedious sales and onboarding tasks.
The great migration
I truly think we're at the beginning of a great migration away from WordPress. Businesses are skipping Webflow, Framer, and the other out-of-the-box builders and going straight for a custom code and hosting stack that used to be reserved for enterprise companies. The best part? AI is helping us zoom through the work that used to make those builds START at $50k. Now you can get the same kind of site starting at just $2500.
But what about editing?
For years, we thought slow page speed scores were a necessary trade-off for easy editing. Well, not anymore.
There are all kinds of ways to edit a site now:
- Straight through an AI like Claude
- A standalone CMS like Payload (which we considered) or TinaCMS
- Claude Design, Anthropic's tool for designs and prototypes
- EmDash, Cloudflare's new CMS, which launched on April Fool's Day 2026 (but is a real thing)
- and more, but that's a story for another post!
I tried my hand at all of them, and while each one had its cons, I never once felt myself drifting back toward drag and drop. The page builder's one real advantage was that a non-developer could move a box. Now you can just ask.

Meet Proxy CMS and BERT AI
Introducing Proxy CMS. Recently launched, it's already working great for client changes. Simply click on any image or text to change it, and it goes live in about a minute. That part isn't unusual. This is where it gets interesting. The layout is handled by BERT AI, our own AI design assistant, who's constantly being trained on Proxy's own design playbooks. BERT is already like an experienced member of the team. BERT can now provide the same level of human design assistance we've always offered, but he can do it 24/7.
Simply describe your change in plain Englisht to BERT, and sit back as he edits the real code, builds it, and shows you a preview before anything goes live. Every version is saved, and one click rolls it back.
"What if you guys died tomorrow?"
A client once asked us, "Well, what if you guys died tomorrow?" (We like you too!) A bit grim, but fair question, we actually have a good answer. If you ever want to move off our platform, your site can easily be converted to work with EmDash, Cloudflare's new CMS. It's still new, but Cloudflare plans to keep growing it (it even moved its own blog onto EmDash in August), and it's designed specifically for Astro sites. And because Astro is free and open source, your site is standard code you own, so any developer can pick it up.
Btw, We Build Apps now
WYSIWYG editors made web design accessible to way more people, and AI is doing the same for app development. Before AI, building an app was crazy tedious. One unlucky teammate spent months painstakingly building out every possible state of one app's UI components in Figma. Just after he finished, Figma released Figma Make, which does in moments what he'd just spent months of late nights working on. 🤦♂️
We've hired and worked with some great full stack developers over the years, but it ended up costing a literal fortune. Now we can turn our LLM's loose on the same work and get it back in days, not months. If you've ever had an app idea you wanted to see become a reality, now is the time to make your app a reality.
A final note on AI
A lot of people believe AI is taking away creative opportunities, but I look at it the other way around. I believe AI is still finding it's place in contemporary visual design, and very likely will lead to a new renaissance of creativity uninhibited by drudgery.
Let's put it this way. Historically, only the wealthy and those with funds were immortalized in paintings. This was until the invention of the camera of course. As photography grew in popularity, suddenly even the low income and poor could afford portraits. Self portraits, family portraits, portraits with pets... They could finally afford to create their own visual records.
The funny thing is everyone thought painting would no longer be a profession. Who would pay for a hand painted portrait when you could create one in a fraction of the time with the press of a button? Sound familiar?
Of course, as it panned out, painters still exist today. What happened? They're no longer conscripted by the rich to make only what the rich want. Now artists are sought out for their unique visual styles rather than their ability to operate a paint brush. You designers and developers out there keep this in mind. The tools do not make the artist. The artist uses (and makes) the tools. We can now wear as little or as many hats as we like and fill in the gaps with the technology of the day. We might use photos instead of paintings, but it's the overall composition that matters.
AI doesn't hinder creativity, it breeds it. Why? Because for the first time, anyone that is a decent wordsmith, but terrible at drawing can now create their own visual record. An illustrator can now make their own animated series without hiring a whole overseas animation team, and any designer can now code their visions with the skills of a full stack developer. For all we know, the next Kubrick is making his magnum opus without a multi-million dollar Hollywood budget.
At the very least, AI is a net positive for creativity simply because it's eliminated the creative differences problem; almost as much as this guy.
With AI, we no longer need to play every instrument to write a symphony. Each one of us is now the composer.
Keep the web beautiful.
- Devin


