WordPress Is So Cooked

How the number one web development platform turned into a burnt weeny sandwich

You’ve seen the thumbnails. Shocked face, red arrow, giant letters: “WordPress is DEAD.” “RIP WordPress.” I’ve used that last one myself.

So let me add one more to the pile. WordPress is so cooked.

Not dead. Cooked. There’s a difference. Dead means nobody’s eating it. Cooked means it’s still on the plate, charred around the edges, and people keep eating it because that’s what was served. Frank Zappa put out an album in 1970 called Burnt Weeny Sandwich. That’s where WordPress is right now: still a sandwich, still technically food, but nobody’s ordering it fresh.

Not dead, just overdone

Let’s be fair about this. Saying nobody uses WordPress would be dumb. W3Techs still has it on about 38.5% of all websites as of November 17, 2026. That’s about seven times Shopify.

But it peaked at 43.6% in January 2025 and has slid since. And here’s the part I find more interesting than the slide itself: the share didn’t go to Wix or Squarespace. It went to “no detectable CMS,” which is now about 33% of the web. Since January, WordPress lost roughly 4.5 points and the no-CMS group gained roughly 4.4.

Those are sites built without a content management system at all. People aren’t trading one website builder for another. They’re skipping the builder.

WordPress was the right answer to an old question

WordPress got popular because it solved a real problem. Before it, you either wrote code or bought desktop software to build a site. WordPress let you log in from any browser and edit your website like a word processor. Plugins arrived in 2004 and you could bolt on almost anything.

And modern WordPress is genuinely easier than it’s ever been. The block editor landed in 2018. Full site editing followed in 2021 and 2022, so you can drag and drop headers, footers and layouts. WordPress 7.0 shipped in May 2026 with a built-in place to connect AI services. This is not a project that’s sitting still.

But all of that is a better answer to the same old question: how does a non-coder edit a website without touching code?

The new answer is: you tell it what you want. Once you can do that, the elaborate interface stops being the help and starts being the thing in the way. It’s one more layer between “here’s my idea” and “here’s the finished page.”

The update treadmill

If you’ve owned a WordPress site, you know the drill. It’s Windows updates for your website.

WordPress core needs updating. The theme needs updating. Every plugin needs updating. And they’re all tied together. Each plugin declares the oldest WordPress version it supports, the newest one its developer has tested, and the minimum PHP version it needs. So a core update or a PHP upgrade from your host can ripple through everything. Update one thing, and three other things want updating, or break.

Most WordPress sites I’ve seen run somewhere between 20 and 30 plugins. That’s 20 to 30 separate pieces of software from 20 to 30 separate developers, all expected to play nicely.

How much time does this take? Maintenance providers I looked at put routine upkeep at about one to four hours a month for someone who knows what they’re doing, in a calm month. Another estimates business owners doing it themselves spend three to five. One bad update can blow that up.

Here’s the kicker: most owners can’t tell whether any of it is being done properly. Maintenance is invisible right up until it isn’t.

Now compare that with a similar brochure site built entirely with AI on a framework like Astro, which by default turns your site into plain, pre-built HTML files.

Typical WordPress site AI-built Astro site
Running on the server PHP, a database, theme, plugins Pre-built HTML files
Monthly updates Core, theme, each plugin, PHP None for the live site
Routine upkeep About 1 to 4 hrs/month Close to zero (my experience)
Paid licences Premium plugins, often $50 to $1,000+/yr Usually none
Login page for bots Yes No
How you change it Log in, find the page, edit blocks Describe the change in plain words

That last row matters most to me. With an AI-built site, I look at the running page and say what I want: move the testimonials up, fix the link in the footer, add a page for the new service. I don’t have to remember how the site was built, which plugin controls what, or where the setting lives.

In a way, AI is hand-coding the website. It’s what we all did in the nineties, except the hands aren’t mine anymore. I’m the director. The machine does the typing.

Security: popularity is a target

To be fair again, WordPress core is in good shape. Patchstack’s State of WordPress Security in 2026 report counted only six vulnerabilities in core in 2025, all low risk.

The problem is everything you bolt onto it. The same report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, up 42% from the year before. 91% were in plugins and 9% in themes.

Worse, 46% of those vulnerabilities had no patch available when they were made public, so “just keep your plugins updated” fails almost half the time. For the most heavily targeted flaws, the median time from public disclosure to mass exploitation was five hours. Five hours. And in Patchstack’s testing, typical hosting defenses blocked only 12% of WordPress-specific attacks.

Who’s doing the attacking? Mostly not people. Imperva’s 2025 Bad Bot Report found that in 2024, automated traffic passed human traffic: 51% of all web traffic, with malicious bots making up 37% on their own.

Bots don’t care who you are or how small your business is. They scan the web looking for the WordPress login page, the XML-RPC file and plugins with known holes, because one working exploit pays off across millions of sites. WordPress’s own handbook says brute force attacks aren’t unique to WordPress, but its popularity makes it a common focus.

That’s what being number one gets you: you’re the biggest target on the range.

A static AI-built site has no database to inject, no PHP running on every visit, no login page for bots to hammer, and no plugins. It’s not magic. Your hosting account, your domain and your contact form still need care. But there’s simply less to break into.

Milking it: the old sedan

So should you tear down your WordPress site tomorrow? Not necessarily. Think about your old car. It’s got 200,000 km on it. It burns a little oil and the air conditioning is moody. But you don’t buy a new car the day the check engine light comes on. You keep it running as long as the repairs cost less than the payments.

Then one day the mechanic says “transmission,” and the math changes.

A WordPress site is the same. If you don’t have the budget for a rebuild, you can milk it for another year or two. And AI makes that a lot easier. I’ve used AI to work on existing WordPress sites: it can read error messages, sort out conflicts, write small fixes and handle content changes. It’s a good mechanic for an old car.

Just know what your transmission moment looks like. A major redesign. A forced PHP upgrade that breaks half your plugins. A hack cleanup. When one of those shows up, stop pouring money into the old sedan.

The verdict

Some sites have good reasons to stay put longer. If your site is tied to a point-of-sale system, a shopping cart, integrated payments, memberships, or a stack of plugins that connect to other software, replacing that is real work. Keep it running, and plan the move carefully.

But an informational brochure site? That’s easy to clone. AI can look at your existing WordPress site, read its menu, and recreate those pages as clean HTML with no WordPress underneath. It’s not hard.

My honest estimate is that in about 80% of cases, there’s no good reason not to switch. Too many benefits, too few reasons to stay.

So here’s where I land:

  • Already on WordPress? Keep it going for a while, and use AI to help maintain it. Milk the old sedan, but watch for the transmission.
  • No website yet? Don’t start on WordPress. There’s no reason to.
  • Old, tired site that needs a makeover? Do the makeover with AI, not WordPress. Switching it over isn’t the hard part anymore.

Zappa built a career on questioning everything and starting from square one. That’s the spirit here. WordPress was the right answer for a long time. The question has changed.

WordPress isn’t dead. It’s just cooked. And nobody says you have to keep eating it.

Book a discovery call