WooCommerce Server Optimisation UK

WooCommerce adds significant database load that a simple WordPress site does not have. Every product page involves queries for product data, stock levels, pricing, related products, and reviews. The cart and checkout involve session queries, tax calculations, shipping calculations, and payment gateway interactions. The WooCommerce action scheduler runs background jobs continuously. Order processing involves multiple database writes.

All of this means that the number of database queries per page load is much higher for WooCommerce than for a blog or brochure site, and performance problems that are invisible on a basic WordPress site become significant on WooCommerce.

PHP-FPM manages the pool of PHP worker processes that handle incoming requests. When a request arrives, a worker picks it up, runs the PHP for that page, and becomes available again. If all workers are busy, subsequent requests queue and wait.

Tuning PHP-FPM means calculating the right number of workers for your server's memory and your typical concurrent request load. Too few workers and requests queue under normal traffic. Too many workers and the server runs out of memory, which causes all workers to slow down or fail. The calculation is specific to your server size and your WordPress/WooCommerce memory usage per request.

WordPress and WooCommerce use an object cache to store the results of database queries and expensive computations temporarily. Without Redis, this cache only exists for the duration of a single PHP request and is discarded when the request ends.

With Redis, the object cache persists between requests. Product data, WooCommerce settings, transient values, session data, and the results of frequently repeated queries are stored in Redis memory and returned instantly on subsequent requests without hitting the database. For WooCommerce stores with substantial traffic, this reduces database load significantly and improves response times across every page.

Full-page caching works by storing a complete rendered HTML response and serving it to subsequent visitors without running PHP or querying the database. This is extremely effective for product and category pages where all visitors see the same content.

Cart and checkout pages show dynamic content that is different for every visitor: their specific cart contents, their address, their chosen shipping method. Caching these pages means one visitor's cart contents could be shown to another visitor, which breaks the checkout experience. These pages must be excluded from full-page caching while product pages benefit from it. Correct exclusion rules are a critical part of WooCommerce server configuration.

Not necessarily. Before recommending a migration, we audit your current server configuration. In many cases, the hardware is adequate but the configuration is suboptimal: PHP-FPM is not tuned, Redis is not installed, MySQL is running with defaults, and caching rules are wrong. Fixing the configuration on your existing server often delivers dramatic performance improvements without moving provider.

If your current hosting genuinely cannot provide a VPS environment with root access for server configuration, such as cPanel shared hosting, then a migration is necessary to apply these optimisations.

A CDN, or Content Delivery Network, is a globally distributed network of servers that stores copies of your static files, product images, CSS, JavaScript, and fonts, close to visitors. Instead of all requests coming to your origin server in one location, visitors receive static assets from the nearest CDN edge node.

For WooCommerce, a CDN reduces origin server load significantly because static assets typically account for most of the data transferred per page visit. Cloudflare's free CDN tier covers most WooCommerce stores adequately. For stores with large product catalogues and high image traffic, a purpose-built asset CDN may be appropriate.

Cost depends on the current state of your server configuration, your VPS provider, and the scope of optimisations needed. We start with a server audit to identify what is missing and what can be improved, then provide a fixed-price proposal for the work.

A focused WooCommerce server optimisation covering PHP-FPM tuning, Redis setup, MySQL configuration, and caching rules typically takes 2 to 3 days. We provide before and after benchmarks throughout the process.