Start by measuring performance

Before changing your store, establish how it performs now. Test important page types separately, including the homepage, category pages, product pages, search results and checkout. A shop may load quickly on the homepage but struggle on pages with large product images, complex filters or third-party scripts.

Tools such as Google PageSpeed Insights, Lighthouse and WebPageTest can highlight slow-loading resources and user experience issues. For real-world monitoring, review field data and analytics as well as laboratory test results. Test on mobile and desktop, and repeat tests under consistent conditions.

Pay particular attention to the Core Web Vitals:

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

These metrics help reveal different kinds of problems. A large hero image may affect LCP, excessive JavaScript may affect INP, and images without reserved dimensions can contribute to CLS.

Check the hosting environment

Magento 2 is a feature-rich platform, so its performance depends partly on the resources and software available to it. Check that your hosting environment meets the requirements for your specific Magento release and is configured for production use.

• Use a supported PHP version and keep Magento, PHP and extensions patched.
• Configure PHP-FPM and OPcache appropriately for the server workload.
• Provide enough CPU, memory and storage performance for your catalogue and traffic.
• Monitor database performance, slow queries and resource usage during busy periods.
• Use a suitable web server configuration and keep background jobs and cron tasks running reliably.

Upgrading server capacity can help, but it will not fix every issue. Slow extensions, uncached pages or oversized images can remain a problem even on powerful hardware.

Make effective use of caching

Caching is one of the most important parts of Magento 2 page speed optimisation. Magento includes built-in caching and full-page cache functionality. Make sure the relevant caches are enabled in production and avoid routinely clearing them without a specific reason, as this can force the store to rebuild cached content.

For production sites, Varnish can serve cached pages efficiently when it is correctly configured with Magento. Test pages that vary by customer, currency, location or other settings carefully: personalisation and cache variation need to be handled correctly so shoppers see the right content.

Redis is commonly used for Magento cache and session storage. It can reduce pressure on the database and improve response times, provided it is configured and monitored appropriately. Review cache hit rates and server metrics rather than assuming that installing a caching service is enough.

Optimise images and other media

Large images are a frequent cause of slow pages, particularly on mobile connections. Resize product images to the dimensions they are displayed at and compress them without making them look visibly poor. Use responsive image delivery so smaller screens do not download unnecessarily large files.

Modern formats such as WebP or AVIF can reduce file sizes, but check browser support and your Magento theme, extensions and image delivery setup before adopting them. Lazy-load images that are below the initial viewport, while ensuring that prominent content—especially the main product image or hero image—does not load too late.

Specify image width and height where possible. This helps the browser reserve space while images load and can reduce layout shifts.

Reduce unnecessary JavaScript and CSS

Magento themes and extensions can add scripts and styles across the storefront, even on pages where they are not needed. Audit third-party tags, chat tools, tracking scripts, sliders and other features. Remove unused code and load non-essential resources only when appropriate.

Minification and bundling may help in some setups, but they are not guaranteed improvements. Test the effect of each setting on a staging site, as bundling or combining files can sometimes make loading less efficient or cause compatibility problems. Defer or delay scripts carefully: moving essential code can break menus, product options, consent tools or checkout features.

Consider reducing render-blocking resources and delivering critical styles efficiently. After any change to JavaScript or CSS, test key customer journeys on different browsers and devices.

Review your theme and extensions

A heavily customised theme or a large collection of extensions can increase page weight and server processing time. Review each extension’s purpose, maintenance status and impact on performance. Remove features that are no longer used and check whether multiple extensions perform similar tasks.

When choosing a theme, look beyond its appearance. Check how it handles responsive layouts, scripts, images and accessibility, and test it with your actual catalogue and extensions. Custom development should follow Magento’s recommended practices and be reviewed after upgrades.

Keep catalogue and database operations in good order

Large catalogues, complex product attributes and inefficient custom queries can affect response times. Keep Magento indexers configured appropriately for your workflow, and ensure cron jobs run regularly. Scheduled indexing is often suitable for production stores, but the right approach depends on how frequently catalogue data changes.

Use Magento’s supported search engine for your release and monitor its health. Search infrastructure mainly affects search functionality, but a misconfigured or overloaded service can still lead to a poor customer experience. Database maintenance should be planned and tested; avoid deleting data or changing tables without understanding the consequences.

Use a CDN where it makes sense

A content delivery network (CDN) can serve static files such as images, CSS and JavaScript from locations closer to shoppers. This is especially useful for stores serving customers across the UK or internationally. Configure cache rules carefully, and make sure dynamic or customer-specific content is not accidentally cached as public content.

A CDN works alongside Magento’s caching and server setup. It is not a substitute for fixing slow application code or poorly optimised pages.

Test changes safely

Performance changes can affect functionality, so apply them in a staging environment first. Compare test results before and after each significant change, and check the complete shopping journey—from browsing and adding products to the basket through to checkout.

After deployment, monitor error logs, server resources, conversion data and real-user performance. Keep a record of changes so that unexpected regressions can be traced and reversed quickly.

A steady approach to a faster Magento 2 shop

The most reliable Magento 2 page speed improvements come from prioritising issues that affect real shoppers. Start with measurement, then address the largest bottlenecks: server response, caching, oversized media, unnecessary scripts and inefficient extensions. Make one change at a time, verify the results and keep the store’s functionality and security in view.

Page speed optimisation is an ongoing process. Regular monitoring helps your Magento 2 shop stay responsive as its catalogue, traffic and technology evolve.