Operanse
Sign inSign up

What went wrong on real stores

Problems on real WordPress and WooCommerce stores: what the owner would have seen, what was actually going on, and what fixed it. The sites are not named unless their owners have agreed. Every figure is as measured, and every fix was made by a person.

  1. Outages

    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

  2. Outages

    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

  3. Performance

    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