Every 100 ms you give back, you keep in the cart
Storefront performance is a revenue line, and it is never under more pressure than during the hour you make most of your money. NimbusCDN caches the personalized page, rebuilds the images, and filters the bots — at the edge, before any of it becomes your origin's problem.
"Our pages are personalized, so we can't cache them"
You can cache almost all of them. A product page is a cacheable shell wrapped around three or four personalized fragments — the cart pill, the price for this customer's segment, a recommendations rail.
Edge Side Includes assemble those fragments at the PoP. The shell is served from cache in single-digit milliseconds; only the small dynamic parts touch your origin, and surrogate keys let you purge one SKU everywhere in under 300 ms.
p75 Largest Contentful Paint, field data, mobile. Illustrative figures for this design.
The drop sells out. The site stays up.
Flash sales, limited drops and Black Friday all share one shape: demand far beyond steady-state capacity, arriving in ninety seconds, half of it automated.
Fair-queue waiting room
Admit shoppers at a rate your checkout can actually sustain, in arrival order, with an honest position and wait estimate. A queue converts; a 503 does not.
Origin shielding
Request collapsing means a thousand simultaneous misses for the same object become one origin fetch. Your platform scales for steady state, not for the spike.
Inventory-aware rules
Rate-limit add-to-cart per account and per device, cap quantities at the edge, and block known resale automation before it reserves stock a human wanted.
| Request | Served | Bytes |
|---|---|---|
| Source (origin) | 4000px JPEG | 1.84 MB |
| Desktop, Chrome | 1200px AVIF | 94 KB |
| Mobile, Safari | 640px WebP | 38 KB |
| Mobile, slow 3G | 480px WebP q60 | 21 KB |
| Placeholder (LQIP) | inline blur | 0.6 KB |
No build step, no pre-generation, no second asset pipeline. Transformations are cached per variant at the edge.
Your catalogue is mostly pixels
On a typical retail page, images are 60–75% of transferred bytes and almost always the LCP element. We resize, re-encode and re-format on the fly, per device and per network condition, from whatever your merchandising team uploaded.
Peak traffic and peak fraud arrive together
The same event that brings your best customers brings scrapers, scalpers and card testers. Each gets a different response, decided at the edge in under a millisecond.
| Threat | What it looks like | Edge response |
|---|---|---|
| Scalper bots | Sub-second add-to-cart, residential proxy rotation, headless fingerprints | Behavioural score, challenge, per-account quantity cap |
| Price scraping | Full catalogue crawled nightly by a competitor | Rate limit per ASN, serve cached stale, block on repeat |
| Credential stuffing | Bursts of failed logins across many accounts from few IPs | Progressive challenge, breached-credential check, lockout at edge |
| Card testing | Many small authorisations against your payment endpoint | Velocity limits before the request reaches checkout |
| Inventory hoarding | Carts filled and abandoned to lock stock during a drop | Cart-hold limits enforced per identity, not per session cookie |
| L7 flood | Search and filter endpoints hammered with expensive queries | Managed WAF rules, request collapsing, origin shield |
Find out what your storefront is leaving on the table
Send us a URL. We will return a field-data breakdown of your LCP, your image payload and your cacheable-but-uncached routes — no contract, no agent to install.