Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Find Slow Plugins in WordPress

Short answer

Install Query Monitor, open a slow page while logged in as an admin, and check the Queries and HTTP API Calls panels to see which plugin adds the most time. Then confirm the result on a staging copy by deactivating that plugin and comparing load times before and after. Replace or remove the plugin if the page stays faster without it.

Key takeaways

  • Query Monitor groups database queries by plugin, so the slowest plugin is easy to spot.
  • A good LCP is 2.5 seconds or less and a good INP is 200 milliseconds or less, as of November 2026.
  • Site Health at Tools > Site Health flags signs of trouble but does not name the slow plugin.
  • Test plugins one at a time on staging, never several at once on the live site.
  • P3 Profiler closed on 13 October 2022, so use Query Monitor instead.

How do you know a plugin is slowing down your WordPress site?

A slow plugin is a plugin that adds clear extra load time, database queries, or HTTP requests to a page.

The clearest sign is timing. A page that loads fast with a plugin off and slowly with it on points to that plugin.

If CPU use jumps while traffic stays normal, read our guide to fixing high CPU usage before you blame one plugin.

Speed targets give you a line to judge by. The web.dev guide to LCP sets a good LCP at 2.5 seconds or less and a poor LCP above 4.0 seconds, as of November 2026.

The web.dev guide to INP sets a good INP at 200 milliseconds or less and a poor INP above 500 milliseconds, as of November 2026.

MetricGoodNeeds workPoor
LCP2.5 seconds or less2.5 to 4.0 secondsMore than 4.0 seconds
INP200 ms or less200 to 500 msMore than 500 ms

LCP is the render time of the largest image, text block, or video in the viewport. INP measures how fast a page answers clicks, taps, and key presses. Both guides judge the 75th percentile of page loads.

What do you need before you start checking plugins?

You need an admin account, a backup, a staging copy of the site, and Query Monitor installed.

Query Monitor only shows its output to admins on a single site, and to super admins on Multisite. Log in with an admin account or you will see nothing.

You need these four items ready:

  • A full backup, so you can undo a bad change.
  • A staging copy of the site for safe tests.
  • A short list of your slowest pages to use as test pages.
  • The load time of each test page before you change anything.

Plan for 30 to 60 minutes for a first pass on a small site, since each plugin gets its own test.

How do you use Site Health to check for plugin problems?

Open Tools > Site Health in the admin menu and read the Status tab for critical issues and recommended improvements.

Site Health joined WordPress in version 5.2, and the WordPress documentation places it under Tools > Site Health. The screen runs checks on your site and groups the results for you.

WordPress core ships with two tabs, Status and Info, as the Site Health handbook explains. The Status tab lists critical issues, recommended improvements, and passed tests. The Info tab lists facts about your setup, such as your WordPress version, server, and plugins.

Site Health does not name a slow plugin. It flags signs that plugins can cause, such as failed loopback requests, a blocked REST API, or an old PHP version.

A failed loopback or REST API check is a lead worth following.

How do you install and use Query Monitor to find slow plugins?

Install Query Monitor from Plugins > Add New, activate it, then load a front-end page and open its toolbar menu to see timings by plugin.

Query Monitor is a free plugin on WordPress.org. Version 4.1.1 was released on 27 October 2026 and needs PHP 7.4 or higher, as of November 2026.

The same page notes that Query Monitor is tested up to PHP 8.5 and supports WordPress versions up to three years old.

Follow these steps to set it up:

  1. Go to Plugins > Add New, search for Query Monitor, click Install Now, then Activate.
  2. Visit a slow page on the front end while logged in as an admin.
  3. Click the Query Monitor menu in the admin toolbar to see page generation time, query count, and memory use.
  4. Open the Queries panel and sort by time to see the slowest queries first.
  5. Open the HTTP API Calls panel to see slow requests to outside services.

Version 4 added the Timeline view and renders its panels in the browser instead of on the server.

Query Monitor has a small effect on page generation time, which its author calls negligible.

How do you read Query Monitor results for slow database queries?

Open the Queries panel, sort by time, and look for slow or duplicate queries grouped under one plugin name.

Query Monitor flags slow, duplicate, and faulty queries. You can filter by query type, such as SELECT, UPDATE, or DELETE, and by the part that ran it.

The panel groups all queries by the plugin, theme, or function behind them. That grouping is what turns a long list into a named suspect.

PanelWhat it showsHow it helps
QueriesDatabase queries by time and callerFinds the plugin behind slow queries
HTTP API CallsOutside requests with time and codeFinds slow calls to other services
TimelineSteps in order with timingsShows when the slow step runs

Look for the same query repeated many times on one page.

What counts as a slow query?

There is no single limit, since hosts differ. Compare queries on the same page and treat the slowest few as your suspects.

How do you check plugins that make slow HTTP requests?

Open the HTTP API Calls panel in Query Monitor and look for requests with long times or failed response codes from one plugin.

The panel lists each request with its response code, the part behind it, and the time it took. It also alerts you to failed or faulty requests.

A call that takes seconds on every page load is a suspect.

Check three points for each slow request:

  • How long it takes, in seconds.
  • How often it runs on the page.
  • Whether the page still works when it fails.

A request that fails and still slows the page is a strong suspect.

How do you test plugins one by one on a staging site?

On a staging copy, deactivate one plugin at a time, reload the test page, and note the load time after each change.

A staging site is a private copy of your site used for tests. Our guide to setting up a staging site for WordPress shows the setup steps.

Follow these steps for each plugin you test:

  1. Record the load time of a slow page on staging with all plugins active.
  2. Deactivate one plugin under Plugins > Installed Plugins.
  3. Clear the cache, then reload the same page and record the new time.
  4. Reactivate the plugin if the time did not change, then test the next one.
  5. Leave a plugin off when the page gets clearly faster without it, and note the change.

Test only one plugin per round. Changing two at once hides which one caused the change.

Use the same page and the same test for every round.

How can Chrome DevTools help you find a slow plugin?

Open Chrome DevTools on a slow page, record a load in the Performance panel, and look for long tasks and slow resources tied to plugin files.

Chrome DevTools is the tool set built into Chrome. The Performance panel records what the browser does while a page loads and runs.

The Performance panel shows your live LCP and CLS scores, and INP once you click, tap, or press a key.

Follow these steps to record a load:

  1. Open the slow page in Chrome.
  2. Press Control + Shift + I on Windows or Linux, or Command + Option + I on Mac, to open DevTools.
  3. Click the Performance tab, then click Record and reload.
  4. Wait for the page to load, then stop the recording.
  5. Look for long tasks and slow files under wp-content/plugins in the results.

The DevTools guide uses a 4x CPU slowdown to mimic a mobile device.

DevTools shows files, not plugin names. Match a slow file path to the plugin folder it sits in.

What should you do once you find the slow plugin?

Replace the slow plugin with a lighter option, update it, change its settings, or remove it if you do not need it.

Check for an update first, since an update can fix a slow query or a bad request.

Look at the plugin settings next, and turn off feeds, logs, or checks you do not use.

If the plugin stays slow, look for a replacement on WordPress.org. Check the replacement for known flaws with our guide to checking a plugin for vulnerabilities before you install it.

Do not install P3 Profiler to check your work. WordPress.org closed it on 13 October 2022, and the page still lists the closure as permanent as of November 2026.

How do you check that the fix worked?

Compare the same before and after numbers on the same page, using Query Monitor timings and LCP and INP from the same tool.

Write down the page generation time, query count, and total query time from Query Monitor before you change anything.

Record LCP and INP for the same page with the same tool, then stay with that tool.

After the fix, clear the cache and test the same page the same way.

A fix worked when LCP falls to 2.5 seconds or less and INP falls to 200 milliseconds or less. Repeat the test twice more to rule out one lucky load.

For the next steps after a fix, see our guide to speeding up WordPress.

If the numbers barely move, the plugin was not the main cause. Go back to the Query Monitor results and test the next suspect.

What mistakes should you avoid when finding slow plugins?

The main mistakes are testing on the live site, changing several plugins at once, and trusting a single speed reading.

Avoid these five mistakes:

  • Testing on the live site instead of staging, which can break pages for visitors.
  • Deactivating several plugins at once, which hides the one that caused the change.
  • Judging plugins by count alone. Our guide to how many plugins is too many for WordPress explains why count alone says little.
  • Using one speed reading, which can come from a warm cache or a quiet server.
  • Checking only the front end when the admin area is slow. See our guide to fixing a slow admin dashboard for that case.

Query Monitor keeps no stored record of its data and sends nothing to other parties.

Frequently asked questions

Can a plugin slow down only the WordPress admin area?

Yes. A plugin can run heavy code only in the admin area, for example on the posts list or the orders page, while the front end stays fast. Open Query Monitor on a slow admin page and check the Queries panel the same way. If the front end is fast and the admin area is slow, the cause is likely a plugin that works only in the admin area.

Is Query Monitor safe to leave active on a live site?

Yes, for short checks. Its output is shown only to admins, it stores no data, and it sends nothing to other parties. Its effect on page generation time is small. Still, deactivate it when you finish, since a debugging plugin has no job on a live site once the slow plugin is found.

Why can't I download P3 Profiler anymore?

WordPress.org closed P3 Profiler on 13 October 2022 at the author's request, and the closure is permanent. The plugin page no longer offers a download. Old copies from other sites are unsafe to install, so use Query Monitor instead.

How many plugins should I deactivate at once when testing?

Deactivate one plugin at a time. If you switch off several at once and the page gets faster, you will not know which one caused the change. Test one, record the time, switch it back on if nothing changed, then move to the next plugin.

What if Query Monitor shows no slow plugin but the site is still slow?

Look past plugins. The theme, the host, large images, or a missing cache can also slow a site. Check the Site Health Status tab for server and PHP notes, then test the theme and the host the same way you tested plugins, one change at a time.

Sources

  1. Query Monitor WordPress.org
  2. Site Health: keep your website healthy WordPress.org
  3. Site Health - Common APIs Handbook WordPress Developer Resources
  4. Interaction to Next Paint (INP) web.dev
  5. Largest Contentful Paint (LCP) web.dev
  6. Analyze runtime performance Chrome for Developers
  7. P3 (Plugin Performance Profiler) WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test