Our Complete Review of Query Monitor for WordPress
Every WordPress developer eventually faces the challenge of debugging a site to fix errors or slow queries. You might encounter a PHP warning, a database bottleneck, or an issue with a specific plugin. Query Monitor is a debugging plugin that provides deep visibility into your site operations.
In this review, I’ll take a close look at how it works, test its database query features, and help you decide if this free plugin is worth it over a premium alternative.
Query Monitor Quick Links
- What is Query Monitor?
- Interface and Ease of Use
- Error Tracking and Capabilities
- Database Query Performance and Insights
- Site Monitoring and Proactive Alerts
- Security
- Performance Impact
- Query Monitor Limitations and Shortcomings
- Pricing
- What Real Users Say About Query Monitor
- Is Query Monitor Worth Using?
What is Query Monitor?
Query Monitor is a free debugging plugin for WordPress that lets you track every database query, PHP error, and HTTP request during a page load. It’s a widely popular plugin among developers who need deep visibility into their site’s server-side operations.
The plugin comes with a component attribution feature that maps every query and error to its exact source, whether it was triggered by WordPress core, a specific theme, or an individual plugin. This makes it incredibly easy to pinpoint exactly which extension is causing a performance issue or triggering an error.
I tested Query Monitor by installing it on a WooCommerce staging site. I checked how it tracks database queries during a standard page load and verified the component attribution accuracy. I also tested its ability to identify slow queries and duplicate patterns in a custom theme loop.
I examined the interface by navigating through the admin toolbar overlay and tested the HTTP API call tracking feature with an external payment gateway. I checked how the plugin handles AJAX debugging and verified its behavior during a simulated plugin conflict. I also monitored the performance overhead while the plugin was active.
Interface and Ease of Use
Once activated, Query Monitor doesn’t require any configuration and becomes accessible without requiring you to navigate to a separate settings page. The plugin adds a diagnostic dropdown menu directly into your WordPress admin toolbar. I found that this integration makes it incredibly convenient to access debugging data while browsing any page on your site.
The admin toolbar displays four key metrics for the current page load. The color-coded status indicators change the toolbar background to red, orange, or brown when issues are detected. This provides an instant visual alert without needing to open the main panel.
If you hover over the toolbar metrics, it reveals a dropdown menu of specific diagnostic categories. Clicking on any item opens the main diagnostic overlay panel. While Query Monitor’s panel docks at the bottom of your browser by default, you can switch it to a sidebar layout or resize it if you want.
The left-hand navigation inside the panel organizes all diagnostic data into specific tabs. I found that navigating between these tabs can be confusing, given the large amount of data it displays.
It gives you some customization options. You can adjust the color scheme and configure your preferred code editor so that file paths in stack traces become clickable links.
Error Tracking and Log Management
Query Monitor provides real-time PHP error reporting without manually parsing through server log files. It catches PHP errors, warnings, notices, and deprecation messages as they happen. Each error is formatted in a table alongside its call stack and the specific component responsible for triggering it.
Query Monitor also includes an HTTP API call tracking monitor for all server-side HTTP requests your site makes to external services. This includes payment gateways, social media APIs, and other third-party integrations. The plugin shows response codes, timeouts, and execution times, which are critical for finding invisible bottlenecks caused by slow external servers.
It also provides hooks and actions inspection, which gives a definitive log of every hook fired during a request. I found that it includes the priority, the callback function, and the component that registered it. This helps resolve plugin conflicts and execution order issues that are otherwise difficult to track down.
Query Monitor tracks page generation time, peak memory usage, and provides a comprehensive summary of your server environment. It also alerts you if a persistent object cache is missing. This is particularly useful for identifying optimization opportunities related to server configuration.
It is also capable of debugging AJAX calls and REST API requests. It does this by appending diagnostic data directly into HTTP response headers. This makes it a unique plugin for troubleshooting background processes that do not trigger a browser refresh.
Database Query Performance and Insights
Query Monitor tracks every SQL query executed during a page load, and highlights slow, duplicate, or erroneous queries to help you identify problematic database interactions immediately.
Its component attribution feature analyzes the PHP call stack to map every query to its exact source. This automatically identifies if a query was triggered by WordPress core, a specific theme, or an individual plugin. I found that you can see the total time and query count for each component by using the Queries by Component panel, which groups all database requests by their source.
There are several ways to drill down into your data as well. You can sort queries by row count to find memory hogs returning thousands of rows. You can also expand the call stack to see the exact file and line of code that triggered each query. This level of detail helps pinpoint the root cause of performance issues.
The plugin includes dedicated support for WooCommerce. This allows developers to monitor complex WooCommerce processes like product archives, cart calculations, and checkout flows. I found that this makes it particularly valuable for developers working on eCommerce sites.
Site Monitoring and Proactive Alerts
Query Monitor does not include site monitoring and alert features. It provides in-the-moment debugging for the current page load only. It does not send email notifications when errors occur or when your site goes down. For users who need automated alerts and crash recovery, I’ll recommend a premium plugin like WP Debug Toolkit.
Security
Query Monitor includes several security features to protect debugging data. By default, the plugin restricts output to administrators only on single-site installations and Super Admins on multisite networks. This prevents non-technical users from accessing sensitive diagnostic information.
You can also set an authentication cookie through the plugin’s settings. This allows you to view the debugging interface while logged out or viewing the site as a non-admin user. This is particularly useful for debugging the frontend experience for customers on ecommerce sites.
Performance Impact
Query Monitor adds between 10 and 100 milliseconds to page generation time and increases PHP memory consumption by about 10%. This overhead occurs because the plugin actively monitors every aspect of a page load and captures extensive data like full stack traces for every database query.
On pages that run hundreds of queries, the memory usage can become noticeably high. You can consider disabling Query Monitor after you finish actively auditing a site as it’s generally not recommended to leave it running on live production sites with high traffic.
Query Monitor Limitations and Shortcomings
Query Monitor provides real-time data for the current page load only. It does not log historical trends or save previous data. This makes it difficult to track down rare, intermittent bugs or invisible background processes like scheduled WP-Cron tasks. The plugin also adds performance overhead if you leave it running on live, high-traffic production sites.
The plugin is deeply integrated into the WordPress execution lifecycle. If your site experiences a fatal PHP error or completely crashes, the Query Monitor panel becomes inaccessible. This is a significant limitation when you need debugging data the most during a site emergency.
Another area where it falls short is that the interface relies on very small font sizes to fit a massive amount of data on the screen. This makes the plugin difficult to navigate for users with visual impairments. The steep learning curve and dense technical data can also be overwhelming for beginners or non-technical users.
How It Compares to Other Debugging Plugins
If you are trying to decide which debugging plugin is best for your development workflow, it can be helpful to see how Query Monitor compares against alternatives.
We have written a detailed WP Debug Toolkit vs Query Monitor comparison article that breaks down the differences in features, site recovery, and proactive monitoring.
Pricing
Query Monitor is a 100% free and open-source plugin. You can download it directly from the official WordPress plugin repository without any paid licenses or premium upgrades. Unlike many WordPress debugging plugins that operate on a freemium model, Query Monitor provides its entire suite of features without requiring any payment.
What Real Users Say About Query Monitor
Query Monitor is a free, open-source plugin, so the best place to look for feedback is the official WordPress plugin repository, where it maintains an impressive 4.9 out of 5 stars based on 463 reviews.
If you read through these reviews, you’ll observe that users are particularly satisfied with the depth of diagnostic information and the component attribution feature.
One user shares that it is “Must have for development,” adding that their favorite features are profiling, logging, and the newly added assertions. Another reviewer echoes the same sentiment, stating it is “Saved my time a hundred times.”
Many developers also appreciate the WooCommerce-specific support. I found that users frequently mention how valuable it is for tracking complex ecommerce processes. The plugin’s ability to identify slow queries and provide stack traces is consistently highlighted as a standout feature that saves hours of troubleshooting time.
Final Verdict: Is Query Monitor Worth Using?
I believe Query Monitor is an essential plugin for every WordPress developer working in a local or staging environment. It provides depth data in debugging database queries, PHP errors, and HTTP requests during active development. The component attribution alone makes it invaluable for identifying which plugin is causing issues.
However, Query Monitor is not recommended for production site monitoring. Its performance overhead and lack of historical tracking make it less suitable for live sites. If you manage client sites and need crash resilience, proactive email alerts, and persistent logging, a premium solution like WP Debug Toolkit is worth the investment. For in-moment debugging during development, Query Monitor remains the standard.
Common Questions About Query Monitor
How to use Query Monitor in WordPress?
Using Query Monitor is straightforward once it is installed and activated. You will see a summary block in your admin toolbar showing page generation time and database queries. Simply hover over this block to reveal a dropdown menu, or click on it to open the diagnostic overlay panel. From there, you can navigate tabs to inspect database queries, PHP errors, and API calls.
What is the best analytics plugin for WordPress?
AnalyticsWP is the best analytics plugin for most WordPress sites. Many external analytics tools add unnecessary bloat, which hurts both performance and privacy. AnalyticsWP is native to WordPress and keeps all data locally on your server. It offers superior WooCommerce integration by automatically tracking the entire customer journey without the data gaps caused by ad blockers. You also get accurate, privacy-compliant insights without sacrificing site speed.
What does debug logging do?
Debug logging creates a file on your server that records PHP errors, warnings, and notices while your site is running. Instead of displaying these errors to visitors, they are captured in a background file. This is essential for troubleshooting because it allows you to review site issues chronologically without interrupting the user experience.
Query Monitor — Further Reading
