The WooCommerce speed of your online store is not a luxury; it is a direct factor in your revenue, your Google ranking, and the satisfaction of your customers. Research by Google shows that 53% of mobile visitors leave an online store that takes longer than 3 seconds to load. Every second of delay costs you an average of 7% conversion. For an online store with a monthly revenue of 10,000 euros, that means 700 euros less per month because of a slow site.

In this complete guide we take you step by step through all the optimizations that dramatically improve your WooCommerce speed. From LiteSpeed Cache configuration and Redis object caching to image optimization, database cleanup, and CDN settings. No vague tips, but concrete settings, code examples, and measurable results. Whether you are a beginning store owner or an experienced developer: after reading this article you will know exactly what to do.

At Theory7 WooCommerce hosting we run LiteSpeed Enterprise with NVMe SSD storage and Redis object caching. That is the foundation. But even on the fastest server there are optimizations that you as a store owner can carry out yourself to get the maximum out of your hosting.

Why is speed crucial for online stores?

Conversion impact: every second counts

The relationship between load time and conversion has been extensively researched and the figures are unmistakable. Amazon calculated that every 100 milliseconds of delay cost them 1% of revenue. Walmart reported that every second of faster load time yielded 2% more conversion. For an average Dutch online store the same principle applies, albeit on a smaller scale.

Load time	Bounce rate	Conversion impact	Revenue loss (at 10k/month)
0-1 second	Baseline (9%)	Optimal	None
1-2 seconds	+9% (18%)	-3 to -5%	-300 to -500 euros
2-3 seconds	+32% (41%)	-7 to -12%	-700 to -1,200 euros
3-5 seconds	+90% (81%)	-15 to -25%	-1,500 to -2,500 euros
5+ seconds	+123% (>90%)	-25 to -40%	-2,500 to -4,000 euros

As the table shows: the difference between an online store that loads in 1 second and one that takes 4 seconds can amount to thousands of euros per month. Speed optimization is therefore one of the most profitable investments you can make in your online store.

Google ranking and Core Web Vitals

Since the Page Experience Update, Google uses Core Web Vitals as an official ranking factor. For online stores, three metrics are crucial:

• LCP (Largest Contentful Paint): measures how quickly the largest visible element loads. For product pages this is often the main image. Target: under 2.5 seconds.
• INP (Interaction to Next Paint): measures how quickly your site responds to user interaction. Think of clicking "add to cart" or filtering. Target: under 200 ms.
• CLS (Cumulative Layout Shift): measures visual stability. Jumping elements caused by late-loading images or ads. Target: under 0.1.

An online store that scores "good" on all three metrics gets a ranking advantage over competitors who do not achieve this. In the competitive e-commerce market this can make the difference between page 1 and page 2 of Google.

User experience and trust

A fast online store feels professional and reliable. Customers who enter their credit card details online want to feel they are dealing with a serious party. A slow, stuttering site creates the opposite feeling. This effect is hard to express in figures but is recognized by every e-commerce entrepreneur: trust is the basis of online sales and speed is a building block of that trust.

Configuring LiteSpeed Cache for WooCommerce

At Theory7 WooCommerce hosting, LiteSpeed Enterprise is standard and you can install and configure the LiteSpeed Cache plugin directly. Below you will find the optimal settings specifically for WooCommerce.

Basic caching settings

Go to LiteSpeed Cache > Cache in your WordPress dashboard and configure the following settings:

Setting	Recommended value	Explanation
Enable Cache	On	Switches on the entire cache
Cache Logged-in Users	Off	Logged-in users see personal content (shopping cart)
Cache Commenters	Off	Prevents problems with review forms
Cache REST API	On	Speeds up WooCommerce API calls
Cache Mobile	Off (unless a separate theme)	Responsive themes serve the same HTML
Private Cached URIs	/cart, /my-account	Per-user caching for personal pages
Drop Query String	fbclid, gclid, utm_*	Prevents separate cache entries per tracking parameter

Cache exclusions for WooCommerce

WooCommerce has pages that should never be cached because they contain content unique to each user. Add these under LiteSpeed Cache > Cache > Do Not Cache URIs:

• /checkout/: the payment page must always be real-time
• /cart/: unique content per session
• /my-account/: personal details and orders
• ?add-to-cart=*: adding to the shopping cart via a URL parameter
• /wc-api/*: WooCommerce API endpoints for payments

In addition, you should exclude the following cookies under Do Not Cache Cookies:

• woocommerce_items_in_cart
• woocommerce_cart_hash
• wp_woocommerce_session_*

ESI (Edge Side Includes) for dynamic blocks

ESI is a powerful feature of LiteSpeed Cache that lets you keep parts of a cached page dynamic. This is perfect for WooCommerce: the product page can be fully cached while the shopping cart icon in the header shows the correct number of products in real time.

Activate ESI under LiteSpeed Cache > ESI:

1. Set Enable ESI to On
2. Set Cache Admin Bar to On
3. Set Cache Cart Widget to On. This is the key for WooCommerce. The shopping cart widget is treated as a separate ESI block and cached per session

With ESI configured, the rest of the page is served from the fast full-page cache while only the shopping cart element is built per user. This gives you the best of both worlds: the speed of full caching with the functionality of a dynamic shopping cart.

Object cache via LiteSpeed Cache

LiteSpeed Cache also offers a built-in object cache that works together with Redis (more about this in the next chapter). Go to LiteSpeed Cache > Object and configure:

• Object Cache: On
• Method: Redis
• Host: 127.0.0.1 (or the path to your Redis socket)
• Port: 6379
• Persistent Connection: On

How do you set up Redis object caching?

How Redis works for WooCommerce

Without Redis, every page view proceeds as follows:

1. Visitor opens a product page
2. WordPress runs 40-80 database queries
3. MySQL processes each query (reads from disk or its own cache)
4. Results are sent back to PHP
5. PHP builds the HTML page

With Redis, steps 2-4 are replaced by a single fast lookup in working memory. The result: the TTFB drops by 30-50% for non-cached pages. For logged-in users (who do not get a full-page cache) the difference is even greater.

Configuring Redis at Theory7

At Theory7, Redis is available from the Basic plan. The configuration is simple:

1. Redis is already activated at server level, so you do not have to request anything
2. Install and activate the LiteSpeed Cache plugin (if you have not already done so)
3. Go to LiteSpeed Cache > Object Cache
4. Set the method to Redis and the host to 127.0.0.1
5. Click Test Connection. You should see a green checkmark
6. Save and clear your cache

You can verify that Redis is active by going to LiteSpeed Cache > Object in your WordPress dashboard. There you will see statistics about cache hits and misses. A well-functioning Redis installation shows a hit ratio of 85% or higher.

Redis optimization for WooCommerce

By default Redis works fine, but for busy WooCommerce stores there are extra optimizations:

Setting	Default	Optimized	Reason
maxmemory	64 MB	128-256 MB	WooCommerce has more objects to cache
maxmemory-policy	noeviction	allkeys-lru	Removes the least recently used keys when memory is full
TTL (cache lifetime)	3600s	7200s	Product data does not change often, a longer cache is safe

If you notice that your Redis hit ratio drops below 80%, the memory is probably too small and objects are being removed too quickly. In that case, contact your hosting provider to increase the Redis memory.

Optimizing images

WebP format: smaller without loss of quality

WebP is a modern image format developed by Google that is 25-35% smaller than JPEG at the same visual quality. For product photos this means: sharper images that load faster. All modern browsers support WebP (Chrome, Firefox, Safari, Edge).

With LiteSpeed Cache you can enable WebP automatically:

1. Go to LiteSpeed Cache > Image Optimization
2. Set Auto Request Cron to On
3. Set Auto Pull Cron to On
4. Under the Image WebP Replacement tab: set to On
5. Click Send Optimization Request

LiteSpeed sends your images to their own optimization servers, converts them to WebP, and sends them back. This happens in the background without your site becoming slow. The original images are kept as a fallback.

Correct dimensions for product images

WooCommerce automatically generates multiple sizes of each uploaded image. Configure these under WooCommerce > Settings > Products > Display:

Image type	Recommended size	Used on
Catalog image	450 x 450 px	Shop overview page, category pages
Single product image	800 x 800 px	Individual product page
Product thumbnail	150 x 150 px	Shopping cart, cross-sells, gallery thumbnails

Upload your product photos in a size of at most 1200 x 1200 pixels. Larger images are scaled down, but the original still takes up storage space and the scaling costs processing time. For compression, use a quality level of 82-85%. This is the sweet spot where the human eye no longer sees a difference but the file size is significantly smaller.

Lazy loading: load what is visible

Lazy loading ensures that images are only loaded when they come into (or close to) the visible screen area. For a category page with 24 products, this means that only the first 6-8 images are loaded immediately. The rest follow only as the visitor scrolls down.

LiteSpeed Cache offers excellent lazy loading:

• Go to LiteSpeed Cache > Page Optimization > Media Settings
• Set Lazy Load Images to On
• Set Basic Image Placeholder to On. This shows a light gray background while the image loads
• Set Responsive Placeholder to On. This prevents layout shifts (CLS) by reserving the correct space
• Set Lazy Load Iframes to On, for embedded videos on product pages

Important: exclude your top product image (hero image) from lazy loading. This element determines your LCP score and must load as fast as possible. You can do this by adding the CSS class of your hero image to the Lazy Load Image Excludes.

Compression checklist for product photos

Follow this step-by-step plan for every product photo you upload:

1. Take the photo in high resolution (at least 1200 x 1200 px)
2. Edit and crop to the desired size
3. Export as JPEG with quality 85% or as PNG for images with transparency
4. Compress with a tool such as ShortPixel, Imagify, or Squoosh (free online)
5. Upload to WordPress. LiteSpeed Cache automatically creates a WebP version
6. Check that the file size stays under 200 KB per image

Cleaning up the database

The biggest culprits

The following data types are the most common causes of a slow WooCommerce database:

Post revisions

By default WordPress saves every change as a separate revision. A product that has been edited 20 times has 20 revisions in the database. With 500 products, that is potentially 10,000 extra rows. Limit revisions by adding this line to your wp-config.php:

• define('WP_POST_REVISIONS', 3);: keeps at most 3 revisions per post/product

You remove existing old revisions with the following SQL query (make a backup first):

• DELETE FROM wp_posts WHERE post_type = 'revision' AND post_date < DATE_SUB(NOW(), INTERVAL 30 DAY);

Expired transients

Transients are temporary data that WordPress and plugins store in the wp_options table. WooCommerce makes intensive use of transients for product caches, session data, and temporary calculations. Expired transients are not cleaned up automatically and pile up.

• DELETE FROM wp_options WHERE option_name LIKE '_transient_timeout_%' AND option_value < UNIX_TIMESTAMP();
• DELETE FROM wp_options WHERE option_name LIKE '_transient_%' AND option_name NOT LIKE '_transient_timeout_%' AND option_name IN (SELECT REPLACE(option_name, '_transient_timeout_', '_transient_') FROM (SELECT option_name FROM wp_options WHERE option_name LIKE '_transient_timeout_%' AND option_value < UNIX_TIMESTAMP()) AS expired);

Expired WooCommerce sessions

WooCommerce stores shopping cart sessions in the wp_woocommerce_sessions table. On busy online stores, this table can quickly grow to tens of thousands of rows. Expired sessions are not always cleaned up neatly:

• DELETE FROM wp_woocommerce_sessions WHERE session_expiry < UNIX_TIMESTAMP();

The wp_options table: the hidden bottleneck

The wp_options table is a common hidden bottleneck. WordPress loads all rows where autoload = 'yes' on every page view. In a typical WooCommerce installation with 30 plugins, there can be hundreds of autoloaded options that are loaded on every request, even when they are not needed.

Check the size of your autoloaded data:

• SELECT SUM(LENGTH(option_value)) AS autoload_size FROM wp_options WHERE autoload = 'yes';

If this number exceeds 1 MB, optimization is needed. Many plugins load their full configuration as autoload while this is not necessary. You can find the biggest culprits with:

• SELECT option_name, LENGTH(option_value) AS size FROM wp_options WHERE autoload = 'yes' ORDER BY size DESC LIMIT 20;

Automated cleanup with WP-Optimize

Running SQL queries manually is error-prone. Rather use a plugin such as WP-Optimize for automated cleanup:

1. Install and activate WP-Optimize
2. Go to WP-Optimize > Database
3. Select: old revisions, auto-drafts, deleted posts, spam comments, expired transients
4. Click Run all selected optimizations
5. Under the Settings tab: schedule a weekly automatic cleanup

Speeding up the checkout page

Minimize plugins on the checkout

Many WordPress plugins load their CSS and JavaScript on every page, including the checkout. This is unnecessary and harmful. Use a plugin such as Asset CleanUp or Perfmatters to decide per page which scripts are loaded:

• Deactivate contact form plugins on the checkout (Contact Form 7, WPForms)
• Deactivate social media widgets and sharing buttons
• Deactivate sliders and animation scripts
• Deactivate analytics scripts that are not essential for conversion tracking
• Deactivate chat widgets (or load them only after 5 seconds via defer)

The goal: the checkout page loads only WooCommerce core, your theme, the payment provider, and essential tracking. Nothing more.

Direct payment: fewer steps, faster conversion

The more steps and page loads your checkout requires, the more chances there are to lose customers. Optimize the payment process:

• One-page checkout: use a plugin such as CheckoutWC or activate the WooCommerce Block Checkout that shows everything on one page
• Express payment methods: Apple Pay, Google Pay, and iDEAL-direct drastically reduce the number of clicks
• Guest checkout: do not require creating an account for an order. Offer it optionally after checkout
• Address auto-complete: use the PostcodeAPI or Google Places Autocomplete so customers only enter their postcode and house number

Prefetching checkout resources

You can let the browser fetch resources in advance that are needed on the checkout. Add this code to your theme's functions.php or via a code snippets plugin:

• Add dns-prefetch for your payment provider (e.g. Mollie, Stripe, MultiSafepay)
• Add preconnect for external domains used on the checkout
• On the shopping cart page: add prefetch for the checkout page CSS and JS

This way the connections to external services are already set up before the customer clicks "checkout", which noticeably shortens the perceived load time of the checkout.

Configuring a CDN with QUIC.cloud

Why QUIC.cloud for LiteSpeed hosting

QUIC.cloud is the CDN developed specifically for LiteSpeed servers. It distinguishes itself from generic CDNs such as Cloudflare on one crucial point: it can also cache and optimize dynamic content. For WooCommerce this means that even non-cached pages are served faster.

Benefits of QUIC.cloud for WooCommerce:

• Dynamic page caching: caches product pages at CDN level, including ESI support for shopping carts
• Image optimization: converts and compresses images on the fly to WebP
• CSS/JS optimization: minifies and combines files at CDN level
• QUIC protocol: faster connection setup than traditional TCP, especially noticeable on mobile
• DDoS protection: protects your online store against attacks

Setting up QUIC.cloud via LiteSpeed Cache

The configuration is done entirely through the LiteSpeed Cache plugin:

1. Go to LiteSpeed Cache > CDN
2. Click QUIC.cloud and create a free account (or log in)
3. Link your domain. QUIC.cloud generates an API key
4. Enter the API key at LiteSpeed Cache > General > Domain Key
5. Set CDN to On
6. Configure the CDN Mapping: add your static file folders (wp-content/uploads, wp-includes)

QUIC.cloud offers a free tier that is sufficient for most small to medium-sized online stores. For busy stores with a lot of traffic there are paid plans with more bandwidth and advanced features.

Core Web Vitals for online stores

LCP (Largest Contentful Paint) for product pages

On a product page the LCP element is almost always the main product image. Optimize it as follows:

• No lazy loading on the main image: this is the LCP element and must load immediately
• Add a preload hint for the product image. This tells the browser to fetch the image with priority
• Serve the correct dimensions: a 3000 px wide photo displayed at 800 px wastes bandwidth
• Use WebP or AVIF: smaller files load faster
• Avoid CSS background images for products, because the browser discovers these later than normal img tags

On category pages the LCP element is often the first product image in the grid or a category banner. Make sure this element has no lazy loading and can load as fast as possible.

INP (Interaction to Next Paint) for interactive elements

INP measures how quickly your site responds to interaction. For WooCommerce the critical interactions are:

Interaction	Common problem	Solution
Add to cart	JavaScript blocking by heavy scripts	Defer non-essential JS, use native AJAX add-to-cart
Product filters	Full page reloads on filter	AJAX-based filters (FacetWP, FLAVOR)
Selecting a variation	All variations are loaded as JSON	Limit variations or use AJAX-loaded variations
Search function	Slow database queries on live search	Elasticsearch or Algolia for instant search
Checkout form	Validation blocks interaction	Async validation, debounce input events

You achieve the biggest INP improvements by deferring heavy JavaScript. Go to LiteSpeed Cache > Page Optimization > JS Settings and set JS Defer to On. This ensures that JavaScript files are only executed after the page has been rendered.

Preventing CLS (Cumulative Layout Shift)

Layout shifts are particularly annoying in online stores. Imagine: a customer wants to click "add to cart", but at that moment an element shifts down because of a late-loading image or ad, and the customer accidentally clicks somewhere else. Frustrating and bad for your conversion.

Prevent CLS in WooCommerce:

• Define dimensions for all images: make sure width and height attributes are present on every img tag
• Reserve space for product thumbnails: use aspect-ratio in CSS for your product grid
• Load fonts locally: web fonts loaded from Google Fonts cause a flash of unstyled text. Use a tool such as OMGF to host Google Fonts locally
• Avoid inject scripts above the fold: ads, review widgets, and social proof popups should load below the fold or after interaction
• Set min-height on dynamic elements: review sections, related products, and upsell blocks

Hosting as the foundation of speed

Why all optimization fails on slow hosting

Suppose your hosting has a TTFB of 800 ms. That means the server needs 800 ms just to send the first byte to the browser. No frontend optimization can win back those 800 ms. On good hosting with LiteSpeed and NVMe SSD, that TTFB is 80-150 ms, a difference of more than half a second before the browser has even started rendering.

The same logic applies to database queries. If your MySQL server runs on an overloaded shared server with HDD storage, every query takes longer. Redis can cache frequently used queries, but a cold cache or a complex WooCommerce query (for example when filtering 5,000 products) still has to go to the database. On NVMe SSD that query is 10-35x faster than on HDD.

What distinguishes WooCommerce hosting from ordinary hosting

Not all hosting is suitable for WooCommerce. An online store places different demands than a blog or company website:

Characteristic	Blog/company site	WooCommerce online store
Database intensity	Low (10-20 queries/page)	High (40-100 queries/page)
Dynamic content	Little (most is cacheable)	A lot (shopping cart, prices, stock)
Peak moments	Gradual	Extreme peaks (sales, holidays)
PHP memory needed	128 MB is enough	256-512 MB recommended
Cron jobs	Minimal	Intensive (stock sync, price updates, emails)
SSL performance	Important	Critical (checkout security, customer trust)

This is exactly why Theory7 WooCommerce hosting is optimized for these specific demands. LiteSpeed Enterprise with LSAPI processes PHP requests up to 6x faster than Apache. NVMe SSD storage delivers the IOPS that WooCommerce needs for all those database queries. Redis object caching catches repeated queries. And HTTP/3 with QUIC ensures faster connection setup, especially important for mobile shoppers.

Choosing the right hosting for your online store

Not every online store needs the same hosting. Consider the following factors in your choice:

• Number of products: up to 500 products: shared hosting is enough. 500-5,000 products: consider a powerful shared plan or a VPS. More than 5,000 products: a VPS or dedicated server is recommended.
• Expected traffic: up to 50,000 visitors per month: shared hosting. 50,000-200,000: a VPS. More: dedicated or cloud hosting.
• Growth plans: do not start too small if you expect to grow quickly. Migrating is always a risk and costs time.
• Technical knowledge: managed hosting (such as at Theory7) means the server is managed and optimized for you. Unmanaged is cheaper but requires technical knowledge.

A good rule of thumb: invest at least 5-10% of your monthly store revenue in hosting. An online store with 5,000 euros of monthly revenue can run perfectly on WordPress hosting from a quality provider. At 20,000+ euros per month it pays to look at a VPS or higher tier.

Step-by-step action plan

Week 1: measuring and basics

1. Measure your current speed with Google PageSpeed Insights and GTmetrix (note all scores)
2. Check your PHP version and upgrade to 8.2 or 8.3
3. Install and configure LiteSpeed Cache with the WooCommerce settings from this article
4. Activate Redis object caching
5. Measure again and compare

Week 2: images and database

1. Activate WebP conversion via LiteSpeed Cache Image Optimization
2. Configure lazy loading (excluding hero images)
3. Check your product image dimensions and adjust them
4. Run a database cleanup with WP-Optimize
5. Schedule a weekly automatic cleanup

Week 3: checkout and frontend

1. Audit which scripts load on the checkout and deactivate the unnecessary ones
2. Activate JS Defer and CSS minification in LiteSpeed Cache
3. Configure font optimization (hosting Google Fonts locally)
4. Test your Core Web Vitals and fix any CLS problems
5. Consider activating the QUIC.cloud CDN

Week 4: fine-tuning and monitoring

1. Run a full speed test and compare with your baseline from week 1
2. Set up monitoring via Google Search Console (Core Web Vitals report)
3. Configure uptime monitoring so you are warned about problems
4. Document your configuration so you can quickly fall back if there are problems

If you follow this action plan, you will have a significantly faster online store after 4 weeks. Most WooCommerce stores see an improvement of 40-70% in load time after carrying out these optimizations. And that translates directly into better Google rankings, higher conversion, and more revenue.

Do you want to start right away with a fast foundation? Take a look at our guide on fast WooCommerce hosting or discover what managed WooCommerce hosting can mean for your online store. An optimized server combined with the tips from this article gives your online store the fastest foundation there is.

Frequently asked questions about WooCommerce speed

How fast should a WooCommerce online store load?

A WooCommerce online store should ideally be fully loaded within 2 seconds. The TTFB (Time to First Byte) should be under 200 ms. Every extra second of load time costs you an average of 7% conversion. Google also rewards fast online stores with a better position in the search results.

Which caching plugin is best for WooCommerce?

LiteSpeed Cache is the best caching plugin for WooCommerce if your hosting runs on LiteSpeed. The plugin communicates directly with the web server and supports ESI (Edge Side Includes), which lets you cache dynamic elements such as shopping carts. For non-LiteSpeed hosting, WP Rocket or W3 Total Cache are good alternatives.

What is Redis object caching and why is it important for WooCommerce?

Redis is an in-memory database that caches frequently used database queries in working memory (RAM). WooCommerce runs dozens of database queries on every page view for products, prices, stock, and sessions. Redis catches these so they do not have to be read from the database over and over. This lowers the TTFB by 30-50%.

How much faster does my online store become by optimizing images?

Images make up on average 60-70% of the total page weight of a WooCommerce online store. By switching to WebP format, enabling lazy loading, and using correct dimensions, you can reduce the page weight by 50-80%. This results in load times that are 1-3 seconds faster.

How often should I clean up my WooCommerce database?

Schedule a weekly automatic database cleanup via WP-Optimize or a similar tool. Remove expired transients, old revisions, spam comments, and expired sessions. For busy online stores with more than 100 orders per day, daily cleanup is recommended. A clean database is directly noticeable in faster load times.

Sources and references

• Google PageSpeed Insights (pagespeed.web.dev)
• WooCommerce, official documentation (woocommerce.com)
• Cloudflare, Learning Center (cloudflare.com/learning)
• GTmetrix, Website Performance Testing (gtmetrix.com)