17 Ways To Fix A Slow WordPress Admin (Dashboard) Caused By Plugins/Settings, Hosting Environment, Overloaded Server

Slow wordpress admin

By the end of this tutorial, your WordPress admin will be faster than ever (if it’s not, leave me a comment with your current setup so I can help).

No time to read? Here’s a summary:

The first step to fixing a slow admin is learning if it’s caused by a single plugin, plugin setting, overloaded server, or underpowered server. It’s usually one of those in the majority of cases.

Query Monitor, WP Hosting Benchmark, and WP Healthcheck are great plugins for diagnosing slow admins. Between the three, you can find slow plugins calling admin-ajax, CPU/memory utilization, database performance, and environment info (PHP, MySQL, and WordPress version). WP-Optimize shows which plugins add the most overhead and lets you remove unused tables.

Next, deactivate plugins 1 by 1 and check their settings. For example, most cache plugins do preloading + automatic cache clearing which WP Rocket and LiteSpeed Cache list as common reasons for high CPU usage in their documentation. Disable them and use cron jobs to schedule these at night. While you’re at it, disable (or limit) everything you don’t use: Heartbeat, widgets, transients, and especially background tasks that collect data like statistics and security plugins.

Finally, cache everything possible. From cache plugins to object cache + OPcache (in your hosting account) as well as CDNs with full page caching. CDNs (and Cloudflare Enterprise) can speed up the admin by offloading bandwidth and blocking unwanted requests. I’m referring to WAF, bot fight mode, hotlink protection, crawler hints, and other features to reduce server load.

But I’ll guess 8/10 times, it’s because you’re on shared hosting with low CPU limits and overcrowded servers. Most hosts use Apache/NGINX when LiteSpeed is faster, while others skimp on CPU/RAM and don’t use faster NVMe SSDs. Check the specs of your current hosting plan and compare them to something like Rocket.net’s specs who I bet will outperform them with 32 cores + 128GB RAM + NVMe + Redis + Cloudflare Enterprise, and no PHP worker limits.


1. Remove High CPU Plugins

Plugins are notorious for slowing down the WordPress admin. You can always deactivate plugins 1 by 1 while testing admin speed. Otherwise, there are several tools that can help pinpoint which plugins increase memory usage or make excessive calls to admin-ajax.php.

Query Monitor – once installed, view any page on your site, then go to “Queries” in the top menu. Use the “Queries by component” tab to see your slowest plugins. You can also find plugins calling ajax.php in your GTmetrix Waterfall chart by looking for POST admin-ajax.php. Be sure to delete Query Monitor you’re done since it scans your site and consumes resources.

Slow wordpress plugins query monitor

A few other things to check:

  • Database: database stats, how large it is, etc (see step #10).
  • Queries: if something generates 100+ queries, remove or replace it.
  • Errors: take note of errors you see in your report and diagnose the issue.
  • Object cache: whether you have a persistent object cache plugin (see step #3).
  • Environment: PHP version, memory limit, and stats about your server, PHP, and WordPress environment. These play a large role in how fast your WordPress admin is.

WP Hive – free Chrome Extension that lets you browse the WordPress plugin repo and see whether a plugin impacts memory usage. This way, you can avoid it before even installing it.

Wp hive high memory usage plugins

75+ Slow Plugins – list of common plugins that either increase memory usage or impact PageSpeed Insights scores. This was made with the help of WP Hive, but I also tested many of them individually since they don’t always impact PSI scores until you add them to the frontend.

Lightweight alternatives:

  • Social Sharing – Grow Social.
  • Comments – native comments/CSS.
  • Translate – MultilingualPress, Polylang (not WPML).
  • Backups – UpdraftPlus or ManageWP (schedule for non-peak hours).
  • SEO – Rank Math or SEOPress (make sure you disable unused modules).
  • Analytics – Google Analytics + Search Console (avoid stat plugins if possible).
  • Theme + Page Builder – Elementor/Divi’s editor aren’t great for admin speed.
  • Security – use a firewall and go through a security checklist instead. Like stat plugins, security plugins are also known for constantly running scans and increasing CPU usage.


2. Get Hosting With Better Specs

Hosting affects both the frontend and admin panel.

Slow wordpress admin hosting

Mainstream hosts (like SiteGround, Hostinger, GoDaddy, and WPX) don’t live up to the hype. They skimp out on CPU/RAM, use slower SATA SSDs, and are shared hosting with strict CPU limits which force you to upgrade. Cloud hosting is faster, but Kinsta and WP Engine still use SATA SSDs with low limits on PHP workers and monthly visits which get expensive. Instead of focusing on speed/technology, they do aggressive marketing… don’t fall for mainstream hosts.

For cloud hosting, I recommend Rocket.net (what I use) or Cloudways Vultr HF (what I previously used). Both use Cloudflare Enterprise which makes a major improvement to TTFB between full page caching, HTTP/3, image optimization, and Argo Smart Routing. Both also use NVMe, Redis, and have monthly pricing. However, Rocket.net is definitely faster since you get a lot more resources (32 CPU + 128GB RAM), LiteSpeed’s PHP (faster than Cloudways’ PHP-FPM), and Brotli. There are also no PHP worker limits due to Rocket.net’s free/automatic Cloudflare Enterprise which handles roughly 90% of traffic, resulting in less requests to your origin server. Finally, Rocket.net is easier between their dashboard and A+ support which is even better than Kinsta’s. Cloudways has more bandwidth/storage, but the technology isn’t as fast. One of these cloud hosts + Cloudflare Enterprise + FlyingPress (cache plugin) is the combination I would use.

WP Engine SiteGround Kinsta Cloudways Vultr High Frequency Rocket.net
Hosting type Cloud Cloud Cloud Cloud Private cloud
CPU cores Not listed 4 12 1 32
RAM (GB) Not listed 8 8 1 128
Storage (GB) 10 40 10 32 10
Object cache Redis Memcached Redis ($100/mo) Redis (Pro) Redis
Server Apache + Nginx Apache + Nginx Nginx Apache + Nginx Apache + Nginx
PHP processing Not listed FastCGI FastCGI PHP-FPM LiteSpeed
Bandwidth or monthly visits 25,000/mo 5TB 25,000/mo 1TB 50GB + 250,000/mo
CDN Cloudflare SiteGround CDN Cloudflare Enterprise Cloudflare Enterprise ($5/mo) Cloudflare Enterprise
CDN PoPs 270 14 270 270 270
Full page caching x Coming soon
Compression Brotli Brotli Brotli GZIP Brotli
Argo smart routing x x x
Load balancing x x x
Image optimization x Limited x
CPU limits Low PHP workers Very common Low PHP workers Average None
Email hosting Limited x x x
TrustPilot rating 4.4/5 4.6/5 4.3/5 4.6/5 4.9/5
Monthly price $25 $100 $30 $13 + $5 for CF Enterprise $25
Plans Don’t use Don’t use Don’t use View plans View plans
Omm ttfb speedvitals 1
Sites hosted on Rocket.net average a 100ms global TTFB (search their TrustPilot reviews)
Keycdn global ttfb
You can also test TTFB in KeyCDN or click through my site to see how fast it loads

Rocket. Net trustpilot reviewKinsta to rocket. Net migrationMoved to rocket. Net vs sitegroundRocket. Net positive review

Rocket. Net vs cloudways vultr hf trustpilot reviewRocket. Net facebook review 1Rocket. Net vs kinstaKinsta to rocket. Net ttfb redis

Rocket. Net woocommerce elementor
Try Rocket.net for $1, request a free migration, then retest your TTFB (or reach out to Ben Gabler)

Why Rocket.net’s Cloudflare Enterprise Is Better

Rocket.net’s Cloudflare Enterprise is free, setup automatically, and uses full page caching (unlike Cloudways). And unlike Kinsta’s, Rocket.net has Argo Smart Routing (specifically good for WooCommerce sites), load balancing, and image optimization. Rocket.net CEO Ben Gabler also used to be StackPath’s Chief Product Officer and went as far as building Rocket.net’s data centers in the same locations as Cloudflare’s. And unlike both hosts, Rocket.net doesn’t limit PHP workers (there’s no CPU limits) and monthly visit limits are 10-25 times more than Kinsta’s.

Cloudflare Enterprise (Kinsta) Cloudflare Enterprise (Cloudways) Cloudflare Enterprise (Rocket.net)
CDN PoPs 270 270 270
Prioritized routing
Full page caching x
Argo smart routing x
Load balancing x
Image optimization x
Automatic configuration x x
Price Free $5/mo (1 domain) Free

For shared hosting, I recommend NameHero. They use LiteSpeed servers which means you’ll use LiteSpeed Cache + QUIC.cloud CDN (arguably the fastest setup on a budget). It’s similar to Hostinger/A2 with LiteSpeed and cPanel, but you get more CPU/RAM and support/uptimes are better which is reflected in their TrustPilot reviews. I generally recommend their Turbo Cloud plan for $7.38/month which includes 3 CPU + 3 GB RAM and faster NVMe storage. The main con is their data centers are only in the US/Netherlands. If your visitors aren’t close to there, make sure to setup QUIC.cloud which has HTML caching (ideally the paid plan which uses all 73 PoPs).

SiteGround Hostinger GoDaddy WPX NameHero Turbo Cloud
Hosting type Shared Shared Shared Shared Shared
CPU cores Not listed 1-2 1-2 Not listed 3
RAM (GB) Not listed .768 – 3.072 .512 – 2 Not listed 3
Object cache Memcached x x x Redis
Server Apache + Nginx LiteSpeed Apache LiteSpeed LiteSpeed
CDN SiteGround CDN Cloudflare Enterprise QUIC.cloud QUIC.cloud Cloudflare Enterprise
CDN PoPs 14 73 14 73 73
Full page caching x
Compression Brotli Brotli Brotli GZIP Brotli
HTTP/3 x
Image optimization Limited x x
CPU limits Common Low RAM Common At their discretion Average
Cache plugin SG Optimizer LiteSpeed Cache x LiteSpeed Cache or W3TC LiteSpeed Cache
Email hosting Limited Very limited Limited
Major incidents Google blocked DNS for 4 days Breach affecting 14M customers Breach almost every year Worldwide outage 2 day outage
Free migration $30/site Free Paid Free Free
Price $3-8/mo (1 year) then $15-40/mo $29/mo (yearly) $20.83 (yearly) $20.83 (yearly) $7.38/mo (1-3 years)
Renewals Very high Monthly Monthly Monthly Monthly
TrustPilot rating 4.6/5 4.4/5 4.9/5 4.5/5 4.9/5
Plans Don’t use Don’t use Don’t use Don’t use View plans
Litespeed vs nginx vs apache
LiteSpeed is faster than Nginx/Apache (and more efficient with less chance of CPU spikes)

Litespeed cache litespeed server

Cpu cores on litespeed hosting plans

Namehero vs siteground feedback

Ram on litespeed hosting plans

Problems with mainstream hosts

I’ve written some pretty bad reviews about SiteGround’s slow TTFB, CPU limits, and why SG Optimizer does a poor job with core web vitals (they also control several Facebook Groups and threaten to sue people who write bad reviews). Hostinger writes fake reviews and is only cheap because you get less resources like CPU/RAM. Kinsta and WP Engine are way too expensive for how many resources, PHP workers, and monthly visits you get. Along with major incidents like WPX’s worldwide outage and SiteGround’s DNS getting blocked by Google for 4 days (both WPX and SiteGround denied responsibility). One thing is clear: most mainstream hosts appear to be interested in profits/reputation over performance. Do your own research before getting advice.

12 things to know about hosting/TTFB

  1. Hosting is the #1 factor of site speed.
  2. TTFB is a key indicator of hosting performance.
  3. TTFB is part of core web vitals and is 40% of LCP.
  4. TTFB also affects INP (since latency is part of TTFB).
  5. SpeedVitals tests TTFB in 35 locations – use this tool!
  6. Test your site 3 times to get accurate numbers in SpeedVitals.
  7. Doing this ensures your caching and CDN are working properly.
  8. Check your average TTFB worldwide in your 3rd SpeedVitals test.
  9. Google flags your TTFB if it’s over 600ms, but under 200ms is better.
  10. PageSpeed Insights (and other testing tools) only test TTFB in 1 location.
  11. WP Hosting Benchmark also tests hosting performance (here are my results).
  12. Combining a good host/CDN is arguably the best way to improve TTFB (using a host with improved specs on top of Cloudflare Enterprise hits 2 birds with 1 stone).
Namehero cloudways rocket. Net
NameHero for shared, Cloudways Vultr HF for cloud, but Rocket.net outperforms both


3. Enable Redis Or Memcached

Object cache is specifically good for speeding up the WordPress admin.

I prefer Redis which uses memory more efficiently. Setting up Redis or memcached is different depending on your host and cache plugin, so be sure to go through their documentation. You first need to enable it on the server (most hosts will have a setting for it). Then you’ll need to install a plugin like WP Redis (some cache plugins like LSC + W3TC also let you connect Redis).

  • Rocket.net: install Redis Object Cache
  • cPanel: PHP Selector → Extensions (then enable in your cache plugin)
  • SiteGround: Site Tools → Speed → Caching → memcached (enable in SG Optimizer)
  • Cloudways: Servers → Manage Services → activate Redis add-on (installs drop-in plugin)
Redis memcached cpanel
Step 1: Enable Redis or memcached in your hosting account
Litespeed cache object cache
Step 2: Set method to Redis or memcached in your cache plugin (or use a dedicated Redis plugin)


4. Block Unwanted Requests To Your Server

3 ways to do this are with a firewall, bot protection, and protecting the wp-login page. You’ll use Cloudflare for most of this.

  • Use a firewall – Cloudflare WAF.
  • Firewall rules – block “hacky” countries. XML-RPC, etc.
  • Rate limiting – prevents excessive requests to specific URLs.
  • Bot fight mode – stop bad bots from hitting your server.
  • Block AhrefsBot and SemrushBot – if you don’t use their service.
  • Hotlink protection – stops people from stealing your image bandwidth.

Protect The Admin

wp-login and wp-admin pages are common targets for bots. By moving and protecting these pages, you’re improving security while saving resources by stopping unwanted login attempts.

  • Use Limit Login Attempts Reloaded.
  • Move login page using Perfmatters or another plugin.
  • Use a Cloudflare page rule to set wp-admin security level to high.
  • Use a Cloudflare page rule to only allow access from your country or IP.
  • If using QUIC, don’t move your login since it already protects the wp-admin.
Perfmatters move wordpress login
Bots usually aren’t smart enough to find custom login URLs


5. Offload Bandwidth To CDNs

CDNs speed up the WordPress admin because:

  • You’re offloading bandwidth (less uncached requests to your server).
  • Cloudflare has many settings to reduce CPU usage (see section above).
  • Firewall and other security features block unwanted requests to your server.
Cloudflare bandwidth
Higher cache HIT ratio = less stress on your origin server

Which CDN Should I Use?

You’re not going to beat Cloudflare Enterprise which you can get on Rocket.net (free with full page caching) or Cloudways/Kinsta (without pull page caching and less smoother integration).

I’m also a fan of the Cloudflare + BunnyCDN combo.

Cloudflare has their DNS, APO, firewall, and many features in the dashboard to improve speed/security while reducing CPU usage. BunnyCDN is highly recommended in Facebook Groups and is consistently performant on cdnperf.com. It has features like geo-replication + perma-cache, SafeHop, Bunny Optimizer (image optimization) and improves cache/hit ratio. QUIC.cloud is a solid choice if you’re on a LiteSpeed server and is setup via LiteSpeed Cache. I don’t recommend RocketCDN (StackPath) which isn’t fast and was removed from cdnperf.com.

Cloudflare with bunnycdn
Gijo from WP Speed Matters also recommends Cloudflare + BunnyCDN
Cdnperf. Com cdn performance
cdnperf.com shows the performance/reliability of several CDNs

Cloudflare Setup Instructions:

  • DNS – fast, reliable DNS on dnsperf.com and done by changing nameservers.
  • CDN – head to your Cloudflare DNS settings and change your website from DNS only to Proxied. Required to use APO, Argo, firewall, and most Cloudflare features.
  • TLS 1.3 – fastest TLS protocol (I recommend setting minimum TLS version to 1.2).
  • Bot Fight Mode – block spam bots (these will be logged in your firewall events).
  • Early Hints – early preload/preconnect hints which improves server wait time.
  • Crawler Hints – tells crawlers if content is updated to prevent wasteful crawls.
  • Page Rules – here’s a screenshot of 3 common page rules for WordPress sites.
  • Firewall Rules – another screenshot of 4 common firewall rules for WordPress.
  • Browser Integrity Check – an extra security layer to block unwanted requests.
  • HTTP/3 With QUIC – delivers website in HTTP/3 (confirm with an HTTP/3 test).
  • Hotlink Protection – stops websites from copying images and using bandwidth.
  • Zaraz – offloads third-party scripts to Cloudflare (Google Analytics, Ads, others).
  • APO (Paid) – caches HTML to Clouflare’s edge network by creating an API Token and using the Cloudflare plugin. Improves TTFB worldwide (see my instructions).
  • Argo (Paid) – routes traffic through the fastest network paths to reduce latency.
  • Cache reservebeta feature to improve cache lifespan + improve cache hit ratio.
  • Firewall (Paid) – multiple rulesets and other tools to identify/fix vulnerabilities.
  • Rate Limiting (Paid) – prevents excessive request rates to reduce CPU/attacks.
  • SXGs (Paid) – uses prefetching to load your site faster in Google’s search results.
  • TCP Turbo (Paid) – reduces latency by automatically choosing the TCP settings.

BunnyCDN Setup Instructions:

  • Sign up for BunnyCDN.
  • Create a pull zone and choose your regions/pricing.
  • BunnyCDN will assign a pull zone name + CDN URL.
  • Install BunnyCDN’s plugin and add the pull zone name.
  • Add your CDN URL to your cache plugin’s CDN settings.
  • Force SSL + enable browser WebP support in BunnyCDN settings.
  • Purge cache and make sure assets are being served from BunnyCDN.
  • Consider using Bunny Optimizer + perma-cache for even better results.
  • If you’re using FlyingPress, I recommend FlyingCDN which uses BunnCDN.

Once Cloudflare is set up, wait a few weeks and check your analytics to not only make sure everything is working, but also see your cache hit ratio and what kind of requests get blocked.


6. Remove Admin Bloat

Most of this can be done with Unbloater.

There’s also Disable WooCommerce Bloat and even Perfmatters has several bloat removal options. Make sure you disable XML-RPC if you’re not using it and take some time to go through each setting to remove as much bloat as you can (remember to delete unused themes/plugins).

Unbloater plugin


7. Remove Database Junk

While most cache plugins clean your database, WP-Optimize lets you remove database tables from old plugins you deleted which will be marked as not installed. If you don’t plan on using the plugin again, remove the table. While cache plugins are good for removing most junk, WP-Optimize does a more robust database cleanup, especially if you find yourself deleting plugins.

Wp optimize unused database tables
Remove tables marked as “not installed” left behind by old plugins
Rank math database bloat
Some plugin features/modules cause bloat (disable modules if they’re not important)


8. Cache The WordPress Admin

Some cache plugins like LiteSpeed Cache let you cache the WordPress admin which can speed it up. Just note that this can cause expired data which you may see when working on your site.

Cache wordpress admin litespeed cache


9. Limit Heartbeat, Autosaves, Post Revisions

WordPress Heartbeat slows down the admin since it consumes resources by notifying you when other users are editing a post, real-time plugin notifications, etc. You can disable/limit it in most cache plugins, the Heartbeat Control plugin, or add the code below into your functions.php file.

add_action( 'init', 'stop_heartbeat', 1 );
function stop_heartbeat() {

Some plugins can control Heartbeat in the dashboard, frontend, and post editor. In this case, I recommend disabling it in the dashboard/frontend, then increasing it to 120s in the post editor.

Heartbeat control plugin settings

Similar to Heartbeat, WordPress autosaves every 1 minute and stores a post revision any time you hit the “publish” button. I personally increased the autosave interval to 5 minutes then limited post revisions to 5 (so I’ll still have a few backups, but they don’t cause too much bloat).

Both these can be done in Perfmatters or by adding the code to your wp-config.php file.

define('WP_POST_REVISIONS', 5);
define('AUTOSAVE_INTERVAL', 300); // seconds


10. Don’t Trigger Actions That Clear The Entire Cache

Any time you trigger one of these actions, the entire cache is deleted and needs to be rebuilt. Just like anything that increases CPU usage, this can slow down the admin. The screenshot is shown in WP Rocket’s documentation but is similar with most cache plugins. They do partial cache deletions on specific actions too. If you trigger these too frequently, it stresses the server.

Wp rocket full cache deletion

To avoid this, you can disable automatic cache clearing (WP Rocket has a helper plugin) then create a cron job to control which pages are cleared and when the cache is cleared. You could schedule the cron job to run in the middle of the night when very few people are on your site.

Increasing cache TTL can help since the cache won’t need to be rebuilt as frequently which can also lead to a better cache hit ratio.


11. Control Preloading In Cache Plugins

Preloading in cache plugins can also get out of hand especially if you preload the full sitemap on a shared server. Just like we controlled cache clearing, we can do the same with preloading.

  • Disable preloading and control it with a cron job (recommended).
  • Only preload important sitemap URLs like pages/posts, not the full sitemap.
  • Increase the preload crawl interval (usually something like 500ms – 3000ms).
  • Most cache plugins like WP Rocket and LiteSpeed Cache have documentation.

Wp rocket sitemap preloading

Disable Link Preloading

You may also want to disable link preloading especially if you’re on a shared server or your website has lots of image links. When users hover over internal links, those pages are downloaded in the background so they’re loaded by the time the user clicks them. This is great for perceived load time but it can increase server load especially if users hover over lots of links.

Wp rocket disable link preloading

Reduce Remove Unused CSS Batch Size

The remove unused CSS feature can also increase CPU usage and can be limited by adjusting the batch size. However, I recommend using Perfmatters, FlyingPress, or LiteSpeed Cache for this since WP Rocket loads used CSS inline which is better for “scores” but slower for visitors.


12. Replace WP-Cron With A Real Cron Job

wp-cron is loaded on every pageview and schedules automatic tasks like checking updates, publishing scheduled posts, sending email notifications, and more. Just like you can use cron jobs to schedule preloading and automatic cache clearing, you can do the same with WP cron.

The first step is to disable wp-cron by adding the code to your wp-config.php file.

define('DISABLE_WP_CRON', true);

Now we’ll set up an external cron job (Google instructions for your host). In cPanel, you’ll open the “cron jobs” tab and add this line to set a cron job to run every 10 minutes. It may seem a higher interval would be better, but this can cause CPU spikes since too many jobs run at once.

wget -q -O - https://yourwebsite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

Cron job minutes

External cron job

WP Crontrol is nice for changing the schedule of specific cron jobs and deleting jobs with no action. You could also offload cron jobs from your server using a Cloudflare JavaScript worker.


13. Upgrade PHP Versions

Upgrade to the latest stable PHP version in your hosting account.

Most hosts support PHP 8.0 but you’ll need to make sure themes/plugins are compatible. The easiest way is to upgrade and check your site for visible errors. If you see errors, revert to the earlier version. Or learn which plugin(s) aren’t compatible and replace it if it’s not maintained.

Cloudways settings packages
Keep PHP, MySQL, WordPress, plugins, and other technology updated


14. Increase Memory Limit

256MB is recommended by WordPress/Elementor, but you can set it even higher.

Step 1: Edit wp-config.php file.

Step 2: Add the code before the line that says, “Happy Blogging”.

define('WP_MEMORY_LIMIT', '1024M');
Cloudways memory limit
Some hosts let you increase memory limit in the dashboard


15. Enable OPcache

OPcache improves PHP performance and CPU utilization which can also speed up your WordPress admin. In cPanel, it’s found in PHP Extensions. Or Google instructions for your host.



16. Delete Transients

WooCommerce and social sharing plugins specifically can accumulate a lot of transients.

You can clear WooCommerce transients and customer sessions in the WooCommerce Tools settings. If you’re not using WooCommerce, the transients manager plugin is a good tool for it.

Clear woocommerce transients customer sessions


17. Use Plugins To Speed Up The Admin

Here’s a list of plugins that can speed up your WordPress admin and reduce CPU usage. These are all lightweight and should help, but keep in mind that sometimes with plugins, less is better.

Plugin Description Category
Query Monitor Find slow queries + plugins Diagnostic
WP Hosting Benchmark View CPU/memory utilization Diagnostic
WP Healthcheck View WordPress/PHP/mySQL version, server, etc Diagnostic
Heartbeat Control Disable/limit Heartbeat Limiting
WP Rocket Helper Plugins Control preloading + automatic cache clearing Limiting
WP Crontrol Control cron jobs Limiting
Unbloater Remove various types of bloat Bloat Removal
Widget Disable Disable unused widgets in the admin Bloat Removal
Disable Woo Bloat Remove WooCommerce admin bloat Bloat Removal
Perfmatters Bloat removal settings + move wp-login Bloat Removal
Limit Login Attempts Block requests to wp-login Security
WPS Hide Login Block requests to wp-login Security
Transients Manager Edit/delete transients Transients
WP-Optimize Remove old databases tables Database
Redis Object Cache Object caching Caching
Cloudflare Set up Cloudflare APO Caching
Super Page Cache for Cloudflare Full page caching on Cloudflare Caching
BunnyCDN Used to set up BunnyCDN CDN
Blackhole for Bad Bots Block bad bots Bot Protection
Wordpress speed optimization plugins
See full list of optimization plugins


Frequently Asked Questions

What are the most common remedies for a slow WordPress admin?

The most common remedies for a slow WordPress admin are to remove high CPU plugins, check if your cache plugin's settings increase CPU usage, and reduce server load with CDNs and caching. But most likely, it's because you're on shared hosting.

Will changing hosts fix a slow admin?

Yes, a host with better specs can speed up your admin especially if you're using shared hosting with limited resources and CPU throttling.

Will a CDN speed up the admin panel?

CDNs offloads resources which lighten the load on your origin server, therefore speeding up both your website and admin panel. Cloudflare and BunnyCDN are both good choices.

Do bad bots slow down the admin?

Yes, spammy bots that constantly hit your site are a waste of server resources. You can use Wordfence to find all bots hitting your site in real-time, then use Cloudflare, Wordfence, or Blackhole for Bad Bots to block bad bots.

Do cache plugins affect the speed of the admin panel?

Cache plugins do preloading and automatic cache clearing differently. If these aren't controlled, it can increase CPU usage and slow down the admin.

How do I fix a slow WooCommerce admin?

Use the Disable WooCommerce Bloat plugin to disable WooCommerce notices, meta box, marketplace suggestions, and other bloat WooCommerce adds, and also clear transient and customer sessions.

Why is the WordPress admin slow on GoDaddy?

GoDaddy overcrowds their servers and has CPU limits. The lack of server resources may result in a slower admin and website.

How do I reduce admin-ajax.php server load?

Disable WordPress Heartbeat and use Query Monitor or GTmetrix waterfall to find plugins making calls to admin-ajax.php.

Did it work? Let me know in the comments :)

Still have a slow admin? Send me your set up (and GTmetrix report URL) and I’ll give my advice.



Your website and admin panel can load slow if CPU or memory usage is close to 100%.

You can check these in your hosting account or use WP Server Stats. The majority of this tutorial is focused on reducing server load and lowering usage. The less

Login to your hosting account and check your CPU usage.

It shouldn’t be even close to 100% since you want your server to stay relaxed. Hosting companies always tell you to upgrade, but you should always optimize your site first to reduce CPU before you consider upgrading. SiteGround, Bluehost, GoDaddy, and many other hosts have awful CPU limits that trap you into their contract, yet force you to upgrade. Don’t fall for it.

Cloudways cpu usage

Wp server stats cpu memory usage

You Might Also Like:


  1. I’m using Avada Theme, and the Avada Builder plugin (which is required) makes getting to the edit product page take 30s+. Removing the plugin reduces the speed to 3s+. I’ve disabled all of the options on Avada Builder, but it still takes forever to edit a product. Any ideas?


    • Moving away from Avada would obviously be the best solution (not good for the admin or frontend). It’s hard to know without looking through your configuration and settings but since you’re using Avada with WooCommerce, your choice of hosting and it’s configuration will be key. Have you run any diagnostic tools, checked memory usage, etc?

  2. Thanks Tom, this was really helpful. By the way, what’s the name of the related posts plugin you use at the end of your content? It looks really nice and simple


Leave a Comment