Blog
WooCommerce slow? Images fix the storefront, not checkout
A slow WooCommerce storefront may be carrying heavy images. A slow checkout is usually code or the database. We measured one, not the other.
Last reviewed:
On this page
A WooCommerce store can feel slow in two different places. Heavy images can weigh down the storefront. A slow checkout or dashboard is usually code or the database. We fix the first problem, not the second.
That split matters. Categories, product pages, and the home page carry images by the hundred. Checkout, cart, and the WordPress dashboard do not.
We measured the storefront side. Across 41 real stores on 14 platforms, the 7 WordPress and WooCommerce stores — a small sample, and we say so — sent 2.5 to 2.7 times more bytes per pixel than the 12 Shopify stores. No stopwatch. Just image bytes.
Is it the checkout, or the storefront?
Open the page that is slow. The answer starts there.
| Symptom | Which half | Where to look first |
|---|---|---|
| Checkout slow, add-to-cart slow, wp-admin slow | Code and database — not images | Plugins, the database, the hosting. Usual suspects, none of them measured by us — and none of them touched by an image CDN. Ours included, said out loud. |
| Storefront slow: categories, product pages, home | Images, usually | Weigh them. It's free, and it's where the photos live by the hundreds. |
If checkout is slow, an image CDN is not the fix. Ours included. Check plugins, database queries, and hosting instead.
On the storefront, the largest visible element is often a product image. Google calls the moment it appears Largest Contentful Paint (LCP):
LCP measures the time from when the user initiates loading the page until the largest image or text block is rendered within the viewport.
— web.dev, Google's guide to optimizing LCP.
We do not measure how long your store takes to open. We measure image bytes. Load time also depends on the hosting, theme, scripts, and everything else on the page. The product image is simply a heavy part we can weigh.
What store images actually weigh
One real product image arrived as a 1,536 px JPEG weighing 176 KB. At the 800 px the screen needed, the AVIF version weighed 15.9 KB. That image was 91% lighter at the same perceived quality.
One image is not a catalogue. So we tested format separately: 14 images from two real stores, encoded 336 ways, with perceived quality equalized at SSIMULACRA2 70.
| Format | Against JPEG, median | Won on |
|---|---|---|
| WebP — the free plan's format | 21.8% lighter | 11 of 14 images |
| AVIF — the Pro plan's format | 32.1% lighter | 14 of 14 |
| AVIF against WebP | about 21% lighter still | 16 real derivatives, same width and quality |
Width matters too. Old uploads often keep traveling at their original size. We set a cap because we measured the alternative: for a 324-pixel space, the browser chose an image 42% heavier than another version the platform already had.
The math of a category page
Multiply the measured image by forty and the arithmetic gets loud. This is an illustration, not a measurement of a forty-image category on your store.
The same images also appear on product pages, search results, and related-product blocks. Repetition turns one heavy file into a catalogue problem.
What fixing it means for a store
Three things have to happen to every image. Re-uploading the catalogue is not one of them.
- Use the size the screen shows. Never send a wider version than the site already has ready.
- Use a lighter format. WebP on the free plan. AVIF on Pro, about 21% lighter than WebP in the measured comparison above.
- Deliver from a network, not the store's server. Each image is prepared once. After that, our network — 335 cities in more than 125 countries — sends it to visitors. We measured the boundary: once the image is on the network, the store's server receives no request for it.
This does not make a promise about checkout speed. It removes image delivery from the server. Those are different claims.
The free plan covers the home page, up to 50 new images a month in WebP. Category and product pages need the whole-site Pro plan: $9.90 a month, one price, AVIF, with no charge per visit, bandwidth, or image.
Weigh your store's images
Paste a category or product page into the website image size checker. It weighs every image there and encodes the heaviest ones for real. Today's number is measured. The other is estimated.
The estimate's median error is 6.2 percentage points for AVIF and 10.2 for WebP, measured on eight stores the model had not seen. That limit belongs next to the number.
If a blog post is the slow page, read why a WordPress site can feel slow. If you want to work inside the media library, the ShortPixel and Imagify comparison explains where each tool does the work.
- Paste the category or product page with the most images.
- Read both numbers. See which images carry the weight.
- If the store uses WooCommerce, install the connector. No account. No credit card. The home page starts shipping lighter right away.
Questions
Will this make my checkout faster?
We do not promise that. We measured image bytes, not checkout time. The network takes image delivery off the store's server; checkout performance still depends on code, database queries, hosting, and the plugins involved.
How many catalogue images can it cover?
The free plan covers the home page, with up to 50 new images a month in WebP. Pro covers every page and image in AVIF for a flat price, with no limit based on visits, bandwidth, or image count.
My store is not on WooCommerce. Can I still measure it?
Yes. Paste any public store page into the checker and it will weigh the images. The connector is for WordPress and WooCommerce today. Other platforms are planned, with no date.
Does it change my original product images?
No. Nothing is recompressed, moved, or deleted. The connector only changes the address used to deliver the images. Deactivate it and the store returns to the originals at once.