There are no affiliate links on PagePipe.
This request – admin-ajax.php – can cause a 436-millisecond parallel delay. Many try to eliminate the delay. It’s a popular topic on blogs. “How do I get rid of – or speed up – the Ajax request?”
The WordPress Heartbeat API allows WordPress 3.6 and all newer version to:
communicate between the web browser and the server
improve user session management
The WordPress Heartbeat API uses /wp-admin/admin-ajax.php to run AJAX requests from the web-browser. Which in theory sounds awesome, as WordPress can keep track of what’s going on in the dashboard.
However this can also start sending excessive requests to admin-ajax.php and leads to high CPU usage. Anytime you leave a web-browser open on a page the Heartbeat API could be an issue.
Are you having an excessive amount of admin-ajax.php requests? You can disable the WordPress Heartbeat API to prevent this from happening.
Change the WordPress heartbeat API behavior. To use fewer server resources, try one of these plugins:
A “waterfall” speed test often indicates the heaviest asset on pages is jQuery Ajax.
39k page weight
200 milliseconds load time
But you can get a double load of another 33k from Google CDN. So WordPress core and a plugin may request different versions of Ajax. This is inefficient but not critical.
From online references, Ajax activation happens with add-on services. For example, ConvertKit tracks form submissions. We see it activated on WooCommerce sites with dynamic Cart Fragments. And the WordPress Popular Posts plugin.
“Starting version 4.2.0, WordPress Popular Posts can cache views data in-memory (Redis, Memcached, etcetera) and batch update the views count of your posts and pages when more than 180 seconds have passed since the last batch update, which greatly reduces the number of database writes. This of course also means better overall performance.”
WordPress Popular Post plugin adds 400 milliseconds to global page loading (Boo!) and only 4k to page weight.
There is no easy fix today when it comes to reducing Ajax page weight. Maybe in the future?
Instead of band-aid approaches, we drill down to the root cause of your slow site. This is origin optimization. Also known as site tuning. To do this, we analyze site components:
- Scripts and third-party services.
- Images and media library.
- We minimize globally loading plugin effects.
Find out more details about Site Tuning – Get Speed!