The basic idea is to give administrators easy access to disable typical bloat, non-utilized functions or whole modules with just a few clicks.<\/p>\n\n
There are no fancy UIs, external libraries, or hidden features \u2014 just clean, fast and easy way to disable things you might not want in your project or website.<\/p>\n\n
All the required information about usage can be found on the plugin settings page; each function is fully described.<\/p>\n\n
Source code can be found on official GitHub repository<\/a><\/p>\n\n The plugin does not:<\/p>\n\n Yes. There are no paywalls or hidden\/premium features.<\/p><\/dd>\n Most of the options should be safe to use, but please read the descriptions carefully \u2014 especially those marked with a red asterisk next to function title.<\/p><\/dd>\n The end result is probably the same in most cases. The differences come down to three principles:\n 1. This plugin does not add anything more than absolutely needed to actually turn things off;\n 2. It will always be (or at least try to) focused on core-related, optimization features.\n 3. It aims to inform users about each feature clearly, without infodumps.<\/p><\/dd>\n Under the general settings tab, or (by default) at \/options-general.php?page=bloatoff-utils; keep in mind that the tab is only available to administrators (or super-admins) by default.<\/p><\/dd>\n For now, there is no network-wide configuration or dedicated page, so it works on a per-site basis.\nThis is on the to-do list, but I can't say when it will be added and properly tested.<\/p><\/dd>\n I'm always looking for new features to add. Feel free to suggest anything you think is worth including.<\/p><\/dd>\n No, I'm keeping it core-related only. Sorry.<\/p><\/dd>\n While I do think it shouldn't be enabled by default, it's more of a security-related feature and doesn't affect installation optimization.<\/p><\/dd>\n There's a high probability that either your theme or one of your plugins is using Gutenberg-related styles or scripts.\nThis option is intended only for installations that do not rely on Gutenberg in any way.<\/p><\/dd>\n Some features are purely technical, and a few are quite archaic (RSD, for example, was added in version 2.0.0). \nUnfortunately, not everything is documented in an accessible way.<\/p><\/dd>\n Some external services rely on oEmbed discovery links and require them to fetch content from your website properly. \nWordPress-related services don't need them and will fetch everything correctly even without those links (assuming your site is configured properly and doesn't have additional blocking rules).<\/p><\/dd>\n Too many things rely on Heartbeat, and removing it entirely is a really bad idea \u2014 most of the potential issues would come from that option.\nIf you still want to disable it, add this snippet to your active theme's functions.php file after Yes. It changes the global \"interval\" setting.<\/p><\/dd>\n It may. It's best to leave it unchecked if you're not sure about this setting. \nSaving the option as unchecked will also reset the interval to the default value of 15 seconds.<\/p><\/dd>\n The easiest way is to check the \"Media handling\" tab in the Site Health tool. \nIn most cases, you'll see the active Image Process Engine along with more detailed information.<\/p><\/dd>\n No. Revisions are only removed when you update each post or page individually.<\/p><\/dd>\n Adding such an option would require considering many factors, like installations with limited system resources or thousands of records to clean. To be honest, I consider this outside the plugin's scope. If you need this functionality, please try plugins like WP-Sweep<\/strong> or Optimize Database after Deleting Revisions<\/strong>.<\/p><\/dd>\n It depends entirely on your workflow. In most cases, I would say 3\u20135, but some people may need to check up to 10 versions back.<\/p><\/dd>\nPrivacy<\/h4>\n\n
\n
Option A:<\/h4>\n\n
\n
Option B:<\/h4>\n\n
\n
Option C:<\/h4>\n\n
\n
\n
Is it 100% free?<\/h3><\/dt>\n
Is it safe to use?<\/h3><\/dt>\n
How is it different from other solutions already available in the repository?<\/h3><\/dt>\n
Where is the settings page located?<\/h3><\/dt>\n
Does it work on multisite installations?<\/h3><\/dt>\n
Will you consider adding new features?<\/h3><\/dt>\n
Will you consider removing bloat from other plugins?<\/h3><\/dt>\n
Why aren't there features like \"App Password removal\"? Isn't that considered a rarely used function by the majority of users?<\/h3><\/dt>\n
My website went blank after removing Gutenberg styles! What should I do?<\/h3><\/dt>\n
Why do some links redirect to developer pages rather than official documentation?<\/h3><\/dt>\n
What does the warning in oEmbed discovery link actually mean?<\/h3><\/dt>\n
Why is there no option to remove the WordPress Heartbeat API altogether?<\/h3><\/dt>\n
<?php<\/code>: Snippet<\/a>. Just keep in mind that you're doing so at your own risk, and it may break some key functionality on your website.<\/p><\/dd>\nDoes the Heartbeat control change the interval for all instances?<\/h3><\/dt>\n
Will changing the Heartbeat interval break anything on my site?<\/h3><\/dt>\n
Regarding Image Process Engine - how do I check which engine I use?<\/h3><\/dt>\n
Will old revisions be removed right away after limiting their number globally?<\/h3><\/dt>\n
Why is there no option to remove old revisions in bulk?<\/h3><\/dt>\n
What is the most optimal number of revisions to keep?<\/h3><\/dt>\n