65 Million WooCommerce Orders: What 2025 Data Reveals About Your Store's Performance

Metorik just published the second edition of their annual WooCommerce ecosystem report (source: metorik.com). The concept: analyze real data from over 6,000 stores — 65 million orders and $6.6 billion in revenue across 2025.

These aren’t surveys or estimates. They’re actual transactions, anonymized and aggregated. It’s the most accurate snapshot of the WooCommerce ecosystem available today.

I won’t summarize the full report — you can download it for free on Metorik’s website (source: metorik.com/woocommerce-insights). What interests me here is what these numbers tell us about the technical performance of your store, and what you can actually do about it.

72% of Orders on Mobile, but Desktop Revenue Is 2.3x Higher

This is the most striking number in the report. In 2025, 72% of WooCommerce orders were placed on mobile (up from ~62% in 2023). The trend is clear and irreversible.

But here’s the paradox: the average desktop order value is $167, compared to $71 on mobile. Desktop accounts for only 28% of orders but captures a disproportionate share of revenue. And the gap is widening year over year.

What does this mean in practice? Every millisecond matters on mobile. If your store takes 4 seconds to load a product listing on a smartphone, you’re losing the 72% of visitors who buy at the bottom of the funnel. And these visitors aren’t lost by accident — mobile is structurally more sensitive to performance.

Google has been saying it for years: beyond 3 seconds of load time on mobile, 53% of visitors bounce. When Core Web Vitals are measured in real-world conditions on 4G mobile connections, optimizing for mobile isn’t optional — it’s the baseline.

What you can do: Test your store on a real phone over 4G, not on your Mac over Wi-Fi. Measure LCP (Largest Contentful Paint) on your product and category pages using PageSpeed Insights, “field data” tab. If your mobile scores are poor, a WooCommerce performance audit can pinpoint exactly what’s slowing things down.

58 Plugins on Average — and It Hasn’t Changed

The average number of active plugins on a WooCommerce store is 58. Larger stores (over $1M revenue) run 66. The record in the dataset: 237 active plugins on a single store.

What’s striking is that this number has been stable since 2023. Merchants can’t seem to reduce or significantly grow their stack. Every plugin they remove gets replaced by another one.

58 plugins means 58 functions.php files or equivalent loaded on every request. 58 potential sources of CSS and JavaScript injected into the front-end. 58 database tables added. And 58 updates to track.

The distribution tells the story: 18% of stores run between 41 and 50 plugins, 17% between 51 and 60. But there’s also 7% of stores with over 100 plugins. At that level, the question isn’t “does it slow things down?” — it’s “how does it stay up at all?”.

What you can do: Take inventory. How many active plugins on your store? Above 60, an audit is in order. Above 80, it’s urgent. The first step isn’t removing plugins at random — it’s measuring each one’s impact with Query Monitor. Third-party scripts are often the main culprits behind front-end slowdowns.

Elementor #1, Storefront at 0.8%: Page Builders Have Won

The theme rankings are telling. Elementor leads at 9.3%, followed by Flatsome (7.4%) and Woodmart (4.5%). WooCommerce’s default theme, Storefront, has dropped to 0.8% — last place in the top 10.

This confirms a trend I see every day when auditing stores: page builders have replaced lightweight themes. Merchants want total layout freedom. They get it — at the cost of performance.

A theme like Flatsome or Woodmart loads its own CSS framework, its own animation scripts, its own icon library, its own shortcodes. On top of that, Elementor adds its layer. You easily end up with 2 to 3 MB of CSS and JavaScript just from the theme.

Another data point from the report: 56% of stores don’t use a child theme. They customize the parent theme directly, which means every theme update risks breaking their modifications.

What you can do: Measure your total front-end weight using Chrome DevTools (Network tab, filter CSS + JS). If you’re over 1 MB of scripts on a category page, it’s time to audit what the theme is loading and disable unnecessary assets page by page.

12% Still on PHP 7.4, 5% on WooCommerce < 9.0

The report reveals the state of the tech stack. On the positive side: 71% of stores run the latest WordPress version (6.9) and 42% run the latest WooCommerce (10.5).

On the concerning side: 12% of stores still run PHP 7.4, which has been unsupported since November 2022. PHP 8.2 is the most common at 33%, but PHP 8.3 only accounts for 24%. And 5% of stores are still on WooCommerce versions older than 9.0.

This isn’t just a security issue. It’s a direct performance issue. Upgrading from PHP 7.4 to 8.2 delivers a 15 to 25% performance improvement on WordPress, measured on server response times (TTFB). For a WooCommerce store running hundreds of SQL queries per page, that translates to hundreds of milliseconds saved.

What you can do: Check your PHP version in the WordPress dashboard (Tools > Site Health). If you’re below PHP 8.1, ask your host to upgrade — it’s often a single click in cPanel or your hosting panel.

21% Cart Abandonment — and the Biggest Carts Are the Ones You Lose

The report includes cart abandonment data from Metorik Engage. On average, 21% of carts are abandoned. The clothing sector reaches 34%.

The painful detail: the average abandoned cart is worth $141, compared to $117 for a completed cart. You’re losing the biggest baskets. Recovered carts (via email follow-up) average $174.

The connection to performance is direct. A checkout that takes 4 seconds to load, a payment button that doesn’t respond immediately, a form that stutters on mobile — all of this pushes high-value buyers toward the exit. These customers know what they want and won’t wait.

For the clothing sector, the 34% rate is also driven by heavier pages (high-resolution images, lookbooks, multiple filters) and a more complex purchase journey (size, color, variants). It’s the sector with the most to gain from an optimized checkout.

What you can do: Measure the load time of your /checkout/ page. If it exceeds 2.5 seconds, migrate to WooCommerce’s block checkout — it’s lighter, updates without page reloads, and supports express payments (Apple Pay, Google Pay). I’ve written a step-by-step migration guide to walk you through the process.

Free Shipping: 74% of Orders and 54% Higher AOV

Free shipping has become the standard. 74% of WooCommerce orders include free shipping in 2025, up from 65% in 2023. And these orders have an average value of $123, compared to $80 for orders with paid shipping.

What this means for performance: the free shipping threshold has become a checkout optimization lever in its own right. If your threshold is well-calibrated, customers add products to reach it, increasing the basket without additional acquisition cost.

But for this to work, the “Only $X more for free shipping” message needs to display instantly when the customer modifies their cart. If your mini-cart updates via an admin-ajax.php request that takes 800ms, the effect is diluted — it’s the same mechanism as the cart fragments that hurt performance. The block checkout updates totals client-side in real time.

What you can do: Make sure your free shipping threshold is visible from the mini-cart. If you’re still using the classic checkout, updating the amount requires a full page reload — yet another reason to migrate to blocks.

What Metorik Doesn’t Measure: The Root Causes

The Metorik report gives numbers on the what: how many plugins, how many abandoned carts, what average order value. But it doesn’t measure the technical why behind those numbers.

Why 58 plugins on average and not 30? Because WooCommerce alone doesn’t do much — you need extensions for shipping, PDF invoices, variations, tracking, coupons, emails. The report shows that the top 20 WooCommerce plugins include basic features like Stripe Gateway (40%), PDF Invoices (28%), and Shipment Tracking (18%).

Why does mobile generate 72% of orders but 2.3x lower AOV? Partly because stores aren’t yet optimized for mobile. A slow mobile experience discourages complex, high-value purchases. Desktop remains the haven for buyers who want to compare, configure, and complete a large cart without friction.

And why do 12% of stores stay on PHP 7.4? Because upgrading is scary. A poorly coded plugin that breaks on PHP 8.x, an untested theme, a host that doesn’t offer staging. Technical debt is comfortable until the day it becomes costly — in performance, security, and conversions. In fact, even cache plugins aren’t enough to compensate for an outdated tech stack.

The Takeaway

Metorik’s data confirms what I see every week when auditing stores:

Mobile dominates but isn’t treated as a priority. 72% of orders, but how many merchants test their store on a real smartphone?
The tech stack is frozen. 58 plugins, stable for 3 years. Merchants don’t know what to remove without breaking something.
Page builders have won — at the expense of performance. Elementor + a heavy theme + 58 plugins = a 3 MB front-end.
Checkout is the critical path. Abandoned carts worth $141 on average, 34% abandonment in fashion. This is where every millisecond directly impacts revenue.
Technical debt is real. 12% on PHP 7.4, 5% on Woo < 9.0. These are stores leaving performance (and money) on the table.

The full Metorik report contains much more data (delivery distances, payment methods, subscriptions, discounting by industry). I recommend reading it — it’s the most comprehensive document on the real state of WooCommerce in 2025.

Does your store look like these averages? Request a free audit — I’ll measure what’s slowing your WooCommerce down and what it’s costing you in conversions.