Initace 
A WooCommerce store most often loads slowly for three reasons: hosting without a configured cache, product images at too high a resolution, and too many plugins running on every page, even where they are not needed. Before you start changing code or the theme, check these three things — they usually give the biggest effect at the lowest cost.
Hosting and cache
WordPress and WooCommerce build the page from scratch on every visit unless a cache is working — a mechanism that stores the finished page and serves it to the next visitors without recalculating. Cheap shared hosting without a server-side cache is a common reason for a slow store. It is worth checking whether the hosting offers it at server level (not only as a plugin) and whether the cart, checkout and customer account are excluded from it — those pages are different for each customer and cannot be served from a stored copy.
Product images
A product photo taken with a phone at full resolution can weigh several megabytes — and a category page can show dozens of photos at once. WordPress itself creates smaller versions of uploaded images and serves the browser the one that fits the screen, but that does not help if the theme or page builder displays the original. It is worth checking the format (WebP, and in newer WordPress versions also AVIF, are usually lighter than JPEG at the same quality), compressing the photos before upload and making sure that images below the first screen load only when the customer scrolls to them.
Too many plugins
Each plugin can add its own CSS and JavaScript files — and many of them do so on every page of the store, even if they work in only one place (for example in the cart). Good practice is a periodic review of installed plugins: whether all are still in use, whether two of them do the same thing, and whether the loading of their files can be limited to the pages where they actually work. The free Query Monitor plugin, switched on for a moment, shows which plugins and database queries take the most time.
How to check it yourself in 5 minutes
Go to the PageSpeed Insights site (pagespeed.web.dev), paste the address of a product page and switch the result to “Mobile”. Look mainly at the top part of the report, which is data from real Chrome users — if your store has too few of them, you will see only the lab test. Google considers a result good when, for at least 75% of visits:
- LCP (the time the largest element appears, usually the product photo) is at most 2.5 seconds,
- INP (how quickly the page responds to a click, for example choosing a variant) is at most 200 milliseconds,
- CLS (elements shifting during loading) is at most 0.1.
In the diagnostics part, also look at the server response time. If the server itself responds slowly (roughly: clearly longer than 0.8 seconds), the problem lies in the hosting or the cache, not in the images. Measure the home page, a category and a product page separately — each has different bottlenecks.
A common mistake: the main product image loaded “lazily”. WordPress itself skips lazy loading for the first large image and marks it as urgent, but image sliders and some speed-up plugins can override this. The result: the image the customer waits for most loads last, and the LCP score drops.
In short: start with hosting that has a cache, compressed images and a review of plugins, and measure the effect in PageSpeed Insights on a product page, on mobile.
No time to dig through the settings yourself? See what Aftercare covers.
