Cache the catalogue, not the basket
Product and category pages come from cache in milliseconds. Baskets, checkouts and accounts are never cached, so every customer sees their own order.
Shops that stay fast when it matters.
WooCommerce shops of every size, and large EC2 estates for clients with millions of visits. Fast catalogues, untouched checkouts.
WOOCOMMERCE, PROPERLY
Fast pages. Untouched checkouts.
We find what breaks caching
Plugins and payment gateways often hand every visitor a session cookie, quietly switching the cache off for everyone. We trace it and fix it at the source.
Hardened against bots
Login and xmlrpc floods, card-testing attempts and scraper storms are filtered before they reach PHP, so real shoppers keep the capacity.
Databases that keep up
Orders and stock sit on Amazon RDS with backups and restore points, and object caching takes the repeat queries off it.
CASE STUDY · IEG EMEA
Six WooCommerce sites, one tuned EC2 estate.
We look after iegemea.com, a WooCommerce multisite of six sites with around 900 product variations, on EC2 with Amazon RDS in the client’s own AWS account. When we started, every request hit PHP with no page caching at all, at around 700 ms to first byte.
5 msfor a cached page, down from 1.5 seconds rendered cold
99.9997%database buffer-pool hit ratio, with zero slow queries
15kxmlrpc attack requests in one day, now blocked at Cloudflare
~110 mshome, shop and product pages served as cache hits through Cloudflare
The fixes were specific: a payment gateway was handing every guest a session cookie, so almost nothing could be cached. We fixed that at the source, widened what’s safely cached, closed the brute-force routes and kept checkout untouched.
BIG CLIENTS, BIG ESTATES
When one server isn’t the answer.
For larger clients we design and run dedicated AWS estates, in their account or ours, sized to their traffic:
- EC2 instances sized and tuned for WooCommerce, with separate PHP pools per site.
- Amazon RDS with backups and restore points, and ElastiCache (Valkey) or Redis for objects and sessions.
- S3 and CloudFront for media, so product images don’t weigh down the web servers.
- Cloudflare in front for DNS, TLS, edge caching and bot filtering.
- Git-based deploys with atomic release switches and one-click rollback, so a launch doesn’t become an outage.
- Monitoring and daily reports in Discord, so problems surface before customers notice.
OUR OWN SHOP, TOO
We run stores we care about on the same stack.
Uni-Carts, a WooCommerce store in the AceMedia family, runs on AceHost with its product images served from its own CloudFront hostname. Every change we recommend to a client has usually run on one of our own sites first.