Skip to content

How to Speed Up a WooCommerce Website: 10 Easy Steps for Beginners

Flat speedometer browser window icon beside the title How to Speed Up a WooCommerce Website

You can speed up a WooCommerce website in about a weekend, even if you have never touched a line of code. Most guides on this topic explain the theory behind site speed and stop there.

We rechecked every step against the WooCommerce developer docs, the WordPress PHP requirements and Google’s Core Web Vitals guidance in October 2026. Every step shows the exact screen you will land on and the button to click.

First you will check your current speed score. Then come ten steps ordered by impact and four fixes that only apply to WooCommerce stores, such as cart fragments and scheduled actions.

How to Check Your WooCommerce Site’s Current Speed

Lighthouse performance score and metrics in PageSpeed Insights

Before you touch a single setting, find out where you stand today. Open Google PageSpeed Insights and paste in your homepage URL.

Run the same test again on a product page and on your cart page. Product pages and cart pages behave differently from your homepage. A single test never tells the whole story.

To see how other stores score, compare your results with the Core Web Vitals and Lighthouse data in WooCommerce speed statistics.

Pay attention to two numbers on the report. Largest Contentful Paint (LCP) tracks how fast your main content appears on screen. Time to First Byte (TTFB) tracks how fast your server responds before anything even starts loading. Google’s LCP guide on web.dev sets 2.5 seconds or less as a good LCP.

If you want the deeper mechanics behind that second number, DevDiggers has a full breakdown on how to reduce TTFB in WordPress. It walks through server response time in more depth than fits here.

Write your starting scores down somewhere you will remember. You will want to compare them after Step 3, since caching usually produces the biggest jump of the entire process.

What You Need Before You Start

You do not need coding skills for any step in this guide. You do need admin access to your WordPress dashboard and access to your hosting control panel.

Back up your site before you begin. Most hosts include a one-click backup tool, usually labeled Backups or Snapshots in your hosting panel. If yours does not, install a free backup plugin first.

Set aside about two hours for the first pass. Steps 1 through 3 alone will take most of that time, and they will speed up your WooCommerce website more than anything else on this list.

Have your hosting login and your WordPress admin login ready before you start. Switching between the two dashboards is something you will do constantly throughout this guide.

10 Steps to Speed Up a WooCommerce Website

These ten steps are ordered by impact. Start at the top of the list.

If you only have an hour this week, Steps 1 through 3 alone will fix most of what is slowing your store down. The rest of the list is where you go once those three are handled.

1. Pick Hosting Built for WooCommerce

Hostinger web hosting plans page

Your host sets the ceiling on everything else you do here. A cheap shared plan cannot be fixed with plugins alone, no matter how carefully you configure them.

Log into your current hosting panel and check what your plan includes. Look for these three features on the plan comparison page:

  • Server-level caching: Built into the hosting stack itself with no plugin to install separately.
  • PHP 8.3 or newer available: Check under your hosting panel’s PHP settings. The option is usually labeled “PHP Version” or “Select PHP Version.”
  • A staging environment: So you can test changes here without risking your live store in front of paying customers.

If switching hosts feels like too big a step right now, move on to Step 2. You can always come back to this one once the smaller fixes are done.

2. Switch to a Fast WooCommerce Theme

  1. Log into your WordPress dashboard and go to Appearance > Themes.
    Themes link under Appearance in the WordPress dashboard menu
  2. Click Add Theme in the top left corner of the screen.
    Add Theme button at the top of the WordPress Themes screen
  3. Install and activate a lightweight option like Astra or GeneratePress.
    Astra theme shown as the active theme on the WordPress Themes screen

Heavy multi-purpose themes load dozens of scripts and stylesheets your store never uses. Every one of those extra files adds a small delay, and those delays add up fast on a busy shop page.

DevDiggers compares the options in its guide to the fastest WooCommerce themes. Read it before you settle on a final choice.

Test your homepage and a product page again after switching. Compare the LCP with the number you wrote down at the start.

3. Turn On a Caching Plugin

Caching is the single biggest fix most stores can make to speed up a WooCommerce website. It saves a ready-made copy of your page. WordPress does not rebuild it from scratch on every single visit.

  1. Go to Plugins > Add Plugin in your dashboard sidebar.
    Add Plugin link under Plugins in the WordPress dashboard menu
  2. Install and activate a caching plugin like LiteSpeed Cache.
    LiteSpeed Cache plugin card in the WordPress plugin search results
  3. Open the plugin’s settings page from your left sidebar menu. Turn on page caching first. That one setting does most of the work.
    LiteSpeed Cache settings with page caching turned on

Never cache your cart, checkout or account pages. Most caching plugins exclude these automatically for WooCommerce, but check the settings screen yourself to confirm before you move on.

A cached checkout page can show customers the wrong cart total, which is a mistake that costs real sales. It is worth the extra thirty seconds to double-check this one setting.

For a side-by-side comparison of the popular options, see DevDiggers’ roundup of WordPress caching plugins. Run your speed test again once caching is live and compare the new numbers to the ones you saved earlier. A free tool can show whether the page now has caching headers and a faster first byte.

4. Compress and Resize Your Product Images

Product photos are usually the heaviest files on any WooCommerce page. An uncompressed photo straight from a phone camera can run 4-8 MB. That is far bigger than any page needs to display them well.

Before uploading new photos, resize them to the exact dimensions your theme displays them at. A 1200px wide image for a thumbnail that only shows at 300px is wasted bandwidth on every single page load.

  1. Install and activate the Image Optimization plugin from the WordPress Plugin Directory.
    Image Optimizer plugin card in the WordPress plugin search results
  2. Most plugins add a Bulk Optimize button under their own settings page. Click it and let the plugin work through your existing catalog in the background.
    Bulk optimization settings in the Image Optimization plugin

Switch new uploads to WebP format where your theme supports it. DevDiggers covers the full process in its guide on image optimization in WordPress, including which formats work best for product photography.

5. Add a Content Delivery Network

Cloudflare caching screen with the Purge Everything confirmation

A CDN stores copies of your images, scripts and stylesheets on servers spread around the world. Visitors then pull those files from whichever server sits closest to them geographically.

If your caching plugin includes CDN integration, look for a CDN tab in its settings menu. Enter your CDN provider’s details there and save the changes.

Cloudflare’s free tier works well for most small to mid-sized stores. Connecting it takes about ten minutes through your domain’s DNS settings, and most hosts walk you through the exact steps in their own documentation.

This step matters most if you sell to customers outside your hosting server’s country. A store hosted in the United States and selling to shoppers in India will feel a real, noticeable difference here.

6. Keep WordPress, WooCommerce and Plugins Updated

  1. Go to Dashboard > Updates in your WordPress admin panel. Any plugin or theme with an update waiting shows up here with a checkbox next to its name.
    WordPress Updates screen listing a plugin with a new version and an update checkbox
  2. Select all of them and click Update Plugins. Do the same on the Themes tab just above it.
    WordPress Updates screen with the Update Plugins button highlighted

Outdated code is not just a security risk sitting quietly in the background. Every WooCommerce release ships with query improvements and bug fixes that affect real load times, especially around checkout.

High-Performance Order Storage (HPOS) keeps orders in their own database tables. It is on by default for new stores since WooCommerce 8.2. The WooCommerce-specific fixes below show where to check it on an older store.

7. Remove Plugins You Do Not Use

  1. Go to Plugins > Installed Plugins and read through the full list carefully. Every active plugin can add scripts, styles and database queries even when you rarely use it.
    Installed Plugins link under Plugins in the WordPress dashboard menu
  2. Deactivate anything you installed once to test and then forgot about. Click Deactivate and then Delete for anything you are certain your store no longer needs.
    Deactivate link under a plugin name on the WordPress Installed Plugins screen

Fewer, well-built plugins from trusted developers beat a pile of one-off tools installed months ago and never removed. If you are unsure whether your plugin count is a real problem for your store, DevDiggers breaks down how many plugins is too many for a typical shop of your size.

8. Clean Up Your WooCommerce Database

Over time, your database fills up with post revisions, expired transients and leftover data from plugins you removed months back. None of it helps your store run any faster.

  1. Install and activate a database cleanup plugin such as WP-Optimize from the WordPress plugin directory.
    WP-Optimize plugin card in the WordPress plugin search results
  2. Once installed and active, open its dashboard and look for a section labeled Database or Optimization.
    WP-Optimize menu with the Database item highlighted
  3. Click Run Optimization to clean up any bulky parts from the database.
    WP-Optimize Database screen with the Run all selected optimizations button highlighted

Note: Back up your site beforehand, every time, with no exceptions. A database cleanup is safe in almost every case, but skipping the backup step is never worth the risk it carries.

Stores that have run for a few years without ever touching this step tend to see the biggest change here. A bloated database quietly slows down every single page and not only the ones with heavy content.

9. Update Your PHP Version

  1. Go to Tools > Site Health in your WordPress dashboard.
    Site Health link under Tools in the WordPress dashboard menu
  2. Open the Info tab and expand Server to check your current PHP version.
    Site Health Info tab with the PHP version row in the Server section highlighted
  3. If you run anything below PHP 8.3, choose a newer version in your hosting control panel. WordPress recommends PHP 8.3 or greater as of October 2026.

PHP 8 processes WooCommerce’s product and cart logic noticeably faster than PHP 7, based on performance testing from the PHP project itself.

Test your checkout flow right after making this change. An older plugin can occasionally break on a newer PHP version. This is one step worth checking by hand.

10. Turn On Lazy Loading for Images

Lazy loading delays offscreen images until a visitor scrolls down to them. It avoids loading every product photo on a page all at once.

  1. Go to Products > All Products and preview any product.
    All Products link under Products in the WordPress dashboard menu
  2. Open the page source of the page.
    View page source option in the browser menu on a product page
  3. Search loading="lazy" in the page source. A match means the theme has lazy loading on by default.
    Lazy loading attribute found in the product page source

WordPress has included this natively since version 5.5. Most modern themes turn it on by default. Confirm it is active under your theme’s performance settings or your caching plugin’s Media tab if it offers the option there.

This step matters most on category and shop pages. Dozens of product thumbnails would otherwise load at once on those pages, whether a visitor scrolls that far down or not.

WooCommerce-Specific Speed Fixes

A WooCommerce store has slow spots that a plain WordPress site does not. Cart fragment requests, a crowded scheduled actions queue and the old order tables all add server work. The four fixes below target those parts and need no new theme or host.

Stop Cart Fragment Requests on Every Page

Cart fragments refresh the classic mini cart through a wc-ajax=get_refreshed_fragments request. Each request asks your server to rebuild the cart after the page has loaded.

Since WooCommerce 7.8 the script loads only where the classic Cart widget renders, per the WooCommerce developer blog. Some themes such as Storefront hard-code that widget into the header. The Mini-Cart block does not use the cart fragments API. Use it in place of the widget.

Clear the Scheduled Actions Queue

WooCommerce runs background jobs through Action Scheduler and lists them under Tools > Scheduled Actions. The same list sits under WooCommerce > Status > Scheduled Actions. Filter by Past-due and Failed to spot jobs that keep piling up.

WooCommerce Scheduled Actions screen filtered to Past-due with three pending actions

In the Action Scheduler 4.0 code that ships with WooCommerce 11.1, completed actions are deleted after 31 days. Failed ones stay for 93 days. A plugin that floods the queue with failing jobs keeps that table large. Fix or remove that plugin first.

Turn On High-Performance Order Storage

HPOS keeps orders in their own tables and out of the posts table. The HPOS documentation says it is on by default for new stores since WooCommerce 8.2. Older stores can check and switch it at WooCommerce > Settings > Advanced > Features.

Order data storage option set to High-performance order storage in WooCommerce Features settings

Add a Persistent Object Cache

WordPress keeps database query results in memory for one page load only. A persistent object cache such as Redis keeps them between requests. Site Health shows the notice “You should use a persistent object cache” when one is missing.

Site Health recommended improvement asking for a persistent object cache

The WordPress code reference shows that this check depends on how much data your site holds. Ask your host whether it offers Redis. The free Redis Object Cache plugin then connects WordPress to that server.

How Long Does It Take to See Results?

The lab score in PageSpeed Insights changes as soon as you finish Steps 1-3. The field data at the top of the report covers real visits over the past 28 days. That part moves slowly, as the PageSpeed Insights documentation explains.

The remaining steps compound rather than replace each other. A fast host with no caching still feels slow to visitors. A cached site full of 6 MB product photos will not score well either. The cache cannot fix a problem it was never built to solve.

Run your PageSpeed Insights test again after finishing all ten steps. Compare the new numbers against the ones you wrote down back at the start.

If your store still feels slow after all ten steps, the main problem is often something specific to your setup. A poorly coded plugin or a heavy theme customization can hide behind an otherwise solid checklist.

Our guide on why WordPress is so slow covers causes outside WooCommerce. Stores that outgrow one server should read how to scale WooCommerce next.

That is a good point to bring in DevDiggers for a WordPress speed optimization service. A closer look at your Query Monitor report often finds the exact cause.

Conclusion

You do not need a developer to speed up a WooCommerce website. The ten steps above cover hosting, caching and images first. The WooCommerce-specific fixes then handle cart fragments, scheduled actions, order storage and object caching.

Start with Steps 1-3 if you only have an hour to spare this week. They tend to produce the biggest visible jump for the least amount of effort.

Come back to this guide every few months. Plugins update and product catalogs grow. A store that loaded fast at launch can slowly drift back toward slow, often without anyone noticing until a customer complains.

Frequently Asked Questions (FAQs)

Q1. How much does it cost to speed up a WooCommerce website?

Most of the ten steps here use free plugins and settings changes you can make yourself with no outside help. The only likely cost is an upgrade to hosting built for WooCommerce. Check current plan prices with your host before you switch.

Q2. Will speeding up my store increase sales?

Yes, in most cases it will. Faster load times reduce cart abandonment and improve your mobile bounce rate, and both of those feed directly into your overall conversion rate.

Q3. Can I speed up my site without a caching plugin?

Not effectively, no. Caching addresses server load in a way that image compression and plugin cleanup cannot replace on their own. That is why it stays near the top of this list.

Q4. Does WooCommerce slow down WordPress by itself?

Not inherently, no. WooCommerce adds dynamic features like cart and checkout that cannot be cached the same way a normal blog post can. That is why hosting and caching setup matter more here than on a simple WordPress site.

Q5. How often should I redo these speed checks?

Run a PageSpeed Insights test every time you add a new plugin, switch themes, or notice a jump in product count. Quarterly checks work well for most stores even without any specific trigger.

Q6. What is a good WooCommerce page load time to aim for?

Aim for a Largest Contentful Paint of 2.5 seconds or less on mobile and desktop. That is the good threshold on web.dev, measured at the 75th percentile of page loads.

Rishi Yadav
Rishi Yadav

Rishi Yadav is a content writer at DevDiggers who covers WooCommerce store management, WordPress performance and security. He works through each topic in a test environment before writing about it. His guides focus on the steps and settings that matter and skip the ones that sound good on paper.

Leave a Reply

Your email address will not be published. Required fields are marked *