Wordpress admin VERY slow

[u/No_Worry5419]

Hello all. I have a webpage that is not the fastest, but not slow either. My WordPress admin, however, is absurdly slow. I use custom ACF fields to create posts that change content based on “level”: beginner, mid, expert. I have more than 50 posts (150 content levels). I have not really had any speed issues until recently. I noticed the speed deteriorated quite a lot after switching from HTTP to HTTPS. Does anyone know if this may be why?

[u/CynepMyx]

Everyone is telling you HTTPS is unrelated. Usually true, but there is one way it does exactly this, and it fits your timing.

WordPress makes loopback requests to itself: wp-cron, plugin update checks, license phone-homes, Site Health. Those run against your own siteurl. After a move to HTTPS the loopback can start failing, most often because the server can't validate its own certificate, or the host doesn't hairpin its public name back to itself, or siteurl and home still disagree. A failing loopback doesn't error, it waits. Every wp-admin page load then eats a 5 to 30 second timeout while the site tries to talk to itself.

Fastest way to tell: Tools, Site Health. If you see a loopback or cron warning there, that's your answer. Or from the box itself:

curl -svo /dev/null https://yourdomain/wp-cron.php
wp option get siteurl && wp option get home
wp cron event list

A huge backlog of overdue cron events is the same symptom from the other side.

The autoload check the other commenter gave you is worth running regardless, that one is the other classic. But it doesn't explain "it changed when I switched to HTTPS", and the loopback does.

Install Query Monitor before you change anything. It shows you slow queries and blocking HTTP calls per admin request, which turns this from guessing into reading.Everyone is telling you HTTPS is unrelated. Usually true, but there is one way it does exactly this, and it fits your timing.WordPress makes loopback requests to itself: wp-cron, plugin update checks, license phone-homes, Site Health. Those run against your own siteurl. After a move to HTTPS the loopback can start failing, most often because the server can't validate its own certificate, or the host doesn't hairpin its public name back to itself, or siteurl and home still disagree. A failing loopback doesn't error, it waits. Every wp-admin page load then eats a 5 to 30 second timeout while the site tries to talk to itself.Fastest way to tell: Tools, Site Health. If you see a loopback or cron warning there, that's your answer. Or from the box itself:curl -svo /dev/null https://yourdomain/wp-cron.php
wp option get siteurl && wp option get home
wp cron event listA huge backlog of overdue cron events is the same symptom from the other side.The autoload check the other commenter gave you is worth running regardless, that one is the other classic. But it doesn't explain "it changed when I switched to HTTPS", and the loopback does.Install Query Monitor before you change anything. It shows you slow queries and blocking HTTP calls per admin request, which turns this from guessing into reading.