Auditing WordPress Plugins for Performance

Audit your WordPress plugins to find performance problems, remove what you do not need, and build a leaner, faster site.

Plugins are one of the most powerful tools in WordPress, but they are also one of the most common causes of slow sites. Treating your plugin list as an ongoing maintenance task - rather than a one-off tidy-up - pays dividends in speed, stability, and security.

Why plugins affect performance

Every active plugin loads PHP code on every page request, including pages where that plugin does nothing visible. A plugin that only adds an admin settings screen still runs its bootstrap code on the front end. The total number of active plugins matters, but code quality matters more: one poorly written plugin can cause more slowdown than ten well-written ones combined, through excessive database queries, slow calls to external services, or memory spikes that push against your account's resource limits.

On Kualo shared hosting, each account runs inside a CloudLinux container with its own CPU and memory quota. You can see your current usage in cPanel under the Resource Usage section. If your site is regularly brushing against those limits, inefficient plugins are one of the first things worth investigating. For a fuller explanation of how those limits work, see Understanding Resource Usage in cPanel.

This article covers single WordPress installations. WordPress Multisite has different plugin management rules and is outside the scope of this guide.

Auditing plugins with in-dashboard tools

Two free plugins give you a clear picture of what is happening under the hood. Install them from Plugins > Add New Plugin in your WordPress dashboard.

Query Monitor

Query Monitor adds a toolbar to your WordPress admin and front end showing real-time diagnostic data for the current page load. The two most useful panels to start with are:

Database queries - shows every query run on the page, how long each took, and which plugin or theme called it. Sort by time to find the worst offenders quickly.
Hooks and actions - shows which plugins are hooking into WordPress on each request, so you can spot plugins running code they have no business running on a given page.

Query Monitor also surfaces PHP errors and warnings, which can point to plugins with compatibility problems.

Query Monitor adds a small overhead of its own. Use it to diagnose, note your findings, then deactivate it when you are done.

Health Check and Troubleshooting

Health Check and Troubleshooting includes a troubleshooting mode that is safe to use on a live site. When you enable it, all plugins are disabled for your browser session only - your visitors continue to see the site exactly as normal. You can then re-enable plugins one at a time to isolate whichever one is causing a slowdown or error.

To use troubleshooting mode:

Install and activate Health Check and Troubleshooting.
Go to Tools > Site Health in your WordPress dashboard.
Click the Troubleshooting tab.
Click Enable Troubleshooting Mode.
Re-enable plugins one at a time and reload the page after each one to identify the culprit.
Click Disable Troubleshooting Mode when you are finished to restore the normal view for your session.

Troubleshooting mode is session-based and cookie-driven. Your visitors are completely unaffected while you work through this process.

Deeper profiling on a staging site

For more invasive profiling - such as Xdebug call tracing or step-through debugging - always work on a staging copy rather than your live site. WP Toolkit makes it straightforward to spin up a staging environment: see Creating Staging Websites with WP Toolkit. Once your staging site is ready, you can follow the Xdebug profiling workflow described in Profiling slow PHP requests with Xdebug to pinpoint the exact function causing a slowdown.

Deactivating and deleting unused plugins

There is an important difference between deactivating a plugin and deleting it.

Deactivating stops the plugin's code from running, but leaves all its files on the server. This is appropriate during a diagnostic session when you may want to re-enable the plugin shortly afterwards.
Deleting removes the plugin files entirely. Any plugin you have decided you no longer need should be deleted, not just deactivated. Dormant plugin files sitting on your server are a security risk: they can contain vulnerabilities that attackers can exploit even when the plugin is inactive.

To delete a plugin from the WordPress dashboard:

Go to Plugins > Installed Plugins.
If the plugin is active, click Deactivate first.
Once deactivated, click Delete under the plugin name.
Confirm the deletion when prompted.

Deleting a plugin through the WordPress dashboard removes its files completely. You do not need to go into cPanel File Manager to do anything further.

Some plugins store data in your database when they are installed. Deleting the plugin files does not automatically remove that data. If a plugin offers a built-in uninstall or clean-up option, use it before deleting.

For a broader look at keeping your plugins updated and patched, Patchman and Imunify360 both monitor your account for known vulnerabilities in installed software, including outdated plugins.

Keeping your plugin count lean

Auditing once is useful; auditing regularly is what keeps a site fast. A few practical habits make a real difference.

Review plugins that have not been updated in over a year. An unmaintained plugin may still work, but it is worth asking whether you still need it and whether WordPress core now covers that function natively. Features like lazy-loading images, responsive embeds, and basic SEO controls have all moved into core in recent years.

Prefer focused plugins over bloated multipurpose ones. If you only need one feature from a plugin that offers twenty, look for a smaller plugin that does just that one thing. Less code loaded per request means a faster site.

Check reviews and active install counts. A plugin with hundreds of thousands of active installs and recent positive reviews is a reasonable quality signal. A plugin last updated three years ago with a handful of installs warrants more caution.

Avoid stacking duplicate plugins. Two caching plugins, two SEO plugins, or two contact form plugins running simultaneously will conflict and slow your site down. Audit for overlap and remove the one you use less.

Back up before making changes. Before removing a plugin you are unsure about, take a quick backup using WP Toolkit so you can restore easily if something breaks.

Connecting plugin performance to resource usage

Kualo shared hosting accounts run under CloudLinux, which enforces per-account CPU and memory limits. These limits exist to keep the server stable for everyone, and they are visible in the Resource Usage section of cPanel.

If your site regularly hits those limits despite having a modest amount of traffic, excessive or inefficient plugins are a common cause. Reducing your active plugin count, removing poorly coded plugins identified through Query Monitor, and enabling LiteSpeed Cache can all reduce the load your site places on the server.

If you have already optimised your plugins and are still consistently hitting resource limits, contact our support team. We can review your account and discuss whether a plan upgrade or other options are appropriate.

For a broader look at speed optimisation beyond plugins, How to read speed reports (GTmetrix, Pingdom, PageSpeed) is a useful next step.

Managing and auditing WordPress plugins for performance