WooCommerce · Guide
How to Speed Up the WooCommerce Checkout
Short answer
To speed up the WooCommerce checkout, first measure it with PageSpeed Insights and your browser's Network tab, then fix the slowest part. Keep cart, checkout, and account pages out of page cache, switch on High-Performance Order Storage, update PHP, and trim heavy plugins and scripts. Test a full purchase after each change to confirm the fix helped.
Key takeaways
- Checkout cannot be page-cached; every request must be built fresh for each shopper.
- Measure checkout with PageSpeed Insights and the browser Network tab before changing anything.
- Good Core Web Vitals are LCP 2.5 seconds or less, INP 200 ms or less, and CLS 0.1 or less.
- HPOS is on by default for new stores since WooCommerce 8.2 and stores orders in dedicated tables.
- WooCommerce recommends PHP 8.3 or newer, and flags a memory limit below 256 MB in Site Health.
Why is the WooCommerce checkout slow?
Checkout is slow because it is the one page that cannot be cached and must be built fresh for each shopper.
Every checkout request runs PHP, loads the session, recalculates products, taxes, shipping, and coupons, and talks to the payment gateway. A cached product page skips most of that work, but checkout cannot skip any of it.
WooCommerce's own speed guidance names the usual causes: hosting, images, caching, extensions, themes, memory, and code delivery. Treat each one as a guess until you measure it, then fix the slowest part first.
A fast home page proves nothing about checkout. Measure the checkout flow on its own, from the cart page through payment to the order confirmation page.
How do you measure checkout speed first?
Measure before you change anything, so you can tell whether a fix helped.
Run your checkout page through PageSpeed Insights and note the Core Web Vitals scores. Google judges each metric at the 75th percentile of real page loads, separately for mobile and desktop. A page passes only when all three are good, as web.dev explains.
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP | When the largest content on screen appears | 2.5 seconds or less | Over 4 seconds |
| INP | How fast the page reacts to taps and clicks | 200 ms or less | Over 500 ms |
| CLS | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
Then open your browser's developer tools on the checkout page. Watch the Network tab while you change the address or shipping method, and look for slow or failed requests, above all XHR requests to the Store API.
Also open WooCommerce > Status and Tools > Site Health > Info > Server. WordPress's Site Health docs explain the screen, which shows your PHP version and memory limit in one place.
Write the numbers down. Time a full purchase from cart to confirmation with a stopwatch, and repeat it after each fix.
How do you fix caching without breaking checkout?
Keep the cart, checkout, and account pages out of page cache, and cache everything else.
WooCommerce's caching guidance is firm on this point: Cart, Checkout, and My Account must stay dynamic, because they show information specific to the current customer and cart. Cache one of those pages and the next visitor can see the previous shopper's cart.
Your cache must also skip requests that carry WooCommerce cookies, such as woocommerce_cart_hash, woocommerce_items_in_cart, and wp_woocommerce_session_. It must also skip the _wc_session_ rows if it offers database caching.
Most caching plugins handle this for you. WP Super Cache excludes those pages by default, and WP Rocket needs the three pages excluded in its settings. If shoppers report seeing someone else's cart or an empty cart after adding a product, the cache is the first place to look.
A CDN still helps checkout, but only for static files such as images, styles, and scripts. It cannot cache the checkout page itself.
For host-level caching, ask your host to confirm the same three pages are excluded. Our guide to LiteSpeed Cache settings for WooCommerce covers one common setup.
Should you switch on High-Performance Order Storage?
Yes, if your store still uses the old WordPress posts storage for orders.
High-Performance Order Storage (HPOS) keeps order data in dedicated tables with dedicated indexes, instead of the shared WordPress posts tables. WooCommerce's HPOS docs say it is enabled by default for new installations from WooCommerce 8.2, released in October 2023.
In WooCommerce's own 2023 testing, the checkout flow ran up to 1.5 times faster after enabling HPOS. That is the vendor's test result on its own setup, not a promise for your store, but the direction is clear.
Check your setting at WooCommerce > Settings > Advanced > Features, under Order data storage. If it already says High-performance order storage, you are done.
If it says WordPress posts storage, back up first, tick Enable compatibility mode, wait for the sync to finish, then switch. Our guide to how to enable HPOS covers each step.
If you want the background first, read what HPOS is before you switch a live store.
How do you cut the work the server does at checkout?
Give checkout a faster server, then remove the work that does not need to happen.
Start with PHP. WooCommerce recommends PHP 8.3 or newer, and notes that each major PHP release has been faster than the last. Check your version under Tools > Site Health > Info > Server, and ask your host to update it if you run an older one.
Next, check memory. WooCommerce lists a PHP memory limit below 256 MB in Site Health as a warning sign. If you see that warning, raise the limit with your host or in your hosting panel.
WooCommerce 11.0, released in August 2026, turned on product object caching by default for new stores.
WooCommerce reports variable products loading roughly 9 to 12 percent faster on product pages, and bundle products processing 6 to 12 percent faster during checkout. Existing stores can opt in from the Features screen, as the WooCommerce 11.0 release notes explain.
Add a persistent object cache such as Redis or Memcached when your host offers it. It keeps repeated database answers in memory, so shipping, tax, and cart lookups stop hitting the database on every request.
Finally, check WooCommerce > Status > Scheduled Actions for a backlog. A stuck queue delays order emails, stock updates, and feed syncs, and it adds load to every checkout. If you need more server power, see what hosting resources WooCommerce needs.
How do you trim scripts and images on the checkout page?
Remove what the shopper never sees, and shrink what is left.
Audit the scripts that load on checkout. Marketing pixels, live chat widgets, and analytics tags often load there by default, and each one adds a request. Defer the ones that can wait, and load chat only after the shopper interacts with it.
Check which plugins add files to checkout. A plugin that loads its scripts on every page costs you time on the page where speed matters most. Ask your developer to dequeue scripts that checkout does not need, or replace the plugin with a lighter one.
Shrink product images and serve them in WebP or AVIF. Images rarely cause a slow checkout on their own, but a heavy product gallery still slows the page that leads into it.
Use the Cart and Checkout blocks if you can. They have been the default for new stores since WooCommerce 8.3, released in November 2023.
The blocks render in stages instead of waiting for every part to finish. WooCommerce documents how to switch back to the classic checkout if a plugin needs it.
How do you check that checkout is faster?
Repeat the same measurement you took at the start, on the same pages, after each change.
- Place a test order in a private browser window, from cart to confirmation.
- Time the full purchase and note any step that stalls.
- Run the checkout page through PageSpeed Insights again and compare the scores.
- Check the Network tab for slow or failed requests that remain.
- Confirm the order, the payment, and the confirmation email all arrive as expected.
Change one thing at a time. When two changes land together, you cannot tell which one helped or which one broke something.
If checkout stops working after a change, see our guide to fixing a WooCommerce checkout that is not working before you undo everything.
What mistakes should you avoid?
Most checkout speed work fails from the wrong fix, not from a lack of effort.
- Caching the checkout page, which hands one shopper another shopper's cart.
- Judging checkout by the home page score, which says nothing about dynamic pages.
- Installing an optimisation plugin at random without measuring first.
- Switching order storage on a live store without a backup or a staging test.
- Chasing a perfect PageSpeed score instead of a purchase that completes without delay.
- Ignoring the payment gateway. A slow gateway callback stalls checkout no matter how fast your server is, so check the gateway status page when delays start suddenly.
WooCommerce's performance team puts the goal in plain terms: make the store fast and correct through browsing, cart changes, checkout, payment callbacks, and order processing. A checkout that is fast and wrong is worse than one that is slow and right.
Frequently asked questions
Can I cache the WooCommerce checkout page?
No. Cart, Checkout, and My Account must never be page-cached, because they show information specific to the current customer and cart. Caching one of them can show one shopper another shopper's cart. Cache your product, category, and home pages instead, and speed up checkout with a faster server, an object cache, and fewer scripts.
Will HPOS make my checkout faster?
It depends on your store. If you still use WordPress posts storage for orders, HPOS is the biggest single database change you can make, and WooCommerce's own testing showed checkout up to 1.5 times faster with it. Check WooCommerce, Settings, Advanced, Features, under Order data storage, and switch after a backup.
How do I find out why my WooCommerce checkout is slow?
Open your browser's developer tools on the checkout page and watch the Network tab while you change the address or shipping method. Slow XHR requests point to the server or a plugin. Check WooCommerce, Status, for warnings, and Tools, Site Health, Info, Server, for your PHP version and memory limit.
Do I have to use the Cart and Checkout blocks?
No. Cart and Checkout blocks are the default for new stores since WooCommerce 8.3, but the classic shortcode checkout still works, and WooCommerce documents how to switch back. Only switch if a plugin you need does not support the blocks, and test a full purchase after you change.
What is a good Core Web Vitals score for checkout?
A good score is LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, measured at the 75th percentile of real page loads. If checkout misses those numbers, fix the slowest metric first, then retest with a real purchase rather than trusting the score alone.
Sources
- High-Performance Order Storage WooCommerce
- Improving WooCommerce Performance at Scale WooCommerce Developer Blog
- What's new in WooCommerce 11.0 WooCommerce
- Web Vitals web.dev
- Site Health: keep your website healthy WordPress.org
- Product Object Caching Enabled by Default for New Stores in WooCommerce 11.0 WooCommerce Developer Blog
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
