Slow stores lose customers. I audit your Magento 2 stack end-to-end — from database queries to browser rendering — and fix the actual bottlenecks, not the obvious ones.
FPC hit rate analysis, cache hole identification, ESI block configuration, and Varnish VCL review for maximum cache coverage.
Slow query log analysis, N+1 query elimination, missing index identification, and EAV collection optimisation.
RequireJS bundle analysis, dead code elimination, critical CSS extraction, and lazy loading for non-critical assets.
LCP, CLS, and INP improvements: image optimisation, font loading strategy, layout shift elimination, render-blocking resource removal.
Identifying which extensions add observer overhead, slow admin queries, or unnecessary JS weight on the frontend.
PageSpeed, GTmetrix, and real-user timing benchmarks before and after. Written report with prioritised recommendations.
PageSpeed scores, WebPageTest traces, slow query logs, and FPC hit rate measured before any changes. No guessing.
I trace the complete request lifecycle: DNS → server → PHP → MySQL → FPC → CDN → browser. The bottleneck is rarely where people expect.
Ranked list of fixes by impact vs effort. Some changes take 30 minutes and halve TTFB. Others are longer projects. I separate them clearly.
Every fix applied on staging first, benchmarked, then deployed to production with monitoring active.
Post-deployment benchmarks confirming the improvement. Written summary you can share with stakeholders or your hosting provider.
I measure before I change. If a fix doesn't show up in the numbers, it didn't help — and I'll tell you that honestly.
I don't just run Lighthouse and follow its suggestions. I trace the actual request to find where time is really being lost.
Every configuration change is tested on staging before production. Cache and server changes can break things if done carelessly.
You get a written report with benchmarks — not just a list of things I did. Something you can act on, share, or refer back to.
Our TTFB went from 1.8s to 310ms after the Varnish VCL and Redis reconfiguration. Faouzi identified the cache hole in our layered navigation within the first hour of the audit.
It’s not just running bin/magento setup:static-content:deploy with more locales. Real Magento performance work means understanding where time is spent across the full stack and fixing the biggest issues first.
The most common wins I find: FPC miss rate above 30% due to misconfigured Varnish, Redis being evicted under load due to a wrong maxmemory policy, and blocking JavaScript that delays Time to Interactive on product and category pages.
Share your PageSpeed score and hosting setup. I'll give you an initial read on where the time is being lost — before we even start.
Pick the category that fits, or skip straight to a free call if you're not sure yet.
Let's talk about your project with no commitment. Free 30-minute discovery call — I'll help you figure out what you need.
Book Free Call →