Running the store yourself?
This guide covers the checks and fixes that protect store revenue, step by step.
Or hand the store to us
Our Commerce plan at $199/mo covers checkout testing, gateway monitoring and store speed work.
Last updated: August 2026
Why stores are harder to speed up than normal sites
Regular websites can be cached aggressively: one saved copy served to everyone. Stores cannot. Cart, checkout and account pages must be dynamic per visitor, product pages change with stock and pricing, and WooCommerce runs database queries on nearly every request. That is why the generic advice that makes brochure sites fast leaves stores sluggish.
Step 1: Product images
Stores have hundreds or thousands of images, so the compounding is brutal. Compress everything, serve WebP, set sensible dimensions rather than uploading 4000-pixel photos for 600-pixel slots, and lazy-load below the fold. On large catalogs this single step often halves page weight.
Step 2: Clean the database
WooCommerce stores accumulate expired sessions, abandoned cart data, order transients and stale logs at a rate normal sites never approach. Sessions in particular can grow into hundreds of thousands of rows. Clean them on a schedule with WP-Optimize or equivalent, always after a backup, and enable High-Performance Order Storage if you have not, since it moves orders to dedicated tables and speeds up large stores dramatically.
Step 3: Cart fragments
WooCommerce loads a script on every page to keep the mini-cart count live. On sites where the mini-cart is not visible, this adds an uncached request to every single page view for no benefit. Disabling cart fragments on non-shop pages is one of the highest-impact store-specific optimizations, and plugins exist that do it selectively without breaking the cart.
Step 4: Audit extensions
Stores accumulate plugins for shipping, tax, reviews, upsells, wishlists, analytics and abandoned carts. Each adds queries and scripts. Deactivate anything nobody has looked at in six months, and replace multi-purpose bloatware with focused tools. Test on staging: this is exactly where plugin conflicts surface.
Step 5: Cache correctly, never carelessly
Page caching for the shop and product pages, excluded absolutely for cart, checkout and my-account. Object caching with Redis genuinely helps stores because it caches the repeated database queries WooCommerce makes. And exclude checkout from every optimization plugin's minification and combination features, which is the most common cause of a store that is fast and cannot take orders.
Step 6: Hosting sized for a store
Uncacheable pages mean stores lean on the server far harder than brochure sites. Shared hosting shows this first at checkout, exactly when it costs money. A modest managed VPS with dedicated resources usually produces a bigger improvement for a store than any further plugin tuning, which is why our managed hosting is priced to sit alongside a maintenance plan rather than compete with it.
Test what actually matters
Do not judge a store by its homepage score. Test a product page, a category page with filters applied, and the cart, because that is the path customers take and the path that decides revenue.
FAQ
How fast should a WooCommerce store load? Aim for under 2 seconds on product pages, since checkout completion measurably degrades beyond that.
Will speeding up my store break checkout? Only if optimization is applied to checkout, which is why the exclusions above matter more than any single speed setting.
Do I need a CDN for a store? If customers are geographically spread, yes, for images and static assets. Keep dynamic pages off the CDN.
How much can a slow store realistically improve? Most neglected stores we take over improve 40 to 60 percent from images, database cleanup and cart fragments alone, before touching hosting.
Protect your store revenue automatically
Our Commerce plan covers weekly checkout and order-flow testing, payment gateway monitoring, staging, store speed work and peak-season readiness, so silent failures stop costing you orders.