EscapeFromWordPress retweeted
wordpress went from almost 44% of all websites to about 39% since january 2025
w3techs numbers, and the drop got bigger every quarter this year
same data, sites with no cms detected went from under 29% to almost 33% this year
my bet is a lot of that is custom sites built with ai
i was one of them
16 years on wordpress, this year we moved 40 client sites to astro
what changed:
1) hosting
- before hetzner + plesk, about $90 a month
- now cloudflare workers, $0 for hosting
2) my time
- before updates, plugins and fixes
- now my agents do the audits and the content changes
3) edits
- my clients dont edit their site
- they send the change, an agent makes it, i check it first
wordpress is not dying tomorrow but the drop is real and its getting faster
EscapeFromWordPress retweeted
Imagine having the full power of AI at your disposal and you create a new website based on WordPress.
EscapeFromWordPress retweeted
AI+WordPress advocates: "Your clients need to be able to update their websites on their own"
AI+Vanilla: "Claude, make it super easy for the client to update their website" (Done in 15 minutes)
In one case, you're integrating the most targeted attack vector on the internet along with a ton of unnecessary bloat because you don't realize that AI has solved CRUD 3 years ago.
EscapeFromWordPress retweeted
another reason why to leave wordpress
thanks god i dont have any site running on wordpress
my agents have full code access to my astro sites and doing weekky security checks
weekly seo audits
weekly google ads audita
social and gbp manages using mcp in postly
‼️ UPDATE: Attackers have fired more than 240,000 exploit attempts at a WordPress flaw that opens while a site is updating, including the update that fixes it.
During an update, WordPress briefly leaves installer files in a predictable folder anyone can reach. Hit it in that window and an attacker with no password can create an admin account and plant code.
Every version from 4.7 to 7.1.3 is exposed.
The fix is 7.1.4. Wordfence advises blocking web access to the upgrade folder before installing it.
EscapeFromWordPress retweeted
Replying to @joshhumble @mark_jansen
Yeah I get that, but why work with a CMS when you can build something better with Claude/Grok.
I know WP well. I used if for over 15 years.
I'm glad I never have to run another update, check PHP, check my host is compatible, check permissions, check plugins work, check plugin updates, change configuration file for install and so on.
I guess it just depends on how quickly you want to work and how you value you time.
When I started EmDash, my goal was for WordPress sites to be "agent-portable", not compatible. Posts like this shows it works better than I could have imagined.
Pixel-perfect theme conversion, and all custom plugins ported.
OK I did it.
Migrated WordPress to Emdash. goodbye $600 bluehost server I've had for 15 years.
307 posts
6.7gb photos
4 custom content types
5 custom page templates
15 custom fields
1 semi-complicated plugin converted and a handful of simple ones
Emdash skills moved it over, migrated off stylus(!) and it's pixel perfect on the front end.
The page speed score went from 52 to 75.
The Admin is fantastic as well - no problem for a WP user. Nice and fast
EscapeFromWordPress retweeted
A WordPress plugin shop moved 5 of their content sites to EmDash CMS. Their take: content sites are where WordPress costs the most and returns the least. escapefromwp.com/evidence/we…
EscapeFromWordPress retweeted
It's wild the number of people using 800,000 lines of code just to let a client log in and add a blog post
EscapeFromWordPress retweeted
Guys, "static" is a spectrum. Very few websites are really truly 100% static, I get it. We all get it.
WordPress is on one end of the static spectrum (0% static) and the kind of sites I build and many other AI stans build might not be 100% static but they're definitely on the other end of that spectrum.
So you can stop countering our arguments about WordPress vs static with "aKtUaLlY...."
EscapeFromWordPress retweeted
Replying to @photomatt @silverlake_news
But the foundation and dot org are just you in a trench coat, pursuing your own goals. And even if that weren't the case, your own actions in the last few years have objectively, tangibly harmed the ecosystem more than anything they've done. Maybe they're baddies; but so are you.
EscapeFromWordPress retweeted
WordPress knows how to make releasing software for it painful.
First, plugin growth statistics disappeared. Then came the login-blocking allegiance checkbox. Now, a six-hour release delay with no precise publication time.
The six-hour "Protect the Shire" delay is a shortsighted implementation. It adds six hours to a release process that already takes several hours, pushing verification and any necessary fixes outside the working day.
Preparing a release already takes hours: final checks, release notes, documentation, packaging, and submission. Add six hours after that, and we're well past an eight-hour workday before we can verify the actual public rollout.
We then have to find out, outside office hours:
- Did the repository render our readme changes correctly?
- Was the update package generated correctly?
- Can users download and install the release?
- Does anything need immediate attention?
The delay doesn't eliminate that work. It moves it into the evening or even night, when the people responsible for the release are less available and too tired to respond. We either extend the workday to babysit publication or leave the rollout unattended. Neither is a good outcome for users.
The timing is uncertain, too. A six-hour hold doesn't tell us exactly when the release will reach users. We either keep checking indefinitely or risk discovering that it went live while we were unavailable. By the time we spot a packaging or installation problem, users may already be affected. That takes away our ability to monitor publication and respond immediately—the very window when close supervision matters most.
I'm not arguing against security checks. I'm arguing that a release safeguard needs to account for the people who must monitor and fix the release.
To WordPress: If a six-hour hold is necessary, give us the generated package, a rendered readme preview, and validation results during that hold. Let us choose a publication time after it expires, when we're actually available to supervise the rollout.
Making maintainers wait is not the same as making releases safer. The process should help us catch problems before publication, not postpone discovering them until everyone has gone home.
A six-hour wait is guaranteed. A secure release isn't.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
The websites I have to manage still on WordPress are painful to even wait for the bloated dashboard to load. I'll never make another WordPress site again unless I'm getting paid a crazy amount of money.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
WordPress is the cancer of the internet... I can't wait till no one uses it anymore.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
Wordpress is shit but you can't build much with HTML, CSS, and JS only.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
I don't get how wordpress didn't die off like 20 years ago. I dabbled with it about that many years ago and kept reading about all the sites that would get hacked because of new vulns. It's been ignored as a solution since.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
Yup! I manage 37 websites. 5 are static. I only have to worry about updating 32 of them each month :0) – at Dortmund, Nordrhein-Westfalen
EscapeFromWordPress retweeted
Replying to @JamesWelbes
Static, fast, secure, easy to maintain. WordPress is unnecessary for a lot of sites.
EscapeFromWordPress retweeted
Replying to @JamesWelbes
I transferred by whole wordpress site to static for exactly that reason. No more dumb failures of the CAPTCHA causing 5000 new fake newsletter signups overnight 😐
EscapeFromWordPress retweeted
Replying to @JamesWelbes
I figured this out THIS morning.
Looked at my site, blogs gone! Was sure I got hacked. Started getting an ego about it: finally getting big enough to be hacked.
But no, it was just WordPress glitching out. And I'm like, why am I using wordpress..?
I no longer use WordPress.





















