Traffic spikes of 500 percent in 30 minutes: capacity planning for small stores

A creator with 400,000 followers posts a 12-second video of your product. A niche newsletter with 40,000 subscribers features your store as its Friday pick. Neither event costs you anything, and neither one asks permission. Thirty minutes later your analytics dashboard shows a line going almost straight up, and somewhere in your stack, something that has never been tested past normal Tuesday traffic is starting to strain.

Most small stores never plan for this because it feels like a good problem to have. It is, right up until the site slows to a crawl, checkout starts timing out, and the moment that could have been your best day of the year becomes a pile of abandoned carts and a support inbox full of complaints. Capacity planning for a surprise 500 percent spike is not the same discipline as planning for a scheduled flash sale, and it is worth understanding the difference before it happens to you.

Why viral spikes are different from planned ones

A scheduled flash sale or a Black Friday campaign gives you warning. Traffic ramps up over hours or days, you can pre-warm caches, and you know roughly when the load will hit. A viral moment gives you none of that. Traffic can go from a normal trickle to five or ten times normal within the time it takes a video to be reshared a few thousand times, or a newsletter to be opened by its subscriber list in the first hour after send.

The unpredictability matters because most of the cheap fixes for planned spikes, like disabling non-essential apps the morning of a sale or pausing a marketing campaign until server load settles, only work if you know the spike is coming. With a viral spike you find out from the traffic itself, often after it has already started. If you have run a load test before (see how to load test your store before a flash sale without breaking it), you at least know roughly where your ceiling is. If you haven't, you are finding your ceiling live, in front of customers.

What actually falls over first

It is rarely the core platform. Shopify, WooCommerce, and BigCommerce are all built to handle far more concurrent traffic than a small store typically sees, and the platforms themselves have their own scaling infrastructure behind the scenes. What breaks first is almost always something layered on top.

Apps and plugins are the most common culprit. A recommendation widget, a reviews app, or a loyalty program that makes its own API calls on every page load can become a bottleneck long before the store itself struggles, especially if that app has its own rate limits or a slow third-party backend. Every additional script is another thing that can queue, time out, or silently fail under load; this is one reason a lean app list matters even outside of a spike (see how many apps is too many).

Checkout is the second common failure point, and the most expensive one, because it fails right at the moment of conversion. Payment gateway calls, tax calculation services, and inventory checks at checkout all add latency, and latency compounds under concurrent load. A checkout that takes two seconds normally can take twenty seconds when a thousand people hit it in the same minute. For a deeper look at where checkout tends to break even without a spike, see checkout is where stores silently bleed.

Image-heavy product pages are the third. If your product photos are large, unoptimized files served without a CDN, a spike in page views can saturate bandwidth or slow page load to the point where visitors leave before the page finishes rendering. This matters even more on mobile, where connection speeds are already the weaker link (see why your mobile conversion rate is half your desktop rate).

Cheap ways to be ready before it happens

You do not need enterprise infrastructure to survive a viral moment. Most of the preparation is about removing weak points, not adding capacity.

Audit your app list quarterly and remove anything that is not earning its keep. Fewer third-party scripts means fewer things that can slow down or fail under concurrent load, and it usually speeds up your site day to day as a side effect.

Use your platform's built-in caching and CDN features rather than working around them. Shopify, WooCommerce (with a caching plugin), and BigCommerce all offer ways to serve static content from edge locations closer to the visitor, which reduces load on your origin server during a spike. Compress and properly size product images; this is cheap, one-time work that pays off every time traffic jumps.

Keep a simple fallback plan for checkout specifically, since it is the highest-value part of the funnel to protect. Know who to call at your payment processor if something is behaving oddly, and understand what a gateway timeout looks like versus a genuine outage (see surviving gateway updates for related failure patterns).

Finally, know your inventory truth in real time. A viral spike on a single product can sell through your stock in minutes, and if your inventory counts across sales channels are already prone to drift, a spike is when that drift becomes an oversell problem instead of a minor annoyance (see [inventory counts that drift](/blog/inventory-counts-that-drift-why-your channels-disagree-and-how-to-catch-it)).

What to watch during the spike itself

Once traffic is climbing, the useful signal is not visitor count, it is conversion rate and page load time. A traffic spike with a stable or improving conversion rate is a good problem. A traffic spike where conversion rate is dropping fast usually means something in the funnel is straining, most often checkout or a slow app.

Watch for a widening gap between site visits and completed orders. If cart abandonment climbs sharply during the spike, that is often the earliest sign of friction rather than simple lack of interest (see cart abandonment spikes: reading the signal versus the noise). A brief spike in support messages about errors, slow pages, or failed payments is another early warning that is easy to miss if you are busy celebrating the traffic numbers.

This is exactly the kind of moment where continuous monitoring earns its keep. Cassian™ tracks uptime, page speed, and order flow together, so a slowdown or a drop in completed orders during a spike shows up as an alert rather than something you discover an hour later in your analytics. The Cassian Score™ gives you a single number to glance at when you do not have time to dig through five dashboards mid-spike.

The upside worth protecting

A viral moment is free marketing that most stores would pay for if they could. The goal of capacity planning is not to build for infinite scale, it is to make sure the free traffic actually converts instead of bouncing off a slow checkout or an out-of-stock page nobody caught in time. A lean app list, optimized images, a known checkout fallback, and a way to see slowdowns as they happen will cover most of what a 500 percent spike throws at a small store. The rest is simply enjoying the good problem while it lasts.