Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Speed Up WooCommerce

How to Speed Up WooCommerce

Short answer

To speed up WooCommerce, measure first with PageSpeed Insights, then update to PHP 8.3 or newer, cache catalog pages while keeping cart and checkout dynamic, and turn on HPOS. Compress product images, remove heavy plugins, clean the database, and serve static files from a CDN.

Key takeaways

  • WooCommerce recommends WordPress 6.9 or newer, PHP 8.3 or newer, and a WordPress memory limit of 256 MB or more.
  • Cache catalog pages but never cache the cart, checkout, or My Account pages.
  • HPOS is on by default for new stores from WooCommerce 8.2; older stores switch it on by hand.
  • Good Core Web Vitals means LCP of 2.5 seconds or less, INP of 200 ms or less, and CLS of 0.1 or less.
  • Measure the home, product, category, and checkout pages before and after every change.

What makes a WooCommerce store slow?

A WooCommerce store is usually slow because the server builds pages slowly, the pages are too heavy, or pages that could be cached are not cached.

Those three causes come from the WooCommerce performance guide, which lists caching, images, code size, and database care as the main levers. A store mixes public pages with per-visitor data, so the cart, checkout, and account pages can never be served from a plain cache.

Heavy product images, a long plugin list, and an old PHP version add up fast. A theme that loads large scripts on every page slows the shop, the blog, and the checkout at the same time. The fixes in this guide work in order, from the server up to the front end.

How do you measure your store speed first?

Run your home page, a product page, a category page, and your checkout through PageSpeed Insights before you change anything.

PageSpeed Insights gives you lab scores and real-user field data in one place. The WooCommerce performance guide also names GTmetrix and WebPageTest as tools for regular checks, so pick one and use it the same way each time.

Judge the numbers against the Core Web Vitals thresholds. Google's web.dev thresholds article sets “good” at a Largest Contentful Paint of 2,500 ms or less, an Interaction to Next Paint of 200 ms or less, and a Cumulative Layout Shift of 0.1 or less, all measured at the 75th percentile of page views.

Write down the scores for each page type before you start. A home page can look fine while the checkout lags, so test all four page types and keep the numbers for comparison later. If you want the wider WordPress picture first, read how to speed up WordPress.

What server setup does WooCommerce recommend?

Run WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, with HTTPS and a WordPress memory limit of 256 MB or more.

Those figures come from the WooCommerce server recommendations, which cover WooCommerce 10.8 and later and were updated on 25 May 2026. The same page says WooCommerce is tested up to PHP 8.4.

Older versions still run, but they cost you. The same document notes that WooCommerce also works with PHP 7.4 and MySQL 5.6 or newer, yet those versions have reached their official end of life and may expose the store to security risks.

Check your own numbers under WooCommerce > Status in the dashboard. The System Status page lists your PHP version, database version, and memory limit, and flags anything below the mark.

If your host cannot give you PHP 8.3, ask for an upgrade or move the store. No plugin fix makes up for an old PHP version.

How do you set up caching without breaking the cart?

Cache product, category, and home pages, but keep the cart, checkout, and My Account pages dynamic, because they show each shopper's own data.

Caching serves a saved copy of a page instead of building it fresh on every visit. The WooCommerce performance guide says caching plays a key role in speeding up a store, and it names WP Rocket, W3 Total Cache, and WP Super Cache as plugins that can set up page, browser, and object caching.

The same guide warns that your caching setup must let dynamic content such as cart and checkout pages stay uncached. Some plugins, like WP Rocket, include built-in support for WooCommerce caching, so they handle those exclusions for you.

Set it up in this order:

  1. Install a caching plugin that states it supports WooCommerce.
  2. Turn on page caching for public pages.
  3. Confirm the cart, checkout, and My Account pages are excluded from the cache.
  4. Turn on browser caching so returning visitors reuse static files.
  5. Purge the cache after any product, price, or stock change.

Then place a test order. Add a product to the cart, change the quantity, and confirm the totals update.

If the cart shows another shopper's items or an old total, the cache is serving dynamic pages, so check the exclusions before anything else. Our guide to speeding up the WooCommerce checkout covers the checkout side in more detail.

How do you turn on High-Performance Order Storage (HPOS)?

Switch order storage to HPOS under WooCommerce > Settings > Advanced > Features, after you turn on compatibility mode and let the sync finish.

HPOS stores orders in tables built for orders, instead of the general WordPress posts table. The HPOS documentation says HPOS is enabled by default for new installations from WooCommerce 8.2 onward, while older stores must switch by hand.

Follow these steps on an existing store:

  1. Back up the database and files, and check the Features page for any extension warnings.
  2. Go to WooCommerce > Settings > Advanced > Features.
  3. Tick "Enable compatibility mode (synchronizes orders to the posts table)" and save.
  4. Wait for the background sync to copy orders into the new tables.
  5. Select “High-performance order storage (recommended)” as the order data storage option and save again.

If an extension is not HPOS-compatible, WooCommerce disables the switch and shows which extension blocks it. All extensions on WooCommerce.com are HPOS-compatible, as the same document states, so the block usually comes from a plugin bought elsewhere. Read what HPOS is for the background.

Our guide to enabling HPOS in WooCommerce walks through the same switch step by step.

How do you speed up product images?

Compress every product image, serve it in a modern format, and lazy-load images below the fold.

Images are often the largest files on a product page. The WooCommerce performance guide recommends the right format for each image, JPEG for photographs and PNG for graphics with transparency, then compression before upload, lazy loading, and responsive images for different screen sizes.

Use this routine for new uploads:

  1. Resize the photo to the largest size your theme shows, not the size from the camera.
  2. Compress it with a tool such as TinyPNG or ShortPixel, both named in the WooCommerce performance guide.
  3. Upload the compressed file and check the product page still looks sharp.
  4. Confirm lazy loading is on, so images below the fold load only when the visitor scrolls to them.

For images already on the store, run a bulk compression pass with an image plugin, then check the largest product pages again in PageSpeed Insights. Keep the originals somewhere safe before any bulk pass. Our guide to optimizing images for WordPress covers formats and compression in more depth.

How do you cut down heavy plugins and scripts?

Audit every plugin, remove the ones the store does not need, and use Query Monitor to find which plugin adds the most queries and scripts.

The WooCommerce performance guide recommends Query Monitor and WP Hive for measuring plugin impact, and removing or replacing plugins that hurt speed. Query Monitor groups database queries by the plugin, theme, or function behind them, as its WordPress.org plugin page explains.

Work through the audit like this:

  1. List every active plugin and note what each one does for the store.
  2. Deactivate any plugin the store no longer uses, then delete it.
  3. Load a product page with Query Monitor open and check “Queries by Component” and the Scripts and Styles panels.
  4. Replace a heavy plugin with a lighter one when the same job can be done with less code.
  5. Check the theme too, and prefer a light theme built for WooCommerce over a heavy multi-purpose theme.

Minify the code that stays. The same WooCommerce performance guide lists minifying HTML, CSS, and JavaScript as its third step, and names Autoptimize, WP Rocket, and W3 Total Cache as plugins that do it. Minifying strips spaces and comments from files, which shrinks them without changing how they work.

How do you clean the WooCommerce database?

Delete spam comments, old post revisions, and expired transients, then optimize the database tables.

Orders, products, and sessions add rows every day, and old data piles up. The WooCommerce performance guide recommends a database plugin such as WP-Optimize, WP-Sweep, or Advanced Database Cleaner to clear the clutter and optimize the tables.

Run the clean-up in this order:

  1. Back up the database first, because a clean-up deletes rows you cannot get back.
  2. Delete spam comments and trashed posts.
  3. Delete old post revisions and expired transients.
  4. Optimize the database tables from the same plugin.
  5. Repeat the clean-up once a month, or set the plugin to do it on a schedule.

Do not delete order data or customer records to save space. Those rows are the store's history, and WooCommerce needs them for reports, refunds, and tax records. If the database is very large, check for a plugin that logs too much, such as an activity log with no limit, and cap what it keeps.

How do you use a CDN for a store?

Serve images, CSS, and JavaScript from a CDN so visitors download static files from a server near them.

A content delivery network copies your static files to servers around the world. The WooCommerce performance guide names Cloudflare, Fastly, and Amazon CloudFront as providers, and says a CDN helps by serving static assets from a network of servers spread across the globe.

Set it up in three steps:

  1. Pick a CDN provider that fits your budget and your store size.
  2. Follow the provider's instructions to point your static files at the CDN.
  3. Purge the CDN cache after theme or plugin updates, so visitors do not get old files.

A CDN does not cache the cart or checkout. Those pages still come from your server, which is why the server and PHP version matter as much as the CDN. Read how to set up a CDN for WordPress for the WordPress side of the setup.

How do you check the fixes worked?

Re-run the same four pages through PageSpeed Insights and compare the new scores with the numbers you wrote down at the start.

Check more than the home page score. Open a product page, a category page, and the checkout, and confirm each one improved. Then place a full test order with a real product, a coupon, and a shipping choice, to prove the store still works after the changes.

Watch the store for a week after a big change. Check the WooCommerce > Status > Logs page for new errors, and check the scheduled actions queue under WooCommerce > Status > Scheduled Actions for jobs that failed or stalled. A fix that breaks the checkout costs more than the speed it gains.

Page to checkWhat to look forTool
Home pageLCP 2.5 seconds or lessPageSpeed Insights
Product pageImages load fast, no layout shiftPageSpeed Insights
Category pageFilters respond in 200 ms or lessPageSpeed Insights
CheckoutTotals update, no script errorsTest order

What mistakes should you avoid?

Do not cache the cart or checkout, do not switch on HPOS without a backup, and do not judge speed by the home page alone.

These mistakes show up again and again:

  • Caching the cart, checkout, or My Account pages, so shoppers see each other's data or stale totals.
  • Turning on HPOS on a live store without checking extension compatibility first, which can block orders.
  • Compressing product images so hard that they look bad, which costs sales even if the page loads faster.
  • Installing three speed plugins at once, which can fight each other and break the layout.
  • Measuring only the home page, while the product and checkout pages stay slow.

Fix one thing at a time and measure after each change. When a change makes no difference, turn it off again. A store with fewer, well-chosen fixes runs faster and breaks less often than a store with every speed setting turned on.

Frequently asked questions

Is it safe to use a caching plugin with WooCommerce?

Yes, as long as the cart, checkout, and My Account pages stay out of the cache. Those pages show each shopper's own data, so a cached copy can show the wrong cart or total. Use a caching plugin with built-in WooCommerce support, and place a test order after setup to confirm the totals update correctly.

What is HPOS and why does it make WooCommerce faster?

HPOS moves orders into database tables built for orders, instead of the general WordPress posts table. It is on by default for new stores from WooCommerce 8.2. Older stores switch under WooCommerce > Settings > Advanced > Features, after turning on compatibility mode and letting the sync finish.

Do I need several speed plugins to make WooCommerce fast?

No. Most stores only need one caching plugin and one image optimization plugin. Running two or three speed plugins at once can cause conflicts, duplicate work, and broken layouts. Pick one plugin per job, turn its features on one at a time, and measure after each change.

How do I check if my server meets WooCommerce speed requirements?

Check the store's PHP version, memory limit, and database version under WooCommerce > Status. WooCommerce recommends WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, HTTPS, and a WordPress memory limit of 256 MB or more for WooCommerce 10.8 and later.

Will a CDN make my WooCommerce store faster?

Yes, if the file is large enough to matter. On a store with many products, a CDN serves images, CSS, and JavaScript from a server near each visitor, which cuts download time. The cart and checkout still come from your own server, so a CDN does not fix a slow server or an old PHP version.

Sources

  1. How to optimize performance for WooCommerce stores WooCommerce Developer Resources
  2. WooCommerce Server Recommendations WooCommerce
  3. High-Performance Order Storage WooCommerce
  4. How the Core Web Vitals metrics thresholds were defined web.dev
  5. Query Monitor WordPress.org

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.