Magento optimization case studies, three anonymised stores

Every client engagement is covered by a non-disclosure agreement that prevents me from naming the brand or publishing exact metrics. The architecture, bottlenecks and fixes are accurate to the actual projects, and the numeric ranges are within the real lift seen. If you need named references, I can supply them privately on a discovery call.

Audit takes ~5-8 hours of my time, delivered as a written report within a week. The sprint itself ranges from ~40 hours (CLS / INP tune on an existing Hyvä store) to ~110 hours (backend + cache + indexer overhaul on enterprise B2B). Full Luma to Hyvä migrations typically land between 80 and 180 hours depending on theme complexity and module count.

No. Case 2 hit its targets without touching the frontend at all, the bottleneck was Varnish + Redis + indexer config. Case 3 was already on Hyvä when I arrived. Hyvä is the right answer when frontend JavaScript is the bottleneck, but on B2B / enterprise stores the bottleneck is often the database or the cache layer instead.

Targets are agreed in the audit report. The default targets I aim for are: mobile LCP under 2.5s, INP under 200ms, CLS under 0.1, FPC hit rate above 70%, TTFB under 600ms on a cold category page. If I cannot hit a target due to scope outside the sprint (e.g. a third-party app the client refuses to remove), it is called out in the report before the sprint starts.

Same playbook. Case 2 was Adobe Commerce. The only difference is licence-specific tooling, Adobe Commerce ships with B2B modules, the page builder, and Live Search that need their own performance review. I am Adobe Certified Magento 2 Developer (cert issued September 2021), so the Adobe Commerce surface area is covered.

Conversion lift is measured against the same traffic source and audience cohort over a 60-day window before/after deploy, using the client's GA4 or Adobe Analytics. I never claim a conversion lift from Lighthouse-only data, that would be dishonest. Where conversion data is not available, I report only the Core Web Vitals and server-side metrics that I can verify directly.

Yes, this is how most engagements actually run. I work alongside an internal Magento team or another agency, deliver the audit and the architectural plan, and either implement the high-leverage changes myself or hand the spec to your team and review their PRs. Both shapes work; the hand-off shape is cheaper.

The $499 audit on its own. You get the written report, the prioritised fix list, the Lighthouse traces and the server-timing breakdown, and you are free to give that document to your internal team or another agency. About 30% of audit clients do exactly that and never come back for the sprint, which is fine.

Ranges only, anonymised, as on this page. If a client gives explicit written permission to publish their store name and full metrics, I will, but I do not ask for that permission unless they offer it first, because the case-study marketing benefit goes to the client, not the developer.

Use the get in touch page or message me on Upwork. The first call is 30 minutes, no charge. If it looks like a fit, I send a scope for the $499 audit and we get going within a week.