WooCommerce performance
WooCommerce Too Slow? Diagnose Before You Rebuild
WooCommerce is usually slow for a reason you can name and locate: every uncached page is assembled per request by PHP and the database, WooCommerce loads cart-refreshing JavaScript on every page that shows the mini-cart, which many themes put in the header of every page, and cart, checkout and account pages can't be full-page cached because they hold customer state. Extensions, media and hosting then add to whichever of those is already hurting. Find which layer is responsible on your store before buying another plugin or committing to a new architecture.
Reviewed against current Google and WooCommerce documentation on August 2, 2026. The add to cart and checkout sections were rechecked against WooCommerce's docs and source code on October 4, 2026.

Hassan Jamal·Published ·Updated ·17 min read
Hassan is PandaCodeGen's co-founder and lead engineer. He audits WooCommerce stores layer by layer, from field data down to the database, and rebuilds storefronts as custom Next.js when the measurement supports it.
Performance evidence stack
A lab score and field experience answer different questions.
Real-user distribution
Review LCP, INP, and CLS at the 75th percentile by route and device.
Controlled reproduction
Use Lighthouse and a trace to inspect LCP, CLS, and Total Blocking Time.
Constrained layer
Separate origin, network, rendering, media, JavaScript, and third-party work.
Repeat and monitor
Record the environment, repeat the agreed profiles, then watch field data.
INP is a field metric; Lighthouse uses lab diagnostics such as Total Blocking Time.
The short answer
- ✓There's no defensible universal PageSpeed range for WooCommerce stores. Test this store, its pages and its real users.
- ✓Use Chrome UX Report field data for user experience and controlled lab runs for diagnosis. They answer different questions.
- ✓Cache public pages where safe, but keep customer-specific cart, checkout and account data dynamic.
- ✓Repair hosting, queries, extensions, assets and transaction flows before deciding that WooCommerce itself must be replaced.
- ✓Choose headless or a full migration only when the business case and operating model justify the added system boundaries.
Four kinds of evidence, and what each one settles
A WooCommerce speed argument usually stalls because two people are holding different evidence. Field data tells you what real customers experienced and can't tell you why. A lab trace tells you why and can't tell you how common it is. Backend measurement is the only thing that sees server time, and commerce timing is the only thing that sees whether the order got placed. Collect all four before deciding anything. If the evidence does point to a rebuild, ours is a fixed price from $1,500 with no minimum project size, and you own the code at the end.
Field
Real-user Core Web Vitals by page type, device and geography.
Lab
Repeatable traces, requests, JavaScript, images and rendering.
Backend
Server time, PHP workers, queries, cache and external calls.
Commerce
Add to cart, shipping, tax, payment and order creation.
On this page
Does WooCommerce have a typical PageSpeed score?
No reliable platform-wide score applies to every WooCommerce store. Lighthouse is a controlled lab test, and its score changes with the tested URL, device profile, network, CPU, content and run conditions. PageSpeed Insights may also show Chrome UX Report field data collected from real users. Record which dataset you're discussing.
A Lighthouse score of 90 or above is Lighthouse's own good-score band. It isn't a Google ranking threshold. Core Web Vitals are used by Google's ranking systems, but relevance and many other signals count too, and a passing result doesn't guarantee rankings or revenue. For what each metric measures, see Core Web Vitals explained, and for the relationship between the two, how site speed relates to search performance.
Build a useful baseline
Test a real example of each: home, a category, a product, search, the cart, checkout and the account area. Segment field data where enough traffic exists. For lab work, keep the same URL, device profile, network, test region, consent state, account state and data set. Run each case multiple times and keep the median plus the raw results. Note releases, promotions and traffic spikes that could distort comparisons. If you haven't narrowed the problem to a layer yet, our walkthrough for tracing a slow-loading site is the wider starting point.
- ✓Core Web Vitals field status and metric distributions
- ✓Server response time and cache status for public and dynamic requests
- ✓Largest image and font payloads, render-blocking assets and long JavaScript tasks
- ✓Slow database queries, repeated option loads and remote API calls
- ✓PHP worker, CPU, memory, database and object-cache saturation
- ✓Cart, checkout, payment, webhook and order-processing duration
- ✓Errors, timeouts and performance changes by template, device and geography
Eight common causes of a slow WooCommerce store
Slowness on a WooCommerce store almost always traces to one of eight layers: hosting, caching, extensions, the theme or builder, media, the database, third-party scripts, or background operations. Work down the table and gather the evidence in the right-hand column before changing anything, because each layer produces a different symptom and the wrong fix costs you time without moving the number.
| Layer | What to inspect | Evidence before changing it |
|---|---|---|
| Hosting | Workers, CPU, memory, storage, database latency and region | Resource graphs, queueing and server traces |
| Caching | Page, object, browser and CDN cache behavior | Cache headers, hit rates and bypass reasons |
| Extensions | Queries, hooks, assets, scheduled work and remote calls | Profile with controlled enable and disable tests |
| Theme and builder | DOM size, CSS, JavaScript, fonts and template work | Coverage, trace and rendered comparison |
| Media | Dimensions, formats, variants, eager loading and CDN delivery | Request waterfall and visual quality checks |
| Database | Slow queries, indexes, autoloaded data, sessions and table growth | Query logs, explain plans and table inventory |
| Third parties | Analytics, ads, chat, reviews, search and payment scripts | Consent-state waterfall and failure simulation |
| Operations | Cron, imports, feeds, backups, scans and concurrent admin work | Job timing, locks, queues and resource overlap |
Every uncached page is assembled per request. That's the mechanism, not a general complaint about the platform.
How to speed up WooCommerce: a measured fix ladder
Fix a WooCommerce store from the bottom of the stack upward: environment first, then caching, then assets, then the code that runs on each request. The order counts, because a tuning change made on an under-provisioned server or an unsupported PHP version measures nothing. Change one variable at a time and retest the same pages and the same transaction flows after each step.
- ✓Back up the store and reproduce the issue in a production-like test environment.
- ✓Check the environment against WooCommerce's own recommendations first: PHP 8.3 or greater, MySQL 8.0 or greater (or MariaDB 10.6 or greater), and a WordPress memory limit of 256 MB or greater. A store below these is being slowed by its environment before any tuning starts.
- ✓Fix errors, unsupported runtime versions, failed jobs and resource exhaustion.
- ✓Set up caching properly, and make sure the cart, checkout and account pages are never cached.
- ✓Optimize the largest images, fonts, CSS and JavaScript found in the trace.
- ✓Profile expensive queries, hooks, extension code and remote requests.
- ✓Reduce or replace a component only after an isolated test shows its effect.
- ✓Retest the same pages and transaction flows, then monitor real users after release.
A faster home page isn't enough if search, product variations or checkout stop working correctly. Performance work is complete only when functional acceptance still passes. The generic version of this ladder, with the frontend steps expanded, is in our guide to speeding up a website.
Two mechanisms to understand before you buy a plugin
Most WooCommerce speed advice skips the mechanism and jumps to a product recommendation. These two explain much of what a real audit finds, and knowing them changes which fix you reach for.
Cart fragments load wherever the mini-cart renders
WooCommerce used to enqueue the cart-fragments script on every page route. That changed in WooCommerce 7.8, released June 2023: the script now loads only where the Cart Widget is rendered, where a third-party script declares it as a dependency, or where it is explicitly enqueued in code. The catch is how often one of those is true. Storefront and many commercial themes hardcode the mini-cart into the header template, so it renders everywhere and the script comes with it. Where that happens, an AJAX request to refresh cart state fires on your homepage, About page and contact page, and because the response varies per visitor, page caching doesn't remove it. Check your own store instead of assuming either way: load a page that has no cart on it and look for wc-cart-fragments in the network panel. If it's there, WooCommerce publishes a filter to scope it to shop pages, and the mini-cart block avoids the API altogether. The same compounding pattern across the wider plugin set is covered in how plugins accumulate into a page-weight problem.
WooCommerce doesn't modernize your images for you
WooCommerce generates cropped thumbnails, and WordPress core has emittedsrcset and sizes markup since version 4.4, so responsive candidates do exist. What neither does is convert uploads to WebP or AVIF, or enforce an upload size limit. Upload a full-resolution DSLR product photo and the largest candidate mobile browsers can pick is still very close to it. Google reports WebP lossy images as 25 to 34% smaller than comparable JPEG at equivalent SSIM quality index, and without that qualifier the number means little: it's a saving at matched quality, not a free one. AVIF is typically smaller again. On a product page carrying eight unoptimized photos, that difference is the gap between a page that renders quickly on mobile data and one that doesn't.
Why cart, checkout and account need different caching rules
WooCommerce's caching guide says Cart, Checkout and My Account should stay dynamic because they contain customer and session-specific information. That doesn't mean these journeys can't be improved. It means a full-page cache must not serve one customer's state to another. Optimize application work, database access, object caching, APIs and frontend behavior, and keep every result correct.
Why is WooCommerce add to cart slow?
WooCommerce add to cart is slow because the click isn't a local update. It's a server round trip that runs WordPress, resolves the product, checks stock and pricing, writes the cart to the session, and then hands back a fragment for the mini-cart to redraw. In a browser network panel a classic store shows the add as wc-ajax=add_to_cart, and its response already carries the updated mini-cart. A block-based store uses the Store API instead and posts to /wc/store/v1/cart/add-item, which returns the whole cart. Either way it's a full server round trip where the shopper expects an instant update. On a variable product it also has to match the chosen variation. Because the response differs per visitor it can't be served from a page cache, so it lands on PHP every time, competing for the same workers as everything else on the site. Any extension hooked into the add-to-cart action, such as bundles, add-ons, subscriptions or upsell logic, runs inside that same request.
Which request you see depends on where the button is. On shop and category pages, the “Enable AJAX add to cart buttons on archives” setting, on by default, sends the wc-ajax=add_to_cart request above. On a single product page in a classic theme, the default template submits the product form instead, so the shopper waits for the whole product page to be rebuilt on the server. If “Redirect to the cart page after successful addition” is ticked under WooCommerce → Settings → Products, they wait for the cart page as well. Both settings were read from WooCommerce's source code on October 4, 2026.
Work through these in order to find which part of the round trip is responsible:
- ✓Separate click responsiveness from the network request and UI update.
- ✓Inspect variation logic, stock checks, pricing rules, bundles and add-on extensions.
- ✓Trace Store API or AJAX requests, database queries and remote dependencies.
- ✓Check for more than one mini-cart on the page. A theme cart, a slide-out cart plugin and a page-builder cart widget can each refresh fragments on the same click, so the work happens two or three times over.
- ✓Check whether analytics or personalization duplicates work after the action.
- ✓Test guest and signed-in states, simple and variable products, and an empty and populated cart.
Why is WooCommerce checkout slow?
WooCommerce checkout is the slowest page in most stores because it's the one page that can never be full-page cached. WooCommerce's own caching guidance is explicit that Cart, Checkout and My Account must stay dynamic, since they carry customer and session-specific data. So every load runs the full stack: it holds customer state, calculates shipping and tax, and checks stock. Separate the three stages before you optimise, because they cost different things. The initial load builds the form and the totals. Changing an address or a shipping method fires a recalculation over AJAX, and that is where a slow checkout usually reveals itself, since a shopper triggers it several times. Only when they press Place Order does WooCommerce contact the payment provider and write the order. Every extension hooked into any of those adds its work to the same request, and a slow payment or fraud service becomes your slow checkout.
Test each supported country, shipping method, tax path and payment method. Inspect address changes, repeated recalculation, payment-provider latency, fraud services, webhooks and order hooks. Simulate third-party slowness and failure, not only the happy path.
The recalculation request looks different depending on which checkout you run. Since WooCommerce 8.3, released in November 2023, new stores get the block-based Cart and Checkout by default, while stores that updated from an earlier version kept the classic shortcode checkout. On the classic checkout, typing in an address field queues a wc-ajax=update_order_review request one second after the last keystroke, and changing the shipping method sends it straight away. Each one recalculates shipping, then totals, then rebuilds the order summary and payment section on the server. On the block checkout, address changes go to the Store API's cart/update-customer endpoint inside a batch request, a new shipping method sends another Store API request, and both return the whole cart. Changing the payment method doesn't send a request on its own. Sources, read October 4, 2026: the WooCommerce 8.3 release post, the classic checkout script and WooCommerce's Cart and Checkout data flow guide.
Shipping rates are one place a checkout can end up waiting on another company. WooCommerce stores the rates it calculates in the customer's session, keyed to the items and the destination, so it recalculates only when one of those changes. A live-rate extension that asks a carrier for prices makes that call during the recalculation, and the data flow guide lists courier rates and payment APIs among the data that can only come from the server. Check that shipping Debug mode is off on a live store: WooCommerce's own setting text says it bypasses the shipping rate cache, so every recalculation starts from scratch. The caching and the setting are both in WooCommerce's shipping code.
One more thing to rule out before timing anything on a block checkout: a payment gateway that hasn't declared support for it. WooCommerce's Cart and Checkout blocks status page says an incompatible gateway may not appear as a payment option at all, and offers a one-click switch back to the classic checkout.
The WooCommerce Cart and Checkout documentation treats the server as the source of truth for transactional data such as totals, addresses, shipping and coupons. A faster interface still needs authoritative server validation.
How to time a slow add to cart or checkout
Time the request, not the page. Add to cart and checkout feel slow because of one or two server round trips, and a PageSpeed run of the checkout page measures neither of them. Five steps find which request is slow and what it's waiting on.
- Open Chrome DevTools, go to the Network panel and pick the Fetch/XHR filter. Type
wc-ajaxin the filter box on a classic store, orwc/storeon a block checkout. - Click add to cart, change the address and pick a shipping method. For each request, open the Timing tab and read Waiting (TTFB), which Chrome's documentation defines as the time the browser spends waiting for the first byte of the response. That is your server's share. If it's short and the update still feels slow, the delay is in the browser.
- Repeat as a guest and signed in, with a simple and a variable product, with one item and a full cart, and with each shipping and payment method. Take three runs of each and keep the median.
- On a staging copy, install Query Monitor. It lists database queries and outbound HTTP API calls with the time each took, grouped by the plugin responsible, and adds debugging information to the headers of AJAX responses and of REST responses when you're signed in as an administrator. A slow carrier, tax or fraud service shows up there as an HTTP API call.
- Switch off the extensions that hook into cart and checkout one at a time on staging, and retime the same requests after each change.
Why is the WooCommerce backend (wp-admin) slow?
A slow WooCommerce admin is a different problem from a slow storefront, and it usually comes from the database, not the frontend. Two causes account for most of it: options inwp_optionsset to autoload, which are read on every request and accumulate as extensions come and go; and order storage, because before High-Performance Order Storage every order lived in the same table as posts, so the Orders screen slowed down as the store grew. Background work such as scheduled actions, imports and feeds competes for the same resources and makes both worse.
Separate back-office performance from storefront performance. Review order-list queries, analytics, scheduled actions, imports, search, extension dashboards and database size. Record whether High-Performance Order Storage is active, whether compatibility synchronization is running and whether every critical extension declares compatibility. Much of this overlaps with the underlying WordPress install, which our evidence-led method for fixing a slow WordPress site covers layer by layer.
What HPOS can and can't prove
High-Performance Order Storage uses dedicated order tables and indexes. WooCommerce enables it by default for new installations from version 8.2, and on an existing store you turn it on at WooCommerce → Settings → Advanced → Features. Compatibility mode keeps the legacy post tables in sync while you transition, which is the safe way to move but also means you're writing orders twice until you turn it off. It can improve order-data operations, but it isn't a universal storefront cure and no fixed speedup applies to every store. Test on a production-like copy, verify extension compatibility, synchronize and reconcile data, exercise every payment path and keep a rollback plan.
Performance and security maintenance overlap
Unsupported extensions, abandoned code and uncontrolled updates can create both reliability and security risk. Keep an inventory of WordPress, WooCommerce, theme, extensions and custom code. Remove unused components after confirming dependencies, test updates in staging, use least-privilege access, protect backups and monitor logs. A smaller dependency set can reduce work, but no architecture has zero third-party or security risk. We looked at how that exposure is changing in our review of WordPress security risk in 2026.
Measure business effect without invented revenue math
Define the affected journey and compare performance cohorts in your own analytics. Watch product discovery, add-to-cart, checkout start, payment success, errors and support contacts. Control for campaign, price, stock, device, geography and seasonality where possible. Faster pages can improve experience, but a public benchmark doesn't prove the conversion or revenue result for this store.
If the funnel numbers point somewhere other than performance, diagnose that instead of optimising further. Our companion guide to a low WooCommerce conversion rate works through the four stages separately, because a drop between product view and add to cart isn't a speed problem and won't respond to a speed fix.
Repair, headless WooCommerce or replace?
Repair WooCommerce when the measurement points at things you can change and the platform still does what the business needs. Go headless when the back office is working and the storefront is the thing holding you back, accepting that you now run two systems and whatever sits between them. Replace WooCommerce only when the core workflows, the data model or the scale no longer fit, because that's the option that costs a data migration and a retraining exercise on top of the build.
| Option | Potential fit | Main tradeoff to test |
|---|---|---|
| Optimize WooCommerce | Capabilities fit and measured bottlenecks are repairable | Ongoing platform and extension operations |
| Headless WooCommerce | Woo back office stays while a separate storefront solves defined needs | Preview, cache invalidation, search, cart, checkout and two-system ownership |
| Replace WooCommerce | Core workflows, scale, data model or operations no longer fit | Data migration, feature parity, retraining, cutover and support |
Each row has its own write-up: what headless commerce means for the middle option, and WooCommerce compared with a custom build for the third.
Signals that point each way
None of these is a threshold that decides for you, and none of them replaces the measurement work above. They're the patterns we see most often on either side of the decision, offered so you can place your own store before you spend anything. If the signals point toward moving, our WooCommerce migration cost breakdown sets out what drives the scope.
Points toward a rebuild
- Mobile field data sits well below your desktop data and the gap persists across templates.
- A long plugin list where several overlap, and nobody can say what would break if one were removed.
- Mobile is a big part of your sessions, so the weakest experience is also the most common one.
- Your own analytics show the drop-off concentrating on the slowest templates, not spread evenly.
- Repairs have already been attempted and the retest moved little.
Points toward staying and repairing
- A small, young catalog where the operating model is still changing month to month.
- Dependence on WooCommerce-specific extensions with no API equivalent on the target stack.
- No technical support available after launch, in-house or contracted.
- The measured bottleneck is one oversized asset, one slow third party or one hosting tier.
- The team relies on visual theme editing and nobody is prepared to give that up.
When headless is the wrong answer
Headless adds APIs, deployment boundaries, content preview, cache invalidation and distributed debugging. It may be poor value for a simple catalog, a team dependent on visual theme editing, or a store whose measured bottleneck is an unoptimized backend or payment integration that would remain. Don't choose it just to get a Lighthouse screenshot.
Agentic commerce and protocol claims
Commerce APIs and agent-facing protocols are evolving. Treat roadmap announcements, experimental features and third-party connectors as changeable integration inputs. Verify the current WooCommerce documentation, authentication model, permissions, data handling and support status during discovery. Don't migrate because a speculative feature is sold as inevitable.
What to ask a WooCommerce performance provider
Six questions separate an evidence-based engagement from a promise. The first two decide the rest: what baseline evidence gets captured before any change, and which pages, devices, account states and transaction flows count as the test surface. Without those written down, there is nothing to hold the result against afterwards.
- ✓Which field and lab evidence will be captured before changes?
- ✓Which pages, which devices, logged in or out, and which checkout steps will be tested?
- ✓How will server, database, extension and third-party time be separated?
- ✓What has to work, load fast and be accessible before you sign it off?
- ✓Which changes are reversible, and what are the release and rollback triggers?
- ✓Who owns hosting, code, provider accounts, monitoring and post-launch support?
Our answers to those questions are set out on the WooCommerce service page, with the wider storefront work described under ecommerce development and finished examples in our project case studies.
PandaCodeGen terms and performance acceptance
PandaCodeGen's published tiers start at $1,500, $3,500 and $5,000, with custom scope where needed. A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. Package discussions may start with 15 calendar days of launch defect support on Starter and 30 on Growth and Scale; support applies only where the accepted project terms record it. A 90-plus score means the pages named in your quote, tested on phone and desktop, passing three times each. That is a test-bench score. It is not a ranking or conversion guarantee. The tiers and what each one includes are listed on the pricing page.
Frequently asked questions
Why is my WooCommerce store slow?
What PageSpeed score should WooCommerce aim for?
How much does a slow WooCommerce store cost in lost sales?
Can I fix WooCommerce speed without rebuilding?
What is the best alternative to WooCommerce for speed?
How do I speed up WooCommerce?
Why is WooCommerce add to cart slow?
Why is WooCommerce checkout slow?
How do I enable HPOS in WooCommerce?
What server does WooCommerce actually need?
Primary sources
- WooCommerce performance documentation
- WooCommerce caching configuration
- WooCommerce HPOS documentation
- WooCommerce server requirements
- WooCommerce Cart and Checkout data flow
- WooCommerce 8.3.0 release notes (block checkout default)
- WooCommerce Cart and Checkout blocks status
- WooCommerce classic checkout script (source)
- WooCommerce shipping rate caching (source)
- Query Monitor plugin
- Chrome DevTools network reference
Get evidence before choosing the fix
We'll find the slow paths, see where one system hands off to another, and agree what done looks like before we recommend optimization, headless WooCommerce or a full migration.
Related Articles
WooCommerce vs Custom Website in 2026: A Requirements Guide
Compare WooCommerce, headless WooCommerce and custom commerce across capabilities, editing, performance, security, SEO, data, ownership, operating cost and exit.
WooCommerce Migration Cost in 2026: Data, Scope and Tiers
Price a WooCommerce migration from products, customers, orders, payments, subscriptions, extensions, content, SEO, acceptance, cutover and operating responsibility.
WooCommerce Low Conversion Rate: Diagnose It Before You Blame Speed
Speed is the usual suspect because it is the easiest thing to have an opinion about. A diagnostic order that finds the funnel stage which actually changed, including the problems WooCommerce creates that no hosted platform does.