WordPress Login Redirect Loop: Fix Being Sent Back to wp-login
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Your host says admin-ajax.php is using too much CPU. Find which action and plugin is calling it, then reduce the load safely.
When your host reports admin-ajax.php high CPU, it means a lot of requests are reaching a single WordPress file that handles background requests, and each one runs PHP. The file is not the cause; it is the doorway. Some plugin, theme feature or script is calling it too often. This guide shows how to find who is calling it, using logs and the action name, and how to reduce the load safely.
Look at your server access logs for requests to /wp-admin/admin-ajax.php and note the action value, the IP addresses and whether visitors are logged in. Match the action name to a plugin or theme by searching its code for that string. Check whether the load comes from logged-in users in the dashboard, where Heartbeat requests are normal, or from front-end visitors, where a plugin feature may be polling. Then reduce the calls: update, replace or configure the plugin, cache what can be cached, and rate limit abusive IPs. Test on staging.
How this guide was prepared: it is research-based. We used the WordPress developer documentation on AJAX listed under Sources, checked on October 23, 2026. We did not review your site; the cause is specific to your plugins and traffic.
The WordPress developer documentation says all WordPress AJAX requests are sent to wp-admin/admin-ajax.php, and the same URL works for both the admin and public areas. Each request has an action value that tells WordPress which handler to run. That is why front-end features such as search suggestions, cart updates, live counters and popups often appear here, and why the file can look busy on a normal site.

Ask your host for access logs, or find them in your hosting panel. Count requests to admin-ajax.php over a busy period and compare with the total. Note the time of day. If the host’s resource graph shows CPU spikes at the same times, you have a link. If you see few requests, the load may come from somewhere else; see WordPress slow after installing a plugin.
Logs of POST requests may not show the action unless your host logs request bodies, but GET requests show it in the URL. A browser’s Network tab also shows it: open your site, press F12, choose Network, filter for admin-ajax and look at the request payload. Search your plugin and theme folders for that action string to find the owner. Update the plugin first, as a newer version may have fixed the issue. If it is a feature you do not need, turn it off.
WordPress uses a Heartbeat feature in the editor and dashboard for autosave and post-locking, and it sends regular requests while someone is logged in. Several editors with tabs left open can add up. Close unused tabs, and ask your developer or host about limiting Heartbeat frequency, but do not turn it off blindly since autosave depends on it.
If anonymous visitors cause the load, find which feature polls the server. Examples include live stock counters, cart fragments, search-as-you-type and popup plugins. Options include caching the response, lowering the polling rate, loading the feature only on pages that need it, or replacing the plugin. Test your cart and checkout afterwards; see WordPress caching explained for how page caching interacts with dynamic features.
If one IP address or bot makes thousands of requests, block it or add rate limiting at your firewall, CDN or host. Do not block admin-ajax.php entirely, because many legitimate features depend on it and the site would break. If the traffic looks like an attack, treat it as a security issue and contact your host.
No. It is a normal WordPress core file. A hacked site can abuse it, but the file itself is legitimate.
Not safely. Many plugins and themes use it for normal features.
AJAX requests from both the admin and public areas go to this file, so front-end plugins often use it.
It may give you more room, but finding the caller is the lasting fix.
Pull one day of logs and find the top action. If you would like help, see WordPress maintenance or contact us with your host’s warning message. We cannot promise a specific CPU reduction.
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Old PHP stops getting fixes, but a rushed update can break plugins. Learn to check your version, test compatibility and switch PHP…
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout