Hi, {{first_name|friend}}. 👋
Welcome to Issue #202 of Loop WP!
Last week was all about Miles, which I took for a spin whilst in beta. Miles is your AI Design Partner for WordPress. It was my most popular newsletter of the last 10 weeks, so check it out.
This week, I'm revisiting a story I first covered in Issue #196, when Maarten Belmans (Studio Wombat) shared early data on block vs classic checkout adoption across 10,000 WooCommerce stores.
Let’s go! 👇
The World's Biggest Dev Event Hits Silicon Valley
WeAreDevelopers World Congress comes to San José, CA — September 23–25, 2026. 10,000+ developers, 500+ speakers, and the full software development lifecycle under one roof, in the heart of Silicon Valley.
Kelsey Hightower. Thomas Dohmke (fmr. CEO, GitHub). Christine Yen (CEO, Honeycomb). Mathias Biilmann (CEO, Netlify). Olivier Pomel (CEO, Datadog). The people actually building the tools you use every day — all on one stage.
AI, cloud, DevOps, security, architecture, and everything real builders ship with. Workshops, masterclasses, and the official congress party.
Same Checkout Story, Bigger Dataset
In Issue #196, the number that stood out most was how low block adoption looked compared with social media sentiment.
💡 Back then, the big takeaway was simple: despite all the focus on Blocks, most stores were sticking with classic checkout.
Maarten has now published a fully updated report based on 15,000 stores (up from 10,000). While it confirms the original point, it also tells a much bigger story about WooCommerce in 2026:
Block cart usage comes in at 12% overall, rising to 18% when filtered to stores created after Blocks became the default experience in WooCommerce 8.3.
The year-on-year chart shows it's clearly climbing, with 20%+ adoption among stores created in 2025. (But it's still nowhere near a full transition.)
🚨 “Store owners” aren't necessarily “anti-block”. They're pro-stability. When you're running a business, "new" often looks like "risk", and nothing feels riskier than touching a checkout that's already converting.
🤔 One question Maarten raises that I'd also love data on: how many stores switch “back” to classic after trying blocks?
The Bigger Story Isn't Just Shopify
The most interesting part of the updated report might not actually be Blocks.
It's that 32% of the 15,000 sampled stores were unreachable, returning 404s, 5xx errors, or stuck in maintenance mode.
🚨 Some highlights:
Grouping by creation year, 36% of stores active in 2022 are already offline.
Then, of the sites still reachable, 14% had moved away from WooCommerce.
Shopify was the biggest named destination, but only at 4.6% (down 0.4% from the original report).
The rest scattered to unknown platforms, lightweight WordPress alternatives, Wix, and Squarespace.
Just one site moved to SureCart, which surprised Maarten, and honestly surprised me too. I’m also surprised no one moved to FluentCart.
The story here is not simply "everyone is leaving WooCommerce for Shopify." The bigger story is that e-commerce is hard, many stores disappear entirely, and the ones that survive are careful about risk.
💡 That also helps explain why adoption of new WooCommerce experiences can be slow. If a checkout works, most merchants are not in a hurry to rip it out and replace it.
WooCommerce Still Has a Performance Problem
🚨 Whilst it didn’t surprise me, another part of the report that is worth discussing was “site speed” (this is not necessarily all Woo’s fault, and they have been working hard on performance over the last 18 months or so).
Maarten measured homepage Time to Last Byte and found WooCommerce sites averaging 1,782ms, compared with 848ms for non-WooCommerce sites. That's a 110% difference.
💡 The metric needs nuance; it's server response only, no assets downloaded, and the WooCommerce sample is ten times larger. But the direction is hard to ignore.
Many WooCommerce stores are still carrying too much weight: heavy themes, page builders, too many plugins, average hosting, or all of the above. And merchants don't always separate "performance", "complexity", and "maintenance burden" into neat categories.
🤔 A small but telling ~1% of migrating stores moved to NextJS-powered platforms. Maarten noted they "honestly feel snappy." It's a tiny trickle for now, but for the dev-leaning part of this audience, is it a signal worth watching?
The Typical Woo Store Still Looks Very WordPress
The install figures paint a picture of an ecosystem that is flexible, messy, extensible, and often carrying years of accumulated decisions (and I can relate to a lot of this with my clients 🫠):
Elementor (free or paid) is on 48% of WooCommerce sites.
Yoast SEO on 39%, WP Mail SMTP on 28%, Contact Form 7 on 26%.
Most popular themes: Hello Elementor (15%), Astra (9.5%), Divi (5.22%), WoodMart (5.19%).
The average site runs 30 plugins.
Most common PHP version: 8.2 (34%), followed by 8.3 (32%).
Only 53% of sites are on the latest WordPress version.
🚨 Interestingly, a lot of this data is comparable to the Metorik 2026 Insights Report (which covers 65 million WooCommerce orders), but with some differences, the biggest being that the average site runs 58 plugins according to Metorik.
If you're running 30 plugins and a legacy page builder, you don't "test out" a new block checkout. You stay on classic because you're not willing to risk your conversion rate on an experiment.
Also, if you’re running 30 - 58 plugins (yes, I know there’s the quality over quantity argument…and the hosting argument), your WooCommerce site is more likely than not going to be slow!
💡 Low block adoption isn't really about Blocks. It's about the reality of how these stores are actually built and maintained.
Final Thoughts
Issue #196 asked “why” classic checkout was still winning.
💡 This updated report gives a fuller answer: because compatibility matters, performance matters, existing stacks matter, and most merchants care more about reliability than platform philosophy.
Blocks may keep growing, and they will. But for now, the clearer takeaway is that WooCommerce still has work to do if it wants more stores to embrace the block future it's building.
What do you think, {{first_name|friend}}?
Have you moved to the block cart or checkout yet?
Does the 32% site mortality rate surprise you, or is that just the reality of e-commerce?
Are you seeing clients ask about more performant, modern alternatives?
Reply and let me know.
🚨 I will leave you with this quote from the report:
“A more worrying trend is probably that new store owners may be choosing Shopify over WooCommerce from the very start.”
I couldn’t agree more with Maarten, and it’s a question worth asking, especially in light of Shopify’s recent MCP announcements, native B2B features and other platform improvements in the last four months (and that’s not even including their marketing campaigns).
All of my inherited or new e-Commerce clients (except one) over the last two years have been on Shopify.
That’s it for this week. 👋
What 200K+ Engineers Read to Stay Ahead
Your GitHub stars won't save you if you're behind on tech trends.
That's why over 200K engineers read The Code to spot what's coming next.
Get curated tech news, tools, and insights twice a week
Learn about emerging trends you can leverage at work in just 5 mins a day
Become the engineer who always knows what's next
Sponsorship Opportunities
🚨 The Google Doc contains all the details if you’re interested in sponsoring the Loop WP Newsletter.
Classifieds
Managed WordPress Hosting redefined. Dynamic autoscaling with high-frequency CPUs & CDN pre-cache for always-fast performance. Easy migration, any time.
DebugBear offers comprehensive website performance monitoring to help you deliver a great user experience and pass Google’s Core Web Vitals assessment.
Kinsta, a reliable hosting partner for your WordPress sites. Everything you need: edge caching, CDN, WAF, 24/7 support, free migrations and much more.
Weekly WordPress News & Tips
This week's excellent and insightful WordPress News & Tips:
Getting Caught Up - How to prepare your store for AI-driven commerce. (WooCommerce)
WooCommerce 10.7 - What’s coming for developers. (Woo Dev Blog)
Call for Speakers - Share your knowledge and experiences at WordPress Accessibility Day! (WP Accessibility Day)
WordPress Agent Bot - Run your WordPress site from Telegram. (WordPress[do]com)
It’s About Trust - Don’t Let AI Grade Its Own Homework. (Chris Reynolds)
Docu-Guide - Adding an MCP Server to the WordPress Core Development Environment. (Weston Ruter)
Four Patterns, Four Stacks - There are only four sensible ways to build a website. (Jono Alderson)
Bug Blitz - How Woo’s happiness team crushed 150+ backlogged bugs. (Job Thomas & Woo Dev Blog)
Zero Requests - While Yoast SEO and Rank Math claim llms.txt helps AI bots find your content, we checked. (The SEO Framework)
No Spending Limit in Core - WordPress 7.0 Lets Any Plugin Use AI Through Your API Key. (The WordPress Company)
Announcing Acorn AI - Acorn AI lets you define abilities as Laravel-style classes, resolved through Acorn’s service container. (Roots)
EmDash - New Plugin Opportunity or Threat? (WP Product Talk)
Annual Survey Results - State of the WordPress Agency 2026. (The Admin Bar)
Valuable Infrastructure - AI Across The WP Ecosystem. (James LePage)
AI Experiments - What’s new in AI 0.7.0. (WordPress AI Team)
Compliance - You Aren’t Responsible for Your Client’s Privacy Policy. (The WP Minute)
April 2026 - What’s new for developers? (WordPress Dev Blog)
WordCamp Asia 2026 - Celebrating Community. (WordPress)
If you have a question about this email or WordPress, please reply, and I will respond as soon as possible.
👋 Until next time,







