Magento

Magento Speed Optimization: Why Your Store Is Slow and How to Fix It

Maria

10 min read

A slow Magento store costs sales long before anyone measures it: shoppers leave category pages, ad clicks bounce, and the team stops trusting the admin. This guide explains why a Magento 2 store gets slow, what to fix first to speed it up, how to speed up the admin, what you can check yourself, and what a Magento performance audit covers when the cause isn't obvious.

Signs your Magento store is too slow

  • Pages load slowly, especially on mobile, or Google PageSpeed scores keep dropping.
  • The store slows down at certain times: when search engines crawl it, during ad campaigns, or while products are imported and reindexed.
  • Product, price or stock updates appear on the site late.
  • Saving a product or opening an order grid in the admin takes long enough to make coffee.
  • Your SEO team keeps asking for better Core Web Vitals.
  • Almost every change brings new bugs, and nobody knows why.
  • You've already paid for "optimization", and nothing changed.

Why Magento is slow: the most common causes

monitoring-dashboard.webp

Front-end

Heavy themes load a lot of JavaScript and CSS on every page. Images are too large or not lazy-loaded. Third-party scripts such as chat widgets, pop-ups and tracking pixels block rendering. The default Luma theme is a frequent source of these problems, because it ships large JavaScript bundles that every page has to download and run.

Code and extensions

Extensions that run on every page, observers and plugins that do too much, and custom code that repeats the same database queries. Many stores also carry extensions nobody uses anymore, still loading on every request.

Caching

Full-page cache not enabled or constantly cleared, no Varnish in front of Magento, Redis not used for cache and sessions, PHP OPcache misconfigured. Fixing caching is often the quickest win.

Database

Slow and repeated SQL queries, missing indexes, tables that grew for years (logs, quotes, old sessions), and indexers set to run on save during busy hours.

Server and load

Not enough CPU or memory for the traffic, PHP and MySQL settings left at defaults, and one server handling everything at once. In Magento, shoppers, search bots, ad traffic, site search and reindexing all share the same server and database, so a crawl or a campaign can slow down checkout.

Bots and crawlers

A large part of the traffic on many stores isn't human: search engines, SEO tools, price scrapers and bots looking for vulnerabilities. They open thousands of filter combinations and search pages that the cache can't hold. When we watch stores through Cloudflare and the server logs, unexpected crawlers are one of the first things we look for, because blocking or rate-limiting them costs nothing and frees the server for real shoppers.

How to measure Magento speed before you change anything

Without a baseline, every fix becomes a matter of opinion. Before you touch the store:

  • Pick the pages. The homepage, two or three busy category pages, a product page, search results and the cart. Test the same URLs every time.
  • Use field data and lab data. Google PageSpeed Insights shows real-user Core Web Vitals (field data) when your store has enough traffic, and a lab test you can repeat on demand. Track both, on mobile first.
  • Measure the server separately. Time to first byte shows how fast Magento answers before the browser does anything. A fast front-end can't hide a slow server.
  • Note the conditions. Was the cache warm? Was a reindex or import running? Was it a sale day? Write it down next to the numbers.
  • Repeat after each change. One change at a time, the same pages, the same conditions. That's how you learn which fix actually worked.

How to speed up Magento 2: what to fix first

Work from the cheapest, safest fixes towards the expensive ones. Measure the same pages before and after each step, so you know what actually helped.

1. Production mode and caching

Run the store in production mode. Enable full-page cache and put Varnish in front of Magento. Use Redis for the cache and for sessions, and give PHP OPcache enough memory. Check that nothing flushes the whole cache every few minutes: imports and extensions often do.

2. Indexers and cron

Set indexers to "Update by schedule" and make sure cron runs and finishes. Indexers that run on save rebuild data while shoppers are browsing, and a stuck cron leaves prices and stock out of date.

3. Images

Serve images in WebP, at the size they're shown, and lazy-load everything below the first screen. Product images uploaded straight from a camera are a common reason for heavy category pages.

4. Third-party scripts

List every script that loads on the storefront: chat, reviews, pop-ups, analytics, ad pixels. Remove what nobody uses, and load the rest after the page renders. These scripts weigh the same on any theme, so no front-end rebuild fixes them.

5. Extensions

Disable and remove extensions you don't use. For the ones you keep, check which run on every page and what they do there. One badly written observer can slow down every request.

6. Database

Clean up tables that grow forever, such as logs, old quotes and sessions. Find the slow and repeated queries with a profiler, then fix the code that sends them or add the missing indexes.

7. Server and hosting

Run a PHP version that your Magento release supports, tune PHP-FPM and MySQL for your traffic instead of defaults, and size the server for your peaks, not your average day. Separate the database or search from the web server once the store outgrows one machine.

8. CDN and bot control

Put a CDN such as Cloudflare in front of the store for static files, and use it to block bad bots and rate-limit aggressive crawlers. Check the server logs regularly: they show which bots hit the store and which URLs they're probing.

9. The front-end itself

If the store is stable but the theme is heavy, a lighter front-end helps most. Hyvä, which has been free since November 2025, replaces Luma's heavy JavaScript. If the store slows down or goes down under traffic, a headless storefront also takes bots, ads and search off Magento.

Magento speed optimization checklist

  • [ ] Production mode on
  • [ ] Full-page cache on, with Varnish in front
  • [ ] Redis for cache and sessions, OPcache with enough memory
  • [ ] Nothing flushes the whole cache every few minutes
  • [ ] Indexers on "Update by schedule", cron running and finishing
  • [ ] Images in WebP, sized to their slot, lazy-loaded below the first screen
  • [ ] Third-party scripts reviewed and deferred
  • [ ] Unused extensions removed
  • [ ] Old logs, quotes and sessions cleaned up
  • [ ] Slow SQL queries found with a profiler
  • [ ] PHP version supported by your Magento release, PHP-FPM and MySQL tuned
  • [ ] CDN in front of the store, bad bots blocked, crawlers rate-limited
  • [ ] Baseline measured, and the same pages measured after every change

How to speed up the Magento admin

A slow admin wastes your team's time every day. The usual causes:

  • Large grids. Product and order grids load thousands of rows with extra columns that extensions add. Reduce the columns and the default page size.
  • Indexers on save. Saving one product triggers a reindex. Switch indexers to "Update by schedule".
  • Extensions in the admin. Some extensions run heavy checks on every admin page. Profile an admin page the same way you profile the storefront.
  • One server for everything. Imports, cron jobs and the admin compete with shoppers for the same resources. Schedule heavy jobs outside busy hours.

What you can check yourself

  • Run Google PageSpeed Insights on your homepage, a category page and a product page, on mobile. Look at the field data for real users, not only the lab score.
  • Check that full-page cache is enabled in System > Cache Management, and that it isn't cleared every few minutes.
  • Check that the store runs in production mode.
  • Look at Index Management: are indexers on "Update by schedule", and do they finish?
  • List your extensions and remove the ones you don't use.
  • If you use Cloudflare, check Security > Bots and the traffic analytics: how much of your traffic is automated?

These checks find the obvious problems. The causes in code, database and server load need profiling.

Performance audit, code audit or technical audit?

The names overlap, so it helps to know what you're buying:

  • Performance audit answers "why is it slow": front-end speed, server response, database queries and behavior under load.
  • Code audit answers "is the code sound": custom modules and extensions checked for bugs, vulnerabilities, outdated patterns and code that will break on the next upgrade.
  • Technical audit is the widest: hosting, Magento version and patches, extensions, integrations, security and performance together.

A useful audit for a slow store combines the first two, because slow code is usually the reason for slow pages. That's how we structure ours.

If pages load fine but shoppers still don't buy, the question is usability rather than speed. That's a different check: see what a Magento UX audit covers.

What a Magento performance audit checks

A complete audit looks at four areas:

  1. Front-end speed: First Contentful Paint, Speed Index, Time to Interactive and input delay, on mobile and desktop.
  2. Code quality: a scan of custom code and extensions for bugs, vulnerabilities and code smells, for example with SonarQube.
  3. Server-side performance: page profiling for response time, memory, CPU and I/O, and how the store behaves under load.
  4. Database and SQL: slow and repeated queries, and what to optimize first.

A safe audit doesn't touch the live store. The store is deployed locally from the code repository and a database copy, so profiling and load tests never affect real customers.

What a good audit report contains

  • Summary: key metrics, main findings and the top priorities.
  • Scope and method: what was checked, with which tools, in which environment.
  • Findings by area: front-end, code, server and database.
  • Recommendations, split into quick wins, short-term fixes and planned work.

Typical recommendations include Varnish full-page cache, Redis, OPcache, lazy loading, an extension review and SQL optimization. See a sample audit report (PDF).

Do speed optimization extensions work?

Some help with narrow tasks: image compression, lazy loading, minifying CSS and JavaScript. None of them fix slow database queries, a misconfigured server or an extension that does too much on every page. Some even add their own load. Install one only when you know which problem it solves, and measure the same pages before and after.

When fixes aren't enough

If an audit shows the store is fine until traffic peaks, the problem is architecture, not a single bug. A lighter theme such as Hyvä speeds up the front-end; a headless storefront also takes the load of bots, ads and search off Magento.

dashboard.webp

Questions about Magento speed and performance

Why is my Magento store so slow?

Most often it's a mix of caching that isn't set up or keeps getting cleared, heavy front-end code, extensions that run on every page, and a server shared by shoppers, bots and background jobs. A profiler shows which of these matters most on your store.

How long does a Magento performance audit take?

Usually a few days. Ours takes up to three days: access and local setup on day one, profiling and scans, and the report on day three.

Do you need access to the live server?

No. A code repository and a database copy are enough, so the audit never touches the live store.

Does the audit include load testing?

It should include how the store behaves under load. Full load testing of a live store is a separate task, because it needs a copy of the production environment.

Does an audit fix the problems?

No. An audit finds and prioritizes them. Fixing is a separate step, which your team, your agency or we can do.

How much does Magento speed optimization cost?

It depends on what the audit finds. Caching and configuration fixes take days; rewriting slow extensions or rebuilding the front-end takes longer. Our audit costs $560, and ongoing support, including performance work, starts at $800 a month.

Want to know what slows your store down? Our Magento performance audit takes up to three days and costs $560, with a prioritized plan of what to fix first. SYSINT has worked with Magento since 2014.

Are we a good fit? Let's discuss.

Tell us about your store and what you want to get done. If we're a fit, you get a clear next step. If not, we'll tell you.

  • Reply within one business day
  • Fixed estimate before we start
  • No commitment