magento2-performance-audit

# Magento 2 Performance Audit This skill performs a comprehensive audit of Magento 2 performance, infrastructure, and code-level patterns. ## Related Skills **REQUIRED BACKGROUND:** Load `magento2-dev-core` first — code-level fixes for N+1 queries and heavy constructors follow the patterns it defines. Part of the QA trio with `magento2-linter` and `magento2-security-scan`. Async/queue findings often point back to `magento2-backend-dev`. ## Audit Categories ### 1. Infrastructure Configuration | Check | Expected | Command | |-------|----------|---------| | Application Mode | `production` | `bin/magento deploy:mode:show` | | PHP OPcache | >= 256MB | Check php.ini | | Redis (Session) | Enabled | Check `app/etc/env.php` | | Redis (Cache) | Enabled | Check `app/etc/env.php` | | Varnish | Running + terminating HTTPS/HTTP in front of the app | Check for a running Varnish container/process and its VCL config; the exact config file is project-specific (e.g. `nginx.conf`, a Docker/orchestrator config file, or a cloud provider's Varnish config) — there is no universal filename to grep for. | > On a **local dev environment** it's normal and expected to have no Redis/Varnish at all (file-based session/cache, FPC often disabled) — don't flag this as a bug unless the target is staging/production. Confirm which environment you're actually auditing before treating any of the above as a problem. ### 2. Cache Configuration ```bash # Verify all caches enabled govard sh -c "bin/magento c...