Magento 2 Performance

Your Magento store is slow. The problem is not the server — it's the configuration.

Q: Why is Magento slow even with a powerful server?

Na maioria dos casos, o problema não é hardware — é configuração. Redis mal configurado faz o Magento ignorar o cache de objetos e processar cada request do zero. Varnish sem VCL correto não cacheia as páginas. MySQL sem índices adequados gera slow queries que travam o sistema. O diagnóstico identifica exatamente onde está o gargalo.

Q: What is Varnish and how does it help Magento?

Varnish é um HTTP accelerator que funciona como cache de página completa na frente do servidor. Com configuração correta do VCL para Magento, ele serve páginas de produto e categoria sem tocar o PHP, reduzindo drasticamente o TTFB e o consumo de CPU do servidor.

Q: Redis for session or object cache — what's the difference?

No Magento, Redis pode ser usado para dois tipos de cache: sessões de usuário (login, carrinho) e cache de objetos (configurações, EAV, layout). A configuração correta usa instâncias ou databases Redis separadas para cada tipo, com políticas de eviction e maxmemory distintas para evitar conflitos.

Q: Is Elasticsearch required in Magento 2.4?

Sim. A partir do Magento 2.4.0, o MySQL Search foi removido e o Elasticsearch (ou OpenSearch) tornou-se obrigatório para o catálogo de produtos. A configuração correta inclui número de shards, replicas e mapeamento de atributos de produto para busca relevante.

Misconfigured Redis, Varnish without correct VCL, MySQL without indexes and poorly tuned Elasticsearch make Magento waste available hardware and process every request from scratch.

Technical diagnosis identifies exactly where the bottleneck is — before any server upgrade or infrastructure investment.

Solicitar diagnóstico de performance Talk on WhatsApp

Technical stack

What is configured in each stack layer

Magento performance is the result of correct configuration at each layer — from cache to database. One misconfigured layer negates the gains of all others.

Object and session cache

⚡

Redis — object and session cache

Redis configuration for object cache and session cache with separate instances, correct eviction policies and maxmemory sized for the store's load profile.

Separate databases for objects and sessions

allkeys-lru eviction policies for object cache

maxmemory and maxmemory-policy configured by type

Hit rate and cache miss pattern diagnosis

Full Page Cache

🚀

Varnish — HTTP full page cache

Varnish configuration as HTTP accelerator with Magento-specific VCL — ensuring product and category pages are served without touching PHP.

Magento-generated VCL customized as needed

Cache exclusion rules for authenticated sessions

Cache purge integrated with Magento deploy

Cache miss and hit rate diagnosis in Varnish

Database

🗄️

MySQL — slow queries and indexes

Slow query analysis and optimization with slow query log activation, identification of unindexed queries and strategic index creation for Magento's load profile.

Activation and analysis of slow query log

Index creation on critical Magento queries

innodb_buffer_pool_size configuration

Diagnosis of unindexed tables and full table scans

Search and catalog indexing

🔍

Elasticsearch — search and catalog

Elasticsearch configuration for Magento 2.4+ with attribute mapping, number of shards and replicas appropriate for catalog size and optimized search relevance.

Search and filter attribute mapping

Shards and replicas configuration by catalog size

Slow query diagnosis in Elasticsearch

OpenSearch support (official replacement in M2.4.6+)

Audit

What is analyzed in the performance diagnosis

The diagnosis covers the full technical stack — not just measuring slowness, but identifying the exact cause in each layer and prioritizing interventions by real impact.

⚡

Redis: hit rate and eviction configuration

Current hit rate check, analysis of unnecessary evictions and policy review by cache type.

🚀

Varnish: cache hit rate and VCL

Analysis of configured VCL, verification of unnecessary cache bypasses and diagnosis of requests not being cached.

🗄️

MySQL: slow query log and explain plan

Analysis of slowest queries, verification of missing indexes and diagnosis of full table scans on Magento tables.

🔧

PHP-FPM and OPcache

PHP-FPM worker configuration, OPcache hit rate and opcache_memory_consumption tuning for Magento's codebase size.

🔌

Extensions impacting load performance

Identification of extensions adding unnecessary queries, blocking Magento's bootstrap or incompatible with granular cache.

📦

Assets, CDN and response compression

Analysis of static asset delivery, CDN configuration, Gzip/Brotli compression and cache headers for Magento static resources.

What you receive in the diagnosis

Technical report with impact-prioritized analysis — no unnecessary jargon, with clear action for each identified point.

✓

Analysis of each stack layer

✓

Prioritization by performance impact

✓

Root cause identification

✓

Action plan with estimated effort

✓

Delivery within 24 business hours

Request free diagnosis

Process

From analysis to production configuration

Every optimization is validated in staging before any production change — no regression risk or unexpected downtime.

Step 01

Stack audit

Full analysis of Redis, Varnish, MySQL, Elasticsearch, PHP-FPM and extensions — with prioritized diagnostic report.

Step 02

Intervention prioritization

Ordering optimizations by real store performance impact — prioritizing highest return with lowest risk.

Step 03

Staging validation

All configurations are applied first in staging with load tests and behavior verification before deploy.

Step 04

Deploy and monitoring

Production deployment with post-deploy monitoring, metric verification and fine-tuning based on real traffic.

Other Magento services

Complementary services for your store

Suporte

Magento Technical Support

Specialized technical support for fixes, PHP errors, extension conflicts and preventive Magento 2 store maintenance.

See service

Development

Development Magento

Custom modules with DI and Plugins, REST API integrations, theme customization and structured version upgrades.

See service

Overview

Magento 2 Specialist

Full overview of Magento services — support, development and performance for Open Source and Adobe Commerce stores.

See Magento page

FAQ

Questions about Magento performance

Frequently asked questions about Redis, Varnish, MySQL, Elasticsearch and how the optimization process works for Magento 2.

Send another question

Why is Magento slow even with a powerful server?

In most cases, the problem is not hardware — it's configuration. Misconfigured Redis makes Magento ignore the object cache. Varnish without correct VCL doesn't cache pages. MySQL without proper indexes generates slow queries that lock the system. The diagnosis identifies exactly where the bottleneck is before any infrastructure upgrade.

What is Varnish and how does it help Magento?

Varnish is an HTTP accelerator that acts as a full-page cache in front of the server. With correct VCL configuration for Magento, it serves product and category pages without touching PHP, drastically reducing TTFB and CPU usage — allowing the server to handle many more simultaneous requests.

Redis for session or object cache — what's the difference?

In Magento, Redis can be used for two types of cache: user sessions (login, cart) and object cache (configurations, EAV, layout). Correct configuration uses separate Redis instances or databases for each type, with distinct eviction policies and maxmemory — preventing sessions and object cache from competing for the same memory.

Is Elasticsearch required in Magento 2.4?

Yes. Starting from Magento 2.4.0, MySQL Search was removed and Elasticsearch or OpenSearch became required for the product catalog. Correct configuration includes number of shards, replicas and product attribute mapping to ensure relevant search and performance appropriate to catalog size.

How does the Magento performance audit work?

A auditoria analisa o stack técnico completo: configuração de Redis, VCL do Varnish, slow query log do MySQL, configuração do Elasticsearch, extensões que bloqueiam o carregamento, PHP-FPM and OPcache. O resultado é um relatório priorizado por impacto com ação clara para cada ponto identificado, entregue em até 24 horas.

Next step

Your Magento store deserves
real performance, not just
more expensive hardware.

Request a free performance diagnosis. We analyze the full technical stack and return with a prioritized report identifying where the real bottleneck is in your Magento 2 store.

Request performance diagnosis Talk on WhatsApp

Free Diagnosis, sem compromisso

Technical stack analysis delivered at no cost. Proceed only if it makes sense.

Response within 24 hours

Report with prioritized analysis of the main performance bottlenecks identified.

Always staging first

No configuration goes directly to production — everything is validated in staging before deployment.