WP Manifestindependent plugin directory
manifest / performance / wp-request-buster

Request Buster

Find themes and plugins that are (ab)using wp_remote functions to slow down your site (WordPress plugin)

by khromov · github.com/khromov/wp-request-buster

18stars
4forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/khromov/wp-request-buster/archive/refs/heads/master.zip

Declares an update source (khromov/wp-request-buster), so updates arrive through the plugin's own updater.

From the readme

Request Buster Find themes and plugins that are (ab)using wpremote functions to slow down your site Screenshots Preface WordPress has functions for getting remote resources (internally using cURL or PHP streams) Whenever these functions (such as wpremoteget()) run during a page load request, they will slow down your site, because WordPress has to wait for the external request before returning the page. This is bad practice, yet so many plugins and themes use it. Debugging is notoriously hard because requests appear only occasionally (they are often cached via the Transients API). Request Buster is a plugin that shows you in the top admin bar if any remote requests were triggered by the current page load. Keeping it open as you develop and use your site will let you find plugins that make remote requests. The correct way to handle loading of remote resources are: Serving the page and grabbing the remote resource via AJAX OR Schedule the remote request to go through WP CRON. Instructions Place request-buster.php in /wp-content/mu-plugins/ (Create the folder if it does not exist) Check the top admin bar to find pages that trigger remote requests Remove the naughty plugins

Read the full README on GitHub →

Releases

TagPublished
1.0 Feb 8, 2015

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.