Aggregated patterns from real Magento projects. No client names — just numbers that repeat.
Based on structured audits across projects ranging from €2M single-store to €100M+ multi-country platforms.
Every audit finds between 8 and 15 issues that directly affect page load time or checkout speed. The most common: N+1 queries on category pages, missing block cache declarations, synchronous API calls in the checkout path.
The most common Magento performance anti-pattern. A product collection that loads attributes individually inside a loop, producing hundreds of queries on a category page that should require fewer than 10.
Category and product pages typically improve by 40–70% after addressing the top 5 findings from the audit. Checkout improvements are usually 30–50% — smaller because checkout is already more constrained.
Most common: unescaped output in custom templates, raw SQL queries, missing CSRF validation on custom admin routes, outdated third-party modules with known CVEs.
When integration logic moves out of Magento and into purpose-built services, these are the patterns we see.
Synchronous ERP calls during order save are the most expensive integration pattern in Magento. Moving them to an async Golang worker with retry logic removes them from the checkout critical path entirely.
Go-based order workers process 3–5× more orders per minute than equivalent PHP cron jobs, with lower memory usage and better error handling. The difference is most visible during peak traffic events.
Go services require fewer CPU cores and less memory than PHP processes handling the same workload. For high-volume import and sync tasks, the infrastructure savings are significant.
A concurrent Go importer with batching and backpressure replaces a serial PHP cron job. The 4-hour import becomes a 25-minute job with better error handling and resumability.
What changes when an experienced commerce architect embeds with the team — typically measured at the 90-day mark.
The percentage of sprint capacity consumed by maintenance, firefighting, and unplanned work. Process changes — explicit maintenance budgeting, code review standards, performance gates — bring this down within 2–3 sprints.
Not from working harder — from reducing rework, catching problems in code review instead of production, and eliminating the time spent debugging issues that better architecture would have prevented.
Combining code review standards, performance gates on deploys, and structured incident response. Most production incidents in Magento projects are preventable with review discipline.
The first 30 days are observation and audit. Days 30–60 introduce changes. Days 60–90 embed the habits. By day 90, the team owns the processes — the external advisor's job is to leave them self-sufficient.
Outcomes from Magento version upgrades and platform migrations.
A Magento patch release (2.4.x to 2.4.x+1) on a project with moderate customization and quarterly upgrade discipline. Includes dependency resolution, automated testing, and deployment.
Jumping 2+ minor versions or upgrading with high customization density (20+ custom modules, 15+ third-party modules). Includes UCT analysis, code fixes, full regression testing.
The audit identifies which customizations are upgrade-blocking (around plugins on frequently-changed core classes, preferences that conflict with new APIs). Remediating these before upgrading changes the risk profile.
Every migration project runs parallel environments during transition. Order data, customer data, catalog — validated row by row before cutover. The target is zero data loss, and that's what we deliver.
Every project is different, but the patterns are remarkably consistent. A conversation costs nothing — let's see if your situation matches.
Start a Conversation Learn About the Audit