ThisCalculator

Everyday

How to Optimize Magento for Speed and Performance

Updated · Standard formula, shown below

How to Optimize Magento for Speed and Performance

This guide shows you how to speed up a Magento store by enabling caching, merging static files, and tuning server-level settings. You’ll learn the key steps that reduce page load times, improve user experience, and help with SEO rankings. Before starting, make sure you have admin access to your Magento backend and can edit server configuration files (via SSH or your hosting control panel).

What You’ll Need

  • Admin access to Magento (backend)
  • SSH access to your server (for command-line commands)
  • Access to your hosting control panel or server config files (e.g., nginx.conf, .htaccess)
  • Basic familiarity with Magento’s admin panel

Step-by-Step

  1. Enable All Caches – Go to System > Tools > Cache Management. Click Select All and then Enable. This activates the default Magento cache types (configuration, layout, block HTML, collections, etc.). After enabling, click Flush Magento Cache to clear any old data.
  2. Enable Flat Catalog (for large stores) – In Stores > Configuration > Catalog > Catalog > Storefront, set Use Flat Catalog Category and Use Flat Catalog Product to Yes. This reduces the number of database queries for category and product pages. Only do this if you have a large catalog (thousands of products) and your site uses simple product types.
  3. Merge and Minify CSS/JS – Go to Stores > Configuration > Advanced > Developer. Under CSS Settings, set Merge CSS Files to Yes and Minify CSS Files to Yes. Under JavaScript Settings, set Merge JavaScript Files to Yes and Minify JavaScript Files to Yes. This reduces the number of HTTP requests and file sizes.
  4. Enable HTTP Cache Headers – In the same Developer section, set Static Files Signatures to Yes (this appends a version to static files). Then, in your server config (e.g., .htaccess for Apache), ensure ExpiresActive On and ExpiresByType are set for CSS, JS, images, and fonts. This tells browsers to cache these files.
  5. Enable Gzip Compression – In your server config, enable Gzip for text files. For Apache, add mod_deflate rules. For nginx, use gzip on; and gzip_types. This reduces transfer size by up to 70%.
  6. Use a Content Delivery Network (CDN) – Sign up for a CDN service (e.g., Cloudflare, Fastly, or a Magento-compatible CDN). Configure it in Stores > Configuration > Web > Base URLs – set the Base URL for Static View Files and Base URL for User Media Files to your CDN domain. This offloads static content delivery.
  7. Enable Varnish Cache (if available) – Magento supports Varnish for full-page caching. In Stores > Configuration > Advanced > System > Full Page Cache, set Caching Application to Varnish. Then, download the Varnish VCL file from Magento and configure your server to use Varnish as a reverse proxy. This dramatically speeds up page delivery.
  8. Optimize Images – Compress all product images before uploading. Use tools like Photoshop or online compressors. Also, enable Image Resizing in Stores > Configuration > Catalog > Catalog > Image Config – set the appropriate sizes. Avoid uploading oversized images.
  9. Enable Database Query Caching – In Stores > Configuration > Advanced > System > MySQL Query Cache, set Enable Query Cache to Yes. This caches database queries and reduces load.
  10. Run Magento Compilation (for production mode) – If you’re in production mode, run php bin/magento setup:di:compile via SSH. This compiles dependency injection configurations and improves performance. Also run php bin/magento setup:static-content:deploy -f to pre-deploy static files.
  11. Enable Redis for Sessions and Cache – If your hosting supports Redis, configure it in app/etc/env.php for session storage and cache backend. This reduces database load and speeds up session handling.
  12. Use a Fast PHP Version – Ensure you’re running PHP 7.4 or newer (ideally PHP 8.1+). PHP 8 is significantly faster than PHP 7. Update via your hosting control panel or server package manager.
  13. Optimize Database – Run php bin/magento setup:db-schema:upgrade and php bin/magento setup:db-data:upgrade to keep the schema up to date. Regularly clean logs in System > Tools > Log Cleaning to keep the database small.
  14. Disable Unused Modules – Disable any third-party modules you don’t use. Go to Stores > Configuration > Advanced > Advanced and set Disable Module Output for unused modules. This reduces processing overhead.
  15. Test with a Performance Tool – After making changes, use Google PageSpeed Insights or GTmetrix to test your site. Aim for a score above 90. If issues remain, check the specific recommendations (e.g., lazy loading images, deferring JS).

Common Mistakes

  • Enabling Flat Catalog on small stores – This can actually slow down sites with few products because it adds complexity.
  • Merging JS/CSS without testing – Sometimes merging can break layout if files have dependencies. Always test thoroughly after enabling.
  • Forgetting to flush caches after changes – If you change config but don’t flush, old cached data may still be served.
  • Using a CDN without proper SSL – Make sure your CDN supports HTTPS to avoid mixed content warnings.
  • Not updating PHP – Running an old PHP version negates many performance gains.

Tips

  • Use a dedicated server or a high-performance VPS – shared hosting is often a bottleneck.
  • Set up a staging environment to test changes before applying to production.
  • Regularly monitor your site’s speed with tools like Pingdom or WebPageTest.
  • Consider using a performance-focused Magento theme that is lightweight.
  • Schedule cron jobs to run during low traffic hours to avoid resource spikes.

Troubleshooting

If your site breaks after enabling merge/minify, go to System > Tools > Cache Management and flush the JavaScript/CSS cache. If that doesn’t help, revert the settings to No and check if the issue resolves. For Varnish issues, ensure your VCL is correctly configured and that Varnish is running. If you see blank pages after running compilation, check the var/log/system.log for errors and run php bin/magento setup:upgrade to fix schema issues. If the site is slow despite all changes, check your server’s memory limits – increase memory_limit in php.ini to at least 256M.

Frequently Asked Questions

Does Magento 2 need a CDN?

Not strictly, but a CDN significantly improves load times for users across the globe by serving static files from edge servers.

What is the best cache type for Magento?

Varnish is the recommended full-page cache for Magento 2. It’s faster than built-in caching and reduces server load.

How do I know if my Magento is in production mode?

Check the app/etc/env.php file – the MAGE_MODE parameter will show production or developer.

Why is my Magento still slow after enabling all caches?

Common reasons include a slow server, unoptimized images, too many third-party extensions, or a lack of Varnish/Redis. Use a performance tool to identify bottlenecks.

Is it safe to disable module output?

Yes, but only for modules you don’t need. Disabling output for a module that is required for functionality can cause errors.

Can I use a plugin to speed up Magento?

Yes, there are extensions like Amasty Full Page Cache Warmer or MagePlaza Cache Cleaner, but they are not a substitute for proper server configuration.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.