Help for owners
My Magento store is slow and customers are leaving
Short answer
Adobe lists the usual Magento slowdowns itself: caches not switched on, indexers set to update on save instead of on a schedule, cron jobs not running, large grids and customer segments, and checkout work done in the foreground. Check these with your host or developer, in this order, before paying for bigger servers.
Does this sound like your situation?
- Category and product pages take several seconds to open.
- The admin panel is slow, especially product and order lists.
- Checkout hangs or times out when many people order.
- Changes I make in the admin show on the store late or not at all.
- Our host says the server is fine, but customers still complain.
Why does this happen?
Caching is not fully on
Adobe says to turn on all caches under System, Tools, Cache Management before launching to production and recommends Varnish as the page cache. A store with caches off rebuilds every page on every visit.
Confirmed by experienceleague.adobe.com
Indexers update during every save
Adobe recommends Update on Schedule instead of Update on Save, because scheduled indexing runs in portions through a cron job. Update on Save can slow the store under heavy load.
Confirmed by experienceleague.adobe.com
Cron is not running correctly
Adobe says all asynchronous operations depend on Linux cron. If it stops, scheduled indexing, emails and queues pile up and the store gets slower without any error screen.
Confirmed by experienceleague.adobe.com
Heavy work happens during checkout
Adobe describes moving sales emails and order indexing to the background, and says large admin grids and many customer segments can slow logins and cart actions. These are settings, not rebuilds.
Confirmed by experienceleague.adobe.com
The server and database are not the right size
Adobe lists tested combinations of software, and slow queries from extensions or large catalogues can overload even a good server. Buying more power without finding the cause often only delays the problem.
Confirmed by experienceleague.adobe.com
What can I do about it today?
- Note which pages are slowWrite down three slow pages and when it is worst, such as during a campaign or at month end.
- Do not change settings yourselfSwitching indexers or caches on a live store can empty caches and slow it further. Ask whoever hosts it to check them.
- Ask your host four questions in writingAre all caches on, is a page cache like Varnish running, is cron running, and are indexers set to update on schedule?
- Ask what changed recentlyA new extension, a bigger catalogue or a new PHP version often starts the slowdown.
- Plan work outside your busiest hoursAny fix should happen with a backup and at a quiet time.
When should I bring someone in?
- The answers from your host are unclear, or nobody can say who is responsible for cron and indexing.
- Checkout is slow or failing during sales.
- The slowdown started after an extension or an upgrade.
How do I handle it?
- Measure one page at a timeI time key pages and find whether the delay is in the server, the database, the browser or an extension.
- Check the documented settings firstCaches, indexer modes, cron and background email are compared with Adobe's own guidance.
- Find the slow queriesWhere the settings are right, I look at the slowest database queries and which extension or custom code causes them.
- Change one thing with a backupEvery change is made on a copy first when possible, with a tested way back.
- Report in plain wordsYou get what was slow, what changed and what is still open.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will a bigger server fix it?
Sometimes, but Adobe's own guidance points first to caching, indexing mode and cron. If those are wrong, extra hardware only hides the problem.
Is it safe to switch indexers to scheduled?
Adobe recommends it for production, with the customer grid index staying on Update on Save. It needs cron working, so it should be done by someone who can check that.
Why is the admin slow too?
Adobe describes large product grids and asynchronous grid indexing as causes and gives settings for them. It depends on catalogue size.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.