The 2026 Magento 2 Performance Checklist: 15 Fixes That Move the Needle
Slow stores lose sales. These are the fifteen Magento 2 performance fixes we apply first on every engagement — ordered by impact on real customers.
Every second of load time costs conversions. After auditing hundreds of Magento stores since 2013, these are the fixes we reach for first — roughly in order of impact.
Server and caching
- Full-page cache on Varnish, not the built-in file cache. Check your hit rate — anything below 80% needs investigation.
- Redis (or a Redis-compatible store) for the default cache and sessions, on separate databases.
- PHP 8.4+ with OPcache tuned: enough memory for your codebase and
validate_timestamps=0in production. - Production mode with compiled DI and pre-deployed static content.
- OpenSearch on adequate memory — search is often the hidden bottleneck on category pages.
Database and indexing
- Indexers on Update by Schedule with a healthy cron.
- Clean up huge tables: old quotes, logs, report events and the cron schedule.
- Enable the slow query log and fix the worst offenders from custom modules.
Frontend
- Move to Hyvä — the single biggest frontend win for most stores.
- Serve images in WebP/AVIF with correct sizes and lazy loading.
- Use a CDN for static and media files.
- Audit third-party scripts — chat widgets and trackers frequently cost more than Magento itself.
Code
- Profile with a tool such as Blackfire or New Relic and fix N+1 collection loads.
- Avoid uncached blocks on every page — one
cacheable="false"disables full-page cache for the whole page. - Remove unused extensions entirely, not just disable them.
Quick wins you can check today
php bin/magento deploy:mode:show php bin/magento indexer:show-mode grep -rn 'cacheable="false"' app/code app/design | head
How to measure Magento 2 performance properly
You cannot improve Magento 2 performance reliably without measuring it the right way. We use three kinds of data together:
- Real-user data. Google’s Core Web Vitals from real visitors show how fast your store feels on actual devices and networks. This is what customers — and search engines — experience.
- Server monitoring. An application performance monitoring tool shows slow database queries, slow third-party API calls and which modules use the most time.
- Repeatable lab tests. Test the same set of pages — home, category, product, basket and checkout — under the same conditions before and after every change.
Set a performance budget for each key page, such as a maximum Largest Contentful Paint, and check it on every release so improvements are not slowly undone. Adobe’s performance best practices are a useful companion to this checklist.
Want a full audit with a prioritised fix list? Book a Magento performance review.
