Why Your Online Shop Slows Down When Sales Take Off (and How Load Balancing Helps)

Every Norfolk retailer knows the feeling of a promotion that works. The email goes out, the social posts land, and orders start coming in. Then the shop slows to a crawl, baskets freeze, and customers who were ready to pay give up.

If you sell online through WooCommerce or Magento, this is a common problem, and it usually has a straightforward cause.

The one-till problem

Picture a busy shop on the Saturday before Christmas with a single till open. However quick the cashier is, the queue grows and people leave their baskets behind.

An online store on one server is that shop. On a quiet Tuesday it copes. When hundreds of people click “add to basket” in the same minute, the server runs out of capacity and pages start timing out.

Stores are hit harder than ordinary websites because so much of what they do is live and personal. Each basket is unique. Checkout calculates stock, tax, shipping and discounts in real time and talks to a payment provider. A brochure site can serve the same cached page to everyone, but a store has to build much of each page afresh for every shopper.

What load balancing does

A load balancer sits in front of your servers and shares incoming visitors between two or more of them. Back to the shop: it’s the staff member at the front of the queue pointing each shopper to the shortest line.

It gives you three things:

• Room to grow. You add capacity by adding another server, rather than rebuilding the store on a bigger machine.
• Shared workload. No single server gets overwhelmed.
• Automatic health checks. If a server stops responding, visitors are sent only to the ones that work.

Customers never see any of this. To them it’s one website at one address.

Don’t forget the front door

Many people stop at “two servers”, but that only solves half the problem. If every visitor still arrives through one load balancer, you’ve moved the single point of failure rather than removed it.

A properly resilient setup, known as high availability, has two layers:

• At least two web servers, so one can fail or be updated while the other keeps serving.
• At least two load balancers, one active and one on standby, so a failure at the front door doesn’t take the shop offline.

As a bonus, you can do routine maintenance in the middle of the day instead of patching at 3am and hoping for the best.

It’s more than a load balancer

Adding a load balancer doesn’t fix everything by itself. For a store to work across several servers, a few other things need to be designed properly:

• Shared sessions, so a basket started on one server is visible to the others.
• Shared files, so product images are available everywhere.
• A well-sized database, which is usually the real bottleneck.
• Sensible caching that speeds up catalogue pages but never serves one customer’s basket or account details to another.
• Load testing before the sale, so you find what breaks while it’s still cheap to fix.

This is why “just add another server” rarely works. The setup needs to be designed as a whole, which is what a cluster is. The WebPulseLab guide to load balancing for WooCommerce and Magento covers the details, including how Nginx and LiteSpeed ADC compare.

Why shared hosting won’t get you there

Cheap shared hosting is fine for a small brochure site. For a store it carries real risk. You share a server with other websites, so someone else’s traffic spike can slow your checkout. You also hit strict resource limits during a rush, and you can’t install or configure a load balancer or failover at all.

Dedicated resources give you consistent performance and full control. They also give you a foundation you can build redundancy on.

Paying for peak capacity only when you need it

Many small businesses ask why they should pay all year for capacity they only need on a few days. On-demand cluster hosting answers that. You run a lean, resilient cluster day to day, then scale it up before Black Friday, the January sales or a product launch, and back down afterwards. WebPulseLab offers on-demand cluster hosting built around this model, so your costs follow your traffic.

The bottom line

A store that slows down during a sale is a store where one server behind one door is serving a crowd it wasn’t built for. Share the work across several servers, make sure no single failure can lock customers out, and run it on resources you control. Then your biggest promotion is a celebration instead of a crisis.

Looking for help with hosting, maintenance or support for your website? WebPulseLab provides website management and on-demand cluster hosting for UK businesses.