How to Disable the WordPress Heartbeat
What We'll Cover:
Did You Know?
- The heartbeat API sends ajax requests to the server using /wp-admin/admin-ajax.php?
- The heartbeat can send large number of requests to the hosting server and resulting in high CPU utilization?
WordPress Heartbeat Functions
- Creation of periodic auto save and revisions when you create / edit posts in editor.
- Real-time sales data on the dashboard by ecommerce plugins.
- Used to show notification on the WordPress admin dashboard.
- Shows the locking information of a post by other author.
Your Next Action Steps:
- Install the plugin.
- Disable or edit the frequency of the Heartbeat API.
Want Us to Boost Your Website Speed?
If you would like us to help you get a faster website we can help.
(If you want us to get your site to load lightening fast.)
Your Next Training Video
Watch the next short video to learn how to optimize 3rd party (external) scripts for a massive speed boost.
Hey and welcome.
Today, I’m going to show you a specific setting for WordPress that can give you a fantastic speed boost. And what we’re going to do is, we will disable something called the WordPress heartbeat API. What it does…
It’s an API service and it sends a continuous pass technically referred to as a tick, that performs periodic tasks. So it allows your browser to communicate with the server and there are three things that this pass or periodic task does.
Number one. It enables an auto-save feature. So when you’re busy writing something on your website, and your browser crashes, the auto-save means it would have saved the last version as well as revisions. The second thing is it sends real-time sales data for some e-commerce plugins.
The third thing is if you’ve got a multi author blog and two or three people are trying to edit the same post at the same time, it locks it down and sends a warning and I don’t think many of these features are required for most people, which is why we disable it because you’d rather have a faster website. Let me explain why.
Firstly, most websites are not multi-author and with a little bit of communication, you can prevent the rare instance of three people trying to work on the same article at the same time. Secondly, most people don’t need real-time real sales data for an e-commerce site.
So that’s not needed. The major feature of the heartbeat API that concerns people is the auto-save. What most people are doing is when they’re writing an article, they’re going to use an editor such as Microsoft Word.
They’re going to write the article, spellcheck it, save it there and then when they’re ready they’re going to load it on the website. So the auto-save feature really isn’t that necessary if that’s what you’re doing.
So let me show you how to disable the heartbeat. It’s quite simple and it’s going to give you a nice boost because remember, that while it’s running, it’s continuously using server resources. While you’re editing or your
Wp-admin or your back-end is open, it is always using your server resources. So, here is a way to stop it and disable it. So let’s make this a little smaller so you can see what’s going on.
There…And what you’re gonna do is you’re going to look for….you can’t see what I’m doing. You’re going to look for something called heartbeat control. You’re gonna activate it, then you’re going to jump down to settings heartbeat control. It looks over there and you’re going to select disable it.
Select or save. If you want to modify it, you can change the frequency. So think about this as the auto-save frequency. The more often it runs, the more resources that it’s going to need.
Obviously, the longer the delay and the less resources. So if you’re not ready to fully give it up you can increase the delay.
I would advise turning this thing off and rather having a faster website. You will earn more money from a faster website! So this is what we do to help people get faster websites.