Magento Page Speed Optimisation: A Practical Guide

A fast Magento store makes it easier for customers to browse products, compare options and complete a purchase. It can also support better engagement and search visibility. Speed is not controlled by one setting, however: hosting, themes, extensions, images, caching and third-party scripts can all affect how quickly a page loads.

This guide covers practical ways to improve page speed on Magento 2, from measurement and server configuration to front-end optimisation.

Start by measuring performance

Before making changes, establish how your store performs. Test key pages separately, including the home page, category pages, product pages, search results and checkout. A store may load quickly on a simple page but struggle on pages with large product galleries or complex filters.

Useful tools include Google PageSpeed Insights, Lighthouse and WebPageTest. Review both laboratory tests and real-user data where available. Pay particular attention to Core Web Vitals:

• Largest Contentful Paint (LCP): how quickly the main visible content loads.
• Interaction to Next Paint (INP): how quickly the page responds to user interactions.
• Cumulative Layout Shift (CLS): how much the page layout moves unexpectedly.

Test on mobile as well as desktop, and repeat tests under consistent conditions. A single score is only a snapshot; look for the biggest bottlenecks and track changes over time.

Choose suitable hosting and infrastructure

Magento can require significant server resources, particularly on stores with large catalogues, heavy traffic or many extensions. If pages are slow even when the cache is warm, investigate the server before focusing solely on front-end changes.

Check that your hosting environment meets the requirements of your Magento version and is configured appropriately. Review CPU and memory usage, storage performance, PHP configuration and database response times. A production store should also use a supported PHP version and an appropriate PHP-FPM configuration.

For larger stores, consider whether the architecture needs separate services for the web application, database, search and caching. The right setup depends on your catalogue, traffic and operational requirements; adding infrastructure without monitoring can increase complexity without solving the underlying issue.

Configure Magento caching

Caching reduces the work required to serve pages repeatedly. Confirm that Magento’s production caches are enabled and that the store is not running in developer mode in a live environment.

Magento supports full-page caching, and many production deployments use Varnish to serve cached pages efficiently. Configure and test the cache carefully, particularly where pages contain customer-specific content. Cart details, account information and other personalised elements must not be exposed through a shared cache.

After changing cache settings or deploying code, clear or refresh the relevant caches. Also check that cache invalidation works as expected when products, prices or content are updated.

Optimise images

Product images are often among the largest assets on a Magento page. Oversized files can delay the main content, especially on mobile connections.

• Resize images to suit the dimensions at which they are displayed.
• Compress images while maintaining acceptable visual quality.
• Use modern formats such as WebP where your storefront and delivery setup support them.
• Provide explicit width and height values to help prevent layout shifts.
• Lazy-load images below the initial viewport, but avoid lazy-loading the main image that users see first.

Review image handling across product listings, product detail pages, banners and promotional content. A single large hero image can have a disproportionate effect on LCP.

Reduce JavaScript and CSS overhead

The theme and extensions can add scripts and stylesheets to every page. Too much front-end code may delay rendering or make interactions feel sluggish.

Audit the code loaded on important pages. Remove unused extensions and avoid loading scripts site-wide when they are only needed on specific pages. Where appropriate, minify CSS and JavaScript, defer non-essential scripts and reduce unused code. Test each change carefully: aggressive bundling or merging can sometimes cause problems with themes and extensions.

Third-party tools also need attention. Analytics, reviews, chat widgets, advertising tags and recommendation services can all add network requests or slow down interaction. Keep only the tools the business needs, and load non-essential services in a way that does not block the main content.

Review extensions and theme customisations

Extensions can add useful functionality, but each one may introduce database queries, scripts, styles or background processes. Review installed modules regularly and remove those that are no longer used.

When a performance issue appears, test whether it is related to a particular extension or customisation. A staging environment can help isolate the cause without disrupting the live shop. Keep Magento, themes and extensions up to date, but test updates before deployment because compatibility issues can affect both performance and functionality.

Improve fonts and external resources

Custom fonts and resources hosted by third parties can delay page rendering. Use only the font weights and character sets required, and consider hosting font files locally where appropriate. Configure font loading to reduce invisible text or sudden changes in typography.

Also review external requests such as embedded videos, maps and social media widgets. These can add substantial overhead. Load them only where needed, or use a lightweight preview that loads the full content after a user interaction.

Keep the database and search services healthy

Slow database queries can affect page generation, particularly on dynamic pages and in the administration area. Monitor database performance and investigate slow queries rather than relying on routine clean-up alone.

For catalogues that use advanced search, check that the configured search service is operating correctly and has suitable resources. Search performance can influence both the speed of results pages and the quality of the shopping experience.

Use a CDN where it makes sense

A content delivery network (CDN) can serve static assets such as images, stylesheets and JavaScript from locations closer to customers. This may reduce transfer times for shoppers who are geographically distant from the origin server.

Configure the CDN to cache the right assets and ensure that updated files are served after a deployment. Dynamic and personalised content needs more careful handling than static files, so review caching rules before applying them broadly.

Test changes safely

Make performance changes in a staging environment where possible. Record a baseline, change one area at a time and compare results. This makes it easier to identify improvements and spot regressions.

After deployment, check the storefront on common devices and browsers. Confirm that navigation, filters, product options, the basket and checkout still work correctly. Page speed improvements should not come at the expense of accessibility, reliability or a functioning purchase journey.

Make optimisation ongoing

Magento page speed optimisation is not a one-off task. New products, extensions, campaign assets and integrations can gradually make a store heavier. Regular monitoring helps identify problems before they have a wider impact.

Start with measurement, address the largest bottlenecks, and prioritise changes that improve the experience on important customer journeys. A well-configured server, effective caching, optimised images and disciplined use of front-end code can provide a strong foundation for a faster Magento store.

 

7 Essential Tips for Optimising Magento Page Speed

1. Enable Magento’s built-in full-page cache, and use Varnish where possible.
2. Optimise and compress images; serve WebP where supported.
3. Use a CDN to deliver static assets closer to shoppers.
4. Remove unused extensions and audit third-party scripts.
5. Keep Magento, PHP and dependencies up to date.
6. Enable production mode and minify CSS and JavaScript.
7. Use fast hosting, Redis for caching, and review database performance.

Enable Magento’s built-in full-page cache, and use Varnish where possible.

Enable Magento’s built-in full-page cache to store ready-to-serve versions of pages, reducing the work required from your server and helping pages load faster for visitors. For production stores, consider using Varnish as the caching application, as it can handle cached requests efficiently and reduce pressure on Magento. Configure caching carefully so that personalised content, such as customer account details and basket information, is never shared between shoppers, and test the setup after changes to ensure pages and updates display correctly.

Optimise and compress images; serve WebP where supported.

Optimising and compressing images is one of the simplest ways to speed up a Magento store, as large product photos and banners can take a long time to download, particularly on mobile connections. Resize images to the dimensions they are displayed at and compress them to reduce file size without noticeably affecting quality. Where supported by your Magento setup and customers’ browsers, serve images in WebP format for further savings, while keeping suitable fallbacks for compatibility. Also consider lazy-loading images below the initial screen, but make sure the main product or hero image loads promptly.

Use a CDN to deliver static assets closer to shoppers.

Using a content delivery network (CDN) can help your Magento store load faster by serving static assets—such as images, CSS and JavaScript—from servers closer to your shoppers. This reduces the distance those files need to travel, which can improve loading times, particularly for customers browsing from far away. Configure your CDN to cache static files appropriately, and make sure updated assets are delivered after site changes.

Remove unused extensions and audit third-party scripts.

Removing unused Magento extensions and auditing third-party scripts can reduce unnecessary code, server requests and processing time, helping pages load and respond more quickly. Review installed extensions regularly and remove those that no longer serve a clear purpose, testing changes in a staging environment first. Also check tools such as analytics, chat widgets, review platforms and advertising tags: keep only what your store needs, and avoid loading scripts on pages where they are not required. This can improve performance without sacrificing essential functionality.

Keep Magento, PHP and dependencies up to date.

Keep Magento, PHP and its dependencies up to date to benefit from performance improvements, security fixes and ongoing compatibility support. Newer supported versions may handle requests and resources more efficiently, while outdated extensions or libraries can introduce slow code or conflicts. Before updating, check compatibility with your theme and extensions, back up the store and test the changes in a staging environment. This helps protect your live shop while ensuring updates improve performance without disrupting essential features.

Enable production mode and minify CSS and JavaScript.

Enable production mode on your live Magento store to avoid the extra processing used for development and debugging. Then minify CSS and JavaScript to remove unnecessary characters and reduce file sizes, helping assets download faster. Apply these changes in a staging environment first, and test key pages and features afterwards to check that your theme and extensions still work as expected.

Use fast hosting, Redis for caching, and review database performance.

Choose fast, reliable hosting with resources suited to your Magento store’s traffic and catalogue. Using Redis for caching can reduce repeated processing and help pages respond more quickly, while regular database performance reviews can reveal slow queries or bottlenecks that affect the whole shopping experience. Monitor these areas together to identify the source of slowdowns and keep your store running smoothly.