Your site used to feel quick, and now pages take a few seconds too long. Or the admin crawls every time you save a post. Plugins are a natural suspect, and often a fair one. But “slow” is trickier to troubleshoot than “broken”, because it’s harder to measure and easier to fool yourself about.

Here’s a way to go about it that gives you an answer you can trust.

First, measure instead of guessing

Before you change anything, put a number on the problem. Otherwise you can’t tell whether a change helped.

  1. Open the slow page in a private window, so you’re not seeing a version cached by your browser.
  2. Press F12, open the Network tab, and reload.
  3. Click the first request in the list (the page itself) and look at the timing details. The figure you want is how long the server took to respond, usually shown as Waiting for server response or TTFB (time to first byte).

Reload a few times and write down a typical value. If the server responds in 0.3 seconds but the page still feels slow, the problem is in the browser: large images, too many scripts, heavy fonts. That’s a front-end job, and a page speed tool like Lighthouse is the better place to look.

If the server itself takes 2, 3 or 5 seconds to respond, the slowness is happening in PHP and the database. That’s where plugins usually come in.

Make sure you’re not measuring the cache

Caching makes a big difference to speed, and it can hide what you’re trying to measure. A cached page might load instantly for visitors, while the uncached version takes four seconds. Both numbers matter, but for troubleshooting you want the uncached one, because that’s the work your plugins are actually doing.

Being logged in usually bypasses page caching, which is handy. Just compare like with like: test logged in every time, or logged out every time.

Check the usual suspects

Some kinds of plugins are slow more often than others:

  • Plugins that call outside services on every page load: social feeds, license checks, some analytics and security plugins. If that service is slow, your site waits for it.
  • Plugins with heavy database queries: related posts, statistics and some search plugins.
  • Plugins that load everything everywhere: a contact form plugin adding its scripts to every page, or a page builder loading its whole toolkit on pages that don’t use it.
  • Security plugins with aggressive scanning running during visits.
  • Leftovers from old plugins. Site Health (Tools → Site Health) may warn you about too much autoloaded data. That’s often settings left behind by plugins you deleted long ago, and WordPress loads it on every single request.

Look inside with Query Monitor

The free Query Monitor plugin is the standard tool here. It adds a menu to the admin toolbar showing how long the page took to generate, how many database queries ran, and which plugin made them. Its panels for queries by component, slow queries and HTTP API calls often point straight at the culprit.

It’s not always conclusive, though. Some slowness doesn’t show up as queries, and a plugin can slow down another plugin without appearing guilty itself. When the numbers don’t point anywhere obvious, test.

Find it by testing

The idea is the same as for any other plugin problem: switch plugins off, measure again, and narrow it down by halving the list. Our guide on finding which plugin is breaking your site explains the halving method in detail.

For a speed problem, you need a clear yes-or-no line before you start. Pick a threshold based on your measurements, something like: “Is the server response still over 2 seconds?” Then at each step, reload the page two or three times and judge by the typical value, not the best or worst one.

On a live site, you don’t want to switch plugins off for your visitors to do this. Culprit Finder switches them off in your browser only, and asks after each step whether the problem is still there. It also marks those pages as not cacheable for you, so you’re always measuring the real, uncached response.

Be honest with yourself about one limitation. This works well when the slowness is big and consistent: four seconds with the culprit on, under one second with it off. If your timings jump around a lot, or the difference is small, your answers may contradict each other. Culprit Finder then tells you the answers didn’t add up rather than blaming the wrong plugin. In that case, Query Monitor or your host’s performance tools are the better route.

When you’ve found the slow plugin

  1. Check its settings. Many slow plugins have options to load less: only on certain pages, fewer items in a feed, a longer cache time for external data.
  2. Update it. Performance fixes are common in changelogs.
  3. Tell the author, with numbers: “Server response goes from 0.6 s to 3.1 s with your plugin active on this page.” Specific reports get fixed.
  4. Look for a lighter alternative, if the plugin does something you could live without or get elsewhere.

If no plugin is to blame

If the site is still slow with every plugin off, look at your theme, your hosting plan and your PHP version. An outdated PHP version, or a crowded shared server, can make even a plain WordPress install sluggish. Your host can tell you which PHP versions you can switch to, and whether your site is hitting its resource limits.