Magento Performance Audit: What Slows Your Store and How to Fix It

A Magento performance audit finds out why a store is slow: is it the front-end, the code and extensions, the server or the database? It ends with a prioritised list of what to fix first. This guide covers the most common causes of a slow Magento 2 store, what a proper audit checks, what you can check yourself, and what a good audit report contains.

Signs your Magento store needs an audit

• 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.
• 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 "optimisation", and nothing changed.

The most common causes of a slow Magento store

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.

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.

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.

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 optimise 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 you can check yourself

• Run Google PageSpeed Insights on your homepage, a category page and a product page, on mobile.
• 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.

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

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 optimisation. See a sample audit report (PDF).

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.

Questions about Magento performance audits

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 prioritises them. Fixing is a separate step, which your team, your agency or we can do.

Want this for your store? Our Magento performance audit takes up to three days and costs $560, with a prioritised plan of what to fix first. SYSINT has worked with Magento since 2012.