ecomhint
Start Audit

Free WooCommerce speed test

Find out what slows your WooCommerce store and fix the right things first. Free, with nothing to install.

Free • No signup • Powered by Lighthouse • No WordPress login needed

An example speed test result: lab score, the verdict, and the fix list with Speed Up Your Server first.
Example result with example values.

Why WooCommerce stores get slow

A slow WooCommerce page usually comes down to one of three things, and each one needs a different fix.

  1. Cause 1: The page cache can't serve it

    A page cache sends a ready copy at once, but a cache that is off, or a cookie set for every new visitor, sends the request on to your server.

  2. Cause 2: The server takes long to build the page

    Without a ready copy, your server builds the page with PHP and the database, and nothing reaches the shopper until it starts sending.

  3. Cause 3: The page is heavy or slow to show

    Images bigger than they show, scripts the page doesn't use (like payment scripts on the homepage) and a main image a plugin holds back all keep the shopper waiting.

How a page reaches a shopper

The shopper's phone asks for the page. If a page cache (your host's cache, a CDN or a cache plugin) has a ready copy, it sends it at once. If it can't (cause 1), your server builds the page with PHP and the database (cause 2) and sends it back. Either way, the page then brings its images and scripts (cause 3).

Simplified. A ready copy skips building the page, but the page's images and scripts still have to download. The three causes follow WooCommerce's own speed guide.
How to speed up WooCommerce

How to test your WooCommerce store speed

Three steps take you from your store's address to a ranked list of fixes, with no WordPress login.

  1. Step 1. Run the WooCommerce speed test

    Paste your homepage address. Results take about a minute.

    Fills in the speed test form at the top of the page.

    Each run covers one address.

  2. Step 2. We test the page two ways

    Google's PageSpeed Insights loads your page on mobile and desktop at the same time. Our server loads it up to 3 times to time your server and look for a page cache.

    PageSpeed Insights

    Mobile and desktop

    • LCP
    • INP
    • CLS
    • TTFB

    Our server

    Timing and page cache

    1. Try 1
    2. Try 2
    3. Try 3

    Up to 3 loads from Germany, each one timed and checked for a page cache.

  3. Step 3. Follow the steps for your cache setup

    The steps follow the cache setup the test finds, and use WP Rocket's or LiteSpeed Cache's own settings when it sees them. With no cache plugin and a slow or uncached page, the cache step starts in Site Health.

    Where the steps send you

    • Speed Up Your ServerSite Health
    • Reduce JavaScript & Tracking ScriptsWP Rocket settings
    • Optimize Your ImagesLiteSpeed Cache settings

    Each store gets the steps for its own setup: WP Rocket, LiteSpeed Cache, or Site Health when the test sees no cache plugin and the page is slow or uncached.

Run the free test

What this test checks on a WooCommerce store

Beyond the PageSpeed Insights scores, the test looks for the slowdowns WooCommerce stores run into.

  • Page cache not serving

    We load your page up to 3 times and check each load for a cache hit.

  • Cart session cookie

    We check whether new visitors with an empty cart get a WooCommerce session cookie, which can keep pages out of the cache.

  • Slow cart requests

    From Google's test run, we time your cart and AJAX requests, which usually skip the page cache.

  • Cart fragments

    We look for WooCommerce's cart fragments script, which asks your server for the cart on a shopper's first page view.

  • Payment scripts on the homepage

    When you test your homepage, we look for Stripe, WooPayments or PayPal files and product page scripts that belong elsewhere.

  • Order Attribution scripts

    We check for the small scripts WooCommerce's Order Attribution loads on every page to record where each buyer came from.

  • Oversized grid images

    When Lighthouse flags an oversized product grid image, we check whether the thumbnail file or its sizes attribute is the cause.

  • Main image held back

    We check whether a plugin such as LiteSpeed Cache or Perfmatters lazy-loads your main image, the one Lighthouse times for LCP.

The WooCommerce checks need your page to load WooCommerce's own files.

Which audit do you need?

Start here for a free speed check. Run the full store audit when you want the whole conversion picture.

WooCommerce speed test

Free

PageSpeed Insights scores plus our server and page cache check. No signup.

  • Mobile and desktop scores
  • Lab and real-user (CrUX) data
  • Fixes grouped with time savings
  • Server and page cache check
  • Page cache steps for your plugin or host
  • Homepage, product pages, and your real cart page
  • Your screenshot and a visual example of the fix

You're here.

Run the free speed test

Full WooCommerce store audit

Recommended
$19one time

An AI review running 80+ checks across your homepage, product pages, and cart.

  • SEO & AI, Performance, UX & CRO, Trust & Legal, Tech & Security, Accessibility
  • Homepage, product pages, and your real cart page
  • Your screenshot, a visual example of the fix, and fix steps
  • WooCommerce plugin recommendations
  • Scored and ranked by priority
Run the full audit

Not on WooCommerce? Use the store speed test. On Shopify? Use the Shopify speed test. Checking SEO instead? Run the free WooCommerce SEO audit.

WooCommerce speed, answered plainly

What the test looks at, what it leaves alone, and why a cached store can still be slow.

Still unsure? Ask us anything.

How do I test my WooCommerce store's speed?

Paste your homepage address at the top of this page and press Analyze Speed. PageSpeed Insights tests it on mobile and desktop, which usually takes 30 to 60 seconds. Each run covers one address, so test a product page separately. You can run 5 tests an hour.

How is this different from PageSpeed Insights or GTmetrix?

The scores are PageSpeed Insights scores, run on mobile and desktop. On top of them, our server loads your page up to 3 times to check your server and page cache, the WooCommerce checks run, and the steps use your cache plugin's own settings when the test spots WP Rocket or LiteSpeed Cache. There's no request waterfall and no choice of test location, and our server check always runs from Germany. If you need a waterfall, GTmetrix and Pingdom show one.

Why is my WooCommerce store slow?

WooCommerce's own speed guide names three causes: the cache can't serve it, the server builds the page slowly, or the page is heavy. On top of that, a theme or plugin can add a cart fragments request or start a cart session for every visitor. The test can flag these when it sees them, along with product and payment scripts on your homepage. Our guide to a faster WooCommerce store puts the fixes in order.

I already use WP Rocket or LiteSpeed Cache. Why is my store still slow?

Installed isn't the same as serving, so the test loads your page up to 3 times and checks each load for a cache hit. It can tell when LiteSpeed Cache or WP Rocket never served a load, or when a cookie made the cache skip the page. Even a working cache can't answer cart requests or make a heavy page lighter. When the test sees your cache plugin, its steps use that plugin's own settings and don't ask you to add a second one.

Why can't the cart and checkout be cached?

Those pages are different for every shopper, so page caches skip them and your server builds them on every visit. The test doesn't load your cart or checkout, but it reads the timings of the cart and AJAX requests your tested page sent during Google's test. If one took 600 ms or more, the Speed Up Your Server card can add a step for pages the cache can't serve. It points to PHP 8.3 or newer, an object cache and Query Monitor.

Does the test need my WordPress login or a plugin?

No. Besides PageSpeed Insights, our server usually makes 4 public requests: up to 3 loads of your page and one to WooCommerce's Store API. We never read cookie values, and your page's HTML isn't stored. A password-protected store can't be tested, because PageSpeed Insights can't sign in.

Is this a load test?

No. It loads your page the way one first-time visitor would: PageSpeed Insights runs its test, and our server requests the page up to 3 times, one after another. It never sends many visitors at once, so it can't tell you how the store holds up during a sale. For that, run a load test on a staging copy of the store, not on the live site.

What is a good speed score for a WooCommerce store?

Google rates a score of 90 or more as good, 50 to 89 as needs improvement and below 50 as poor. Compare mobile with mobile, since the mobile test runs on a throttled connection with a slowed CPU. For your server, the test uses Google's limits for how fast the page starts arriving: 800 ms or less is good and above 1,800 ms is poor. The comparison in your report uses 1,533 Shopify homepages, because we have no WooCommerce benchmark. Read it as a comparison with Shopify stores, not with other WooCommerce stores.

Does it check HPOS, Action Scheduler or my database?

No. HPOS, Action Scheduler and database queries live inside WordPress, and the test never logs in. It sees only what a first-time visitor can load. When the Speed Up Your Server card flags a slow server or a slow cart request, its step points you to Query Monitor for slow queries and plugins.

Does it work on plain WordPress, Shopify or other platforms?

Yes, it runs on any public store address and picks its steps from what it finds. A WordPress site without WooCommerce gets the WordPress steps without the WooCommerce ones. Shopify stores get Shopify steps, and the Shopify speed test page explains them. For any other platform, see the store speed test.
1,400+ stores audited

Need a full WooCommerce audit?

Speed is one reason shoppers leave. The full store audit looks for the others across your homepage, product pages and real cart, starting with a free preview.

Free preview  •  No credit card  •  Nothing to install