Keeping a store taking orders
Case studies of what went wrong on real WooCommerce stores, and guides to catching it early. For invented scenarios, see the examples.
- Case studies
How bot traffic on a shared server took a WooCommerce store offline
Scanner requests to a sister site used up the memory the store shared with it. Bot protection stopped the scanners, and also blocked the store's scheduled jobs.
Read the case study · 6 min · real site
- Case studies
Eleven minutes offline, and it wasn't a traffic surge
A store went down, the host blamed traffic, and the real cause was a daily report using all the memory.
Read the case study · 6 min · real site
- Guides
WooCommerce Monitoring: 5 Tools That Catch Problems Early
The five tools we'd put on any WooCommerce store that takes real money: what each one catches, what each one misses, and the habits that make them worth having.
Read the guide · 8 min
- Case studies
Two slowdowns nobody had noticed, found in the first hour
For years, a manufacturer’s WooCommerce site had been running with a PHP cache too small to hold its code, and an admin that waited a wasted second on almost every click. Neither showed up as an error anywhere. Operanse raised both within an hour of being connected.
Read the case study · 5 min · real site