Few things are more frustrating than discussing prospective changes to a product but being inhibited by the grid taking its time to load. Spinning loading indicators can even introduce thoughts of questioning our life choices.
Admin grids are notorious because of their potentially intensive interaction with the database. Adobe Commerce’s default grids Because Magento is so customizable, every grid can be modified with custom database queries that can tank performance. This is the first thing we troubleshoot when looking into a problem like this.
First, it is critical to determine which grids are slow. If it’s just the product grid, then troubleshooting can be localized here.
But, what if every page is slow? This could indicate a more systemic problem.
A while back, we were dealing with a similar case. After doing some analysis, we discovered that a module sent a synchronous request that keeps the rest of the code from executing every time a page is loaded. The purpose of this request was to ensure the module was licensed correctly. This type of verification only occurs in an open-source environment. We removed this code.
In a similar vein as the previous issue, but quite different, technically speaking, is when the save operation takes forever. You may encounter a CloudFlare timeout page, causing even more concern (the good news is that this operation is still likely to be successful).
This is almost guaranteed to be a backend coding problem.
Adobe Commerce has an excellent system for coordinating background tasks. Unfortunately, there is little visibility into whether or not the tasks are running or have failed. You, as a merchant, simply see that the task never completes.
The primary bulk operations are data exports and mass product operations (attribute changes and inventory updates).
