Case study · grüum
How Urumi increased grüum's user satisfaction by 294%.
Cached requests went 4s → 0.3s. Uncached 5.7s → 0.4s. The platform held 1.2M req/day in production. The team stopped losing checkouts to timeouts and started shipping through their busiest weeks without an incident. Here's how.
Headline numbers
- 294% better user satisfaction
- 4s → 0.3s cached response time
- 5.7s → 0.4s uncached response time
- 1.2M req/day sustained production traffic
Engagement timeline
- Week 0 — Discovery + audit. Founders walked grüum's store with George — traffic patterns, plugin stack, the cold starts. Written audit + fix plan delivered.
- Week 1–2 — Cache + server config. Cloudflare misconfig fixed, server tuned, PHP worker config rebuilt. Cached responses dropped 4s → 0.3s.
- Week 3–4 — Hot paths + N+1 fixes. Application hot paths optimised, N+1 queries eliminated, WooCommerce Product Bundles patch shipped. Uncached 5.7s → 0.4s.
- Week 5+ — Migration + ongoing ops. Migrated to Urumi.ai infrastructure with zero downtime. P99 to <900ms. Engagement ongoing.
The context
When Urumi engaged with grüum.com, the team wanted to resolve performance instability that was directly affecting customer experience. Cached LCP would climb to 5–7 seconds, and intermittent cold starts could take up to ~40 seconds.
"I'm very happy with the results. The biggest performance improvements we've seen is from you guys."
George Lagonikas · Founder & CTO, grüum
The shift
In plain English: their site got fast and stayed fast. The engineer's view of what we found and what we fixed is below.
Urumi worked directly with George and the grüum team to identify root causes across caching, server configuration, and application hot paths. The focus was on fixing both the "everyday" slow paths and the unpredictable extremes that make a site feel unreliable.
From this work, grüum saw a shift around:
- Cloudflare + caching misconfigurations were identified and fixed.
- Performance hot paths were identified and fixed; a patch was provided to the WooCommerce Product Bundles team.
- Server configuration was optimized so workers could use the available infra more effectively.
- Latency-inducing N+1 query issues were fixed (traces went to almost 0 post-deploy).
- Cold starts caused by unoptimized PHP worker config were eliminated.
Cached requests went from 4s to 0.3s. Uncached requests dropped from 5.7s to 0.4s.
The outcomes
After Urumi's changes were deployed, grüum's New Relic data showed ~294% improvement in % satisfied users.
The grüum team validated the improvements with stress tests mimicking real user journeys (browse → login → add to cart → order):
- Average response time: 740ms with p95 at 3.03s
- Stress testing: Avg 770.09ms, Median 314.14ms, P90 1620ms
- Sustained well beyond grüum's 1.2M req/day production load, with p90 under ~2s at 300 VU
They went from customers abandoning checkout due to timeouts to completing orders without friction.
What this means for stores like yours.
grüum's numbers came from fixing the things that quietly slow every high-traffic WooCommerce store — misconfigured caching, N+1 database queries, untuned PHP workers, cold starts that the team only notices when checkout drops.
The free audit starts with the same diagnostic. We look at your traffic patterns, your plugin stack, your custom code, and the exact moments your store slows down for customers. Within a week you have a written audit + fix plan — yours to share internally, whether or not we end up running your operations.
"The results speak for themselves—I'm really happy we worked with Urumi."
George Lagonikas · Founder & CTO, grüum
Run your store on Urumi.
Production-ready today. Built for high-traffic WooCommerce stores where downtime moves revenue.
See the WooCommerce platform · Talk to founders
Agent live · 99.99% uptime · shipping today.
🦷 Can you believe it? This page was built by a dentist using urumi.ai