Free speed test
WooCommerce speed test
Test how fast your WooCommerce shop loads on a phone and a computer, and learn which shop features usually slow it down.
Test your site now
Enter your website address. We test your home page on a phone and on a computer.
Free, no account needed. Keep the page open: the test can take a minute or two.
What the test measures
We ask Google PageSpeed Insights to load your home page twice, once as a phone and once as a desktop computer. It is a lab test: it loads the page under fixed conditions, like a first-time visitor, so it shows how the page is built, not what every real visitor sees.
- Performance score
- A grade from 0 to 100 that Google's Lighthouse test works out from the timings below. 90 or more is good, 50 to 89 needs work, below 50 is poor.
- Largest Contentful Paint (LCP)
- How long until the biggest part of the page, usually the main image or headline, is visible. 2.5 seconds or less is good.
- First Contentful Paint (FCP)
- How long until the first text or image appears, so the visitor sees that the page is coming. 1.8 seconds or less is good.
- Speed Index
- How quickly the visible part of the page fills in as a whole. 3.4 seconds or less is good.
- Total Blocking Time (TBT)
- How long the browser is too busy running scripts to react to a tap or click. 200 milliseconds or less is good.
How to read your results
The test checks your shop's home page, which can usually be cached. Cart, checkout and account pages are built fresh for each customer, so they depend fully on your server. A slow FCP on the home page is a warning sign for those pages too. A high TBT in a shop often comes from payment, review and marketing scripts.
The estimate with fast.site
Next to your results you see an estimate of the same page with fast.site in front of your site. It is a calculation based on your results, not a measurement. To get real numbers, connect your site and run a live test.
Common reasons a WooCommerce shop is slow
Cart updates on every page
Some themes and plugins ask the server for the cart contents on every page view, even when the cart is empty. That request can't be cached, so it adds server work to each visit.
Pages that can't be cached
Cart, checkout and My account are different for every customer, so a cache has to skip them. On a slow server, these are the pages where customers wait, right before they pay.
Big product photos and galleries
Product pages often show several large photos and zoom images. Uploading them at the size they are shown keeps product pages light.
Filters, search and a cluttered database
Product filters and search ask the database many questions, more so with a large catalog. Expired sessions and data left behind by old plugins can make those questions slower over time.
Questions and answers
Does the test place an order or change my shop?
No. It only loads your public home page, like a visitor who just arrived. It doesn't add products to a cart, log in or change anything in your shop.
Why does the test check the home page and not the checkout?
The checkout needs a cart and a customer session, which a public test can't create. Use the home page as a guide: if your server is slow to start sending the page there, the checkout will feel slow too.
Can fast.site make a WooCommerce shop faster?
fast.site keeps ready copies of public shop pages, such as product and category pages, on servers near your visitors. Cart, checkout and account requests go straight to your server, so each customer's cart stays their own.
Is the speed test free?
Yes. You don't need an account or a payment card. To keep the test available for everyone, one connection can run a few tests in a row; after that, please wait a few minutes.
Why is my score different each time?
Lab tests vary a little from run to run, because the network, your server and outside scripts never answer in exactly the same time. Compare the timings, not only the score. Results are kept for some hours, so testing the same site again soon shows the saved result.
Next steps
Give your website 7 days. Let the results decide.
Start with your own domain, your own traffic and a clear understanding of what comes next.