How to Fix Slow Admin Panel in WordPress and Magento

Updated 2 days ago by Adam Thacker

A slow admin panel can disrupt workflow and hinder site management. Here's a comprehensive guide on common causes and optimization tips for WordPress and Magento admin panel performance issues.

Common Causes of Slow Admin Panels

1. Excessive Plugins or Extensions
   Running too many or poorly optimized plugins (WordPress) or extensions (Magento) can slow down the backend significantly.
2. Inefficient Database
   A bloated or unoptimized database can increase response times, especially when handling large datasets.
3. Low Server Resources (CPU/RAM)
   Insufficient CPU or memory resources can severely affect admin panel performance, especially during high-traffic periods or bulk operations.
4. Outdated PHP Version
   Running on an older PHP version can degrade performance, as newer versions bring significant speed improvements.
5. Admin Panel Caching Disabled or Misconfigured
   Lack of proper backend caching leads to redundant queries and page loads, increasing load times.
6. High Traffic on the Frontend
   High server resource consumption by frontend visitors can slow down the admin panel.
7. Cron Jobs
   Overlapping or inefficient cron jobs can hog resources, causing the admin panel to slow down.

Optimization Tips

1. Disable or Remove Unnecessary Plugins/Extensions

• WordPress: Deactivate and remove any plugins you no longer use. Prioritize quality over quantity, as fewer plugins mean less resource consumption.
• Magento: extensions are disabled from the command line, not the admin - bin/magento module:disable Vendor_Module, followed by bin/magento setup:upgrade and bin/magento setup:di:compile. (The old Stores > Configuration > Advanced screen was removed in Magento 2.2, and it only ever hid a module's output rather than disabling it.)

2. Optimize the Database

• WordPress: Use plugins like WP-Optimize or Advanced Database Cleaner to clean up post revisions, transient options, and unused data.
• Magento: reindex with bin/magento indexer:reindex, and check your cron history is being pruned - that is a setting under Stores > Settings > Configuration > Advanced > System > Cron, not a cron job you write yourself.

3. Increase PHP Memory Limit

• Adjust the memory_limit value in your hosting’s PHP settings. 256M is a sensible figure for WordPress. Magento needs considerably more - Adobe documents at least 1G for compiling code or deploying static assets, which is exactly when stores run out of memory. see our guide to changing your PHP version and settings

4. Update PHP to a Higher Version

• Use PHP 8.3 or newer. Newer versions are significantly faster, and older ones stop being an option: PHP 7.4, 8.0 and 8.1 have all reached end of life and no longer receive security fixes. WordPress asks for 8.3 or greater, and current Magento releases will not run on 7.4 or 8.0 at all. see our guide to changing your PHP version and settings

5. Enable Admin Panel Caching

• WordPress: LiteSpeed Cache can cache the admin area, which is what helps here. Note that its object cache is a front-end for Redis or Memcached rather than a cache in itself, so one of those has to be available on your plan. Do not pick Memcached - we do not run Memcached servers, so although the PHP extension appears in the selector there is nothing behind it. Redis is available on our Business PCI-DSS packages: Emerald, Sapphire, Diamond and Tanzanite. See Support for memcached and redis. The same plugin also has a database optimiser under Toolbox.
• Magento: Ensure that all cache types are enabled under System > Tools > Cache Management.

6. Use a Content Delivery Network (CDN)

Offloading static assets (CSS, JS, images) to a CDN reduces server load, improving both frontend and backend performance.

7. Optimize Cron Jobs

• WordPress: Offload WP cron jobs to a server-side cron by adding define('DISABLE_WP_CRON', true); to your wp-config.php and setting up a proper cron in cPanel. see our guide to moving the WordPress cron job into cPanel
• Magento: Magento expects its cron to be called every minute - that is by design, and is not something to throttle. What is worth checking is that jobs are not overlapping or piling up, under Stores > Settings > Configuration > Advanced > System > Cron.

8. Limit Admin Panel Resource Usage

• WordPress: reduce the frequency of the admin-ajax "heartbeat" requests that run while you have the admin open. LiteSpeed Cache has this built in, which saves installing another plugin for it.
• Magento: LiteMage caching can help, though it depends on the LiteSpeed licence on your server - ask us whether it is available on your plan. Also try to keep heavy admin grid use away from your busiest hours.

9. Reduce Concurrent Backend Users

Too many users logged into the admin simultaneously can slow it down. Consider limiting access during high-demand times.

10. Monitor Real-Time Resource Usage

Use monitoring tools to check if the admin panel slowdown is linked to server resource spikes. WordPress users can use Query Monitor to identify slow queries and performance bottlenecks.

How did we do?