Your WordPress site is slow, and you suspect a plugin. But which one?
Guessing is slow and risky. You can turn plugins off one at a time, but that takes hours, and it can break a live site. A speed test tells you that a page is slow, but it does not tell you which plugin or query is the cause.
Query Monitor is a free plugin that answers this question. It shows what happens inside WordPress each time a page loads: which database queries ran, how long each took, which hooks fired, which outside requests were made, and which plugin or theme was responsible for each.
In this review, we’ll explain what Query Monitor does, how to install it, and how to read its main panels. We’ll show how to use it to find slow plugins and queries, and we’ll cover the cautions that you should know before you use it on a live site.
What Is Query Monitor?
Query Monitor is a developer tool for WordPress and WooCommerce. According to the project’s page on GitHub, it shows debugging and performance information about the current request. When you are logged in as an administrator, it adds a panel to the admin bar, and you can open it on any page of your site.
It is built for developers, but a site owner can use it too. You do not need to write code to read the main panels.
What Query Monitor Shows
| Panel | What it shows | Why it helps |
|---|---|---|
| Database queries | Every query, its time, and the component that ran it | Finds slow and repeated queries |
| Queries by component | Queries and time grouped by plugin, theme, or core | Shows which plugin is heaviest |
| Hooks and actions | The hooks that fired, with callbacks and priorities | Finds code that runs too often |
| HTTP API calls | Outside requests made by the server, with time and result | Finds slow calls to other services |
| PHP errors | Warnings, notices, and deprecated messages, with the source | Finds code that needs fixing |
| Scripts and styles | Files loaded on the page, and what depends on them | Finds extra files from plugins |
| Template and blocks | Which template and blocks built the page | Helps with theme problems |
| Rewrite rules and query variables | How WordPress read the address | Helps with page not found errors |
| Capability checks | Which user permissions were checked | Helps with access problems |
| Environment | PHP and database details | Shows the server setup |
The key feature for speed work is the grouping by component. It tells you how much time and how many queries each plugin, theme, or core caused on the page.
Installing Query Monitor
- Go to Plugins, then Add New, and search for Query Monitor.
- Install and activate it.
- Look at the admin bar. A small box with the page generation time and memory use appears.
- Click the box to open the panel at the bottom of the page.
By default, only administrators on a single site, and super admins on a multisite network, can see its output. Other visitors do not see it.
A note about the database file
Query Monitor adds a small file named db.php in your wp-content folder, as a link, so that it can record database queries in more detail. If your folder cannot be written to, the plugin still works, but you may miss some database detail. If you ever remove the plugin, check that this file is gone as well.
Cautions Before You Use It
A debugging tool adds work to each page, and it exposes technical information.
- Do not leave it active on a busy live site longer than you need. It adds load, and it can make a slow page slightly slower.
- The project page says that it does not store its data permanently or send it to third parties, but you should still limit who can see its output.
- Do not share screenshots that show private details, such as database queries with user data.
- If you can, run your first test on a staging copy.
- Remember that a test on a staging site may not match the live site, because traffic, caching, and data differ.
- Turn the plugin off, or remove it, when you finish.
The project’s page does not discuss production use, so treat this as general safety advice, not a statement from the authors.
How to Find a Slow Plugin: Step by Step
Here is a simple method that works for most sites.
Step 1: Measure your baseline
Run a speed test on a few pages, and note the time. Open Query Monitor, and write down the page generation time, the memory use, and the number of database queries for each page.
Step 2: Look at queries by component
Open the Database Queries panel, then choose the view that groups queries by component. Each row shows a plugin, the theme, or core, with the number of queries and the total time.
- A plugin with a large share of the total time is a suspect.
- A plugin with hundreds of queries on a simple page is a suspect.
- Core should take a fair share. A single plugin that takes more than core is worth a look.
Step 3: Look for slow queries
Sort the queries by time. Query Monitor flags slow queries, and it also flags duplicates. A slow query is one that takes a long time to run, and a duplicate is the same query repeated many times.
- Click a slow query to see where it came from. The call stack shows the plugin file and the function.
- A query that scans a large table without an index is a common cause of slowness.
- Repeated identical queries can often be fixed by caching, and a persistent object cache can help.
Step 4: Check the hooks
Open the Hooks and Actions panel. A hook with many callbacks from one plugin may show code that runs on every page when it is needed on only a few.
Step 5: Check outside requests
Open the HTTP API Calls panel. Look for requests to other services that take a long time, or that fail. A plugin that calls a slow outside service on each page load can slow down your site, even if your server is fast.
Step 6: Check PHP errors
Warnings and notices do not always break a page, but a plugin that throws many of them is often poorly maintained. Note which ones appear.
Step 7: Test the suspect
Deactivate the suspect plugin on staging, or replace it, and measure again. If the numbers improve, you have found a cause. If they do not, check the next component on the list.
If you want a wider method for testing plugins, our guide on how to find which plugin is breaking your site shows safe ways to turn plugins on and off.
Reading the Admin Bar Summary
The summary in the admin bar shows four numbers.
- Page generation time: how long the server took to build the page.
- Peak memory use: the most memory that PHP used.
- Database query time: the total time spent on queries.
- Number of queries: how many queries ran.
These are helpful but not a full picture. They measure the server side only. A page can have a fast generation time and still feel slow, because of large images, heavy scripts, or slow outside resources. For those, use a browser speed test too. Our guide on why your WordPress website is so slow explains how to combine both.
How Slow Queries Happen
A database query is a question that WordPress asks the database. Most are fast. Some are slow, for reasons that you can often see.
| Cause | What it looks like | What to do |
|---|---|---|
| A large options table with too much autoloaded data | Slow query on the options table at every page load | Clean old plugin data, and ask plugin authors before removal |
| A missing index on a custom table | A slow query on a plugin’s own table | Contact the plugin’s author |
| Many meta queries | Slow search or filter results | Use a better plugin, or simplify the query |
| Large post and comment tables | Slow listing queries | Clean revisions, spam, and old data |
| Heavy shop queries | Many queries on product pages | Use an object cache, and reduce plugins |
| Repeated identical queries | The same query many times | Use object caching |
You do not need to fix the query yourself. Often the best action is to report the finding to the plugin’s author, replace the plugin, or add a cache.
Using Query Monitor With Ajax and the REST API
Slow pages are not the only problem. Background requests can be slow too, such as those that save posts in the editor or load a shop’s cart.
- Query Monitor can show debugging data for these requests, and for REST API calls from logged-in users, if you are allowed to view its output.
- Open the panel while you use the editor, and look at the requests that run in the background.
- A slow admin area, as opposed to a slow front end, is often caused by plugins that run heavy tasks in the dashboard.
Using It to Find PHP Errors and Deprecated Code
Query Monitor shows PHP warnings, notices, and deprecated function messages, with the file and line.
- A deprecated message means that a plugin uses code that WordPress plans to remove. It is a warning that the plugin may break in a future version.
- A warning on every page load shows careless code, and it can slow the site by writing to the error log.
- Errors can also point to a plugin that is not compatible with your PHP version.
Use these messages to decide which plugins to update, replace, or report. For deeper debugging, the official WordPress debugging guide explains how to turn on the debug log.
Using It to Check Your Own Snippets
If you add custom code with a snippet plugin or your theme, Query Monitor shows how much time and how many queries that code adds. A small snippet that runs a query on every page can add up. Our review of WPCode explains how to add snippets more safely, and Query Monitor is a good way to measure what they cost.
Pros and Cons
Pros
- Free, and made for WordPress.
- Groups results by plugin, theme, and core, which makes blame clear.
- Shows queries, hooks, outside calls, scripts, and errors in one place.
- Works with WooCommerce and block themes.
- Does not require code to read the main panels.
- Active development and a long history.
Cons
- It is a developer tool, and the panels can look dense at first.
- It adds some load while it is active.
- It measures the server side only, not the browser side.
- It exposes technical details, so it must be limited to trusted users.
- The project page states that it does not meet an accessibility standard for font size, so some users may find the panel hard to read.
- Findings need judgment. A high number does not always mean a problem.
Alternatives and Companions
Query Monitor works well alongside other tools.
- A browser speed test, for front-end loading, images, and scripts.
- A waterfall chart, for the order and timing of files.
- The server’s error log and slow query log, which your host may provide.
- An application performance monitoring service, for continuous tracking on a busy site.
- A staging site, for tests without risk.
Use Query Monitor to find the cause on the server side, and the other tools for the browser side.
A Safe Workflow for Site Owners
- Take a backup.
- Clone your site to staging, if your host offers it.
- Install Query Monitor on staging.
- Open your slowest pages, and record the numbers.
- Find the components with the most time and queries.
- Test changes one at a time: update, replace, or turn off the suspect plugin.
- Measure again after each change.
- Apply the working fix to the live site.
- Remove Query Monitor from the live site, if you installed it there.
- Test again with a speed tool, and keep notes.
A Worked Example: Finding a Slow Plugin on a Blog
Here is a realistic case, to show how the steps fit together.
A blog loads slowly. A browser test shows that the server takes more than two seconds to respond, even on a cached page after a purge. The owner installs Query Monitor on a staging copy and opens the home page.
- The admin bar shows a page generation time of about two seconds and 180 database queries.
- The component view shows that a related posts plugin ran 70 of those queries and took more than half of the total query time.
- Clicking the slowest query shows that it searches the post meta table on every page load.
- The owner turns off the related posts plugin on staging, and the page generation time drops to under half a second.
- The owner replaces the plugin with a lighter one that caches its results, and tests again.
- The same change is applied to the live site, and the server response time improves.
The lesson is that one plugin caused most of the delay, and Query Monitor showed which one in a few minutes. Without the tool, the owner might have blamed the host, or turned off plugins at random.
What Numbers Are Normal?
There is no single number that is right for every site, but these rough guides help you decide where to look.
| Measure | Often fine | Worth a look |
|---|---|---|
| Page generation time on an uncached page | Under one second | Over two seconds |
| Database queries on a simple page | A few dozen | Several hundred |
| Slow queries flagged | None | Any that repeat on every page |
| Peak memory use | Well under your memory limit | Close to the limit |
| Outside HTTP calls | Few, and fast | Many, or any that take more than a second |
| PHP errors on a normal page | None | Repeated warnings |
A shop or a membership site runs more queries than a blog, and that is normal. What matters is a sudden change, or a single component that dominates the numbers.
Cached Pages and What You See
A page cache serves finished pages without running WordPress, so Query Monitor does not show anything for a cached page. To test, log in as an administrator, since logged-in users are often not served cached pages, or add a test parameter to the address, or clear the cache and load the page once.
Remember what you are measuring. Query Monitor shows the cost of building a page when the cache is empty. That cost matters on the first visit after a cache clear, for logged-in users, for the checkout and cart, and for the dashboard. It does not show what most cached visitors experience. Use a browser speed test to see that side. If you are choosing a cache, see our comparison of LiteSpeed Cache vs WP Rocket.
Object Caching and Repeated Queries
When you see the same query many times, an object cache may help. An object cache, such as Redis or Memcached, stores the results of queries in memory, so that WordPress does not ask the database again.
- Ask your host whether an object cache is available.
- Install the matching plugin, and turn it on.
- Run Query Monitor again, and check that the number of queries drops.
- Test your site thoroughly, since a cache can show old data if it is set up wrongly.
An object cache is not a cure for a badly written plugin, but it can reduce the cost of a plugin that you cannot replace.
Using Query Monitor in the Admin Area
Many site owners only test the front end, but the dashboard can be slow too.
- Open the post editor, the plugins page, and the media library, and check the numbers.
- A plugin that runs checks or remote calls on every dashboard page can slow your work.
- Look at the HTTP API panel in the dashboard. Update checks, license checks, and news feeds from plugins can make remote calls that delay the page.
- If the dashboard is slow but the front end is fast, the cause is often one plugin with heavy admin code.
A fast dashboard saves you time each day, so it is worth the check.
Security and Privacy Notes
Query Monitor shows technical details that you would not want to share.
- It can show database queries that contain user names or email addresses.
- It shows file paths and server details.
- Limit access to trusted administrators.
- Do not post screenshots of the panel in public forums without hiding private values.
- Remove the plugin from sites where you no longer need it.
- Keep it updated while it is active, since any plugin can have security fixes.
If you give access to a developer, remove their account when the work ends.
Common Mistakes When Using Query Monitor
- Testing on a cached page and seeing nothing.
- Blaming the plugin with the most queries without checking the time. Many fast queries can be less costly than one slow one.
- Ignoring core. If core takes most of the time, the problem may be the server.
- Leaving the plugin active on a live site for months.
- Fixing a small problem and missing a large one. Start with the biggest component.
- Making several changes at once, and not knowing which one helped.
- Forgetting to test the front end with a browser speed tool.
- Not taking a backup before turning plugins off.
When the Problem Is Not a Plugin
Sometimes Query Monitor shows that no plugin is to blame.
- If core and the theme use most of the time, the server may be too slow. Check your hosting plan and PHP version.
- If the database time is high for all components, the database server may be overloaded or too small.
- If outside HTTP calls dominate, the cause is a service that your site calls, which you may need to remove or cache.
- If the page generation time is low but the page still feels slow, the cause is in the browser: images, scripts, fonts, or layout shifts.
In these cases, move to the fixes for hosting, images, and scripts in our speed guides, and use Query Monitor again afterward to confirm the gain.
How Often Should You Run These Tests?
You do not need Query Monitor active all the time. Use it at set moments.
- After you install or update a large plugin, such as a shop, a page builder, or a membership tool.
- When a page or the dashboard feels slower than before.
- Before you choose between two plugins that do the same job, to compare their cost.
- Once or twice a year, as a health check on a busy site.
- When your host warns you about resource use.
Keep a small log with the date, the page, the generation time, the number of queries, and the heaviest component. Over time, this record shows you which changes helped and which made things worse.
Frequently Asked Questions (FAQs)
Is Query Monitor free?
Yes. It is a free, open source plugin.
Can Query Monitor tell me which plugin is slow?
Yes. It groups queries and time by component, so you can see which plugin, theme, or core part is responsible.
Does Query Monitor slow down my site?
A little, while it is active. Use it for tests, and turn it off when you finish.
Who can see Query Monitor’s output?
By default, administrators on single sites and super admins on multisite networks. Check the settings if you want to change this.
Is it safe to use on a live site?
It is usually used on staging. If you use it on a live site, do it for a short time, keep access limited, and take a backup first.
Do I need to know code to use it?
No for the main panels. Reading the component view and the slow query flags does not need code.
What does a slow query mean?
A query that takes a long time to run. It may come from a large table, a missing index, or a heavy plugin.
Can it fix the problem for me?
No. It shows the cause. You then update, replace, or reconfigure the plugin, or ask the author for a fix.
Can someone use it to find my slow plugins for me?
Yes. If you prefer an experienced person to run the tests and fix the cause, you can get WordPress management help through this Fiverr gig.
Final Thoughts
Query Monitor turns a guessing game into a clear list. It shows which plugins run the most queries, which queries are slow, which hooks and outside calls waste time, and which code throws errors.
Use it on a staging copy, read the component view first, test one change at a time, and measure again. Then remove it, and combine its findings with a browser speed test. With that method, finding a slow plugin takes minutes instead of days.

