How to fix slow page on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Full-page cache: In Admin → System → Cache Management, ensure 'Full Page Cache' is enabled. Switch the FPC engine from the default built-in cache to Varnish (Admin → Stores → Configuration → Advanced → System → Full Page Cache → Caching Application → Varnish Cache) for dramatically faster response times.
2. JS/CSS merging and minification: Go to Admin → Stores → Configuration → Advanced → Developer → JavaScript Settings and CSS Settings. Enable 'Merge JavaScript Files', 'Minify JavaScript Files', 'Merge CSS Files', and 'Minify CSS Files'. (Disable on staging first to check for conflicts.)
3. Images: Install the 'TinyPNG' or 'WebP Images' extension from the Adobe Commerce Marketplace, or use a server-side tool (ImageMagick) to bulk-compress and convert product images. Ensure Catalog → Configuration → Product Image → Lazy Load is enabled.
4. CDN: In Admin → Stores → Configuration → General → Web → Base URLs (Secure), configure a CDN base URL if using Fastly (included with Adobe Commerce Cloud) or a third-party CDN. For on-premise, install the Fastly extension or configure Cloudflare at the DNS level.
5. Extensions: In Admin → System → Web Setup Wizard → Extension Manager (or Composer), audit installed modules. Disable unused third-party modules via bin/magento module:disable Vendor_Module to reduce boot overhead.
6. Hosting: For on-premise/self-hosted Magento, enable PHP OPcache and Redis object/session caching via php.ini and app/etc/env.php respectively. Upgrade to PHP 8.x. For Adobe Commerce Cloud, open a support ticket to review Fastly and New Relic performance data.

What is slow page?

Page load time is how long it takes for a visitor's browser to fully display your store page. When that time exceeds 3 seconds — a threshold like 9 seconds represents a critical failure — shoppers see a blank or partially loaded screen before they can browse or buy. Search engines measure this speed directly and use it as part of their ranking signals. Slow pages hurt you in two ways at once: fewer people find you, and fewer of those who do actually stay long enough to purchase.

Google officially uses page experience signals, including Core Web Vitals (which are speed-based metrics), as a ranking factor — a slow store can rank lower than a competitor with similar content simply because their pages load faster. Studies consistently show that conversion rates drop roughly 4–5% for every additional second of load time, meaning a page taking 9 seconds could be losing the majority of potential buyers before they ever see your products. Mobile shoppers — who now make up the majority of ecommerce traffic — are hit hardest, since they often have slower connections. Beyond revenue, extremely slow pages can also trigger Google to crawl your site less frequently, limiting how quickly new products and content get indexed.

See the complete Slow page guide for every platform and the full background.