Query Monitor


Query Monitor is the developer tools panel for WordPress. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.

It includes some advanced features such as debugging of Ajax calls, REST API calls, and user capability checks. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.

Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.

Для дополнительной информации посетите сайт Query Monitor.

Here’s an overview of what’s shown for each page load:

  • Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (SELECT, UPDATE, DELETE, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.
  • The template filename, the complete template hierarchy, and names of all template parts used.
  • PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.
  • Blocks and associated properties in post content when using WordPress 5.0+ or the Gutenberg plugin.
  • Matched rewrite rules, associated query strings, and query vars.
  • Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.
  • Language settings and loaded translation files (MO files) for each text domain.
  • HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.
  • User capability checks, along with the result and any parameters passed to the capability check.
  • Environment information, including detailed information about PHP, the database, WordPress, and the web server.
  • The values of all WordPress conditional functions such as is_single(), is_home(), etc.
  • Transients that were updated.

In addition:

  • Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.
  • The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.
  • The response from an authenticated WordPress REST API request will contain various debugging information in its headers, as long as the authenticated user has permission to view Query Monitor’s output.

By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.

In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.

Заявление о конфиденциальности

Query Monitor не хранит постоянно какие-либо данные, которые он собирает. Плагин не отправляет данные третьим лицам и не включает какие-либо сторонние ресурсы.

Полный текст политики конфиденциальности Query Monitor можно найти здесь.


  • The admin toolbar menu showing an overview
  • Aggregate database queries by component
  • User capability checks with an active filter
  • Database queries complete with filter controls
  • Hooks and actions
  • HTTP requests (showing an HTTP error)
  • Aggregate database queries grouped by calling function

Часто задаваемые вопросы

Who can see Query Monitor’s output?

By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.

In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.

Does Query Monitor itself impact the page generation time or memory usage?

Short answer: Yes, but only a little.

Развернутый ответ: Query Monitor слабо влияет на генерацию страницу за счет использования хуков WordPress таким же образом, как это делают другие плагины. Воздействие низкое, обычно 10-100 мс в зависимости от структуры вашего сайта.

Использование памяти плагином Query Monitor как правило составляет около 10% от общего объема памяти, необходимого для генерации страницы.

Are there any add-on plugins for Query Monitor?

A list of add-on plugins for Query Monitor can be found here.

In addition, Query Monitor transparently supports add-ons for the Debug Bar plugin. If you have any Debug Bar add-ons installed, just deactivate Debug Bar and the add-ons will show up in Query Monitor’s menu.

Where can I suggest a new feature or report a bug?

Please use the issue tracker on Query Monitor’s GitHub repo as it’s easier to keep track of issues there, rather than on the wordpress.org support forums.

Is Query Monitor available on WordPress.com VIP Go?

Yep! You just need to add define( 'WPCOM_VIP_QM_ENABLE', true ); to your vip-config/vip-config.php file.

I’m using multiple instances of `wpdb`. How do I get my additional instances to show up in Query Monitor?

You’ll need to hook into the qm/collect/db_objects filter and add an item to the array with your connection name as the key and the wpdb instance as the value. Your wpdb instance will then show up as a separate panel, and the query time and query count will show up separately in the admin toolbar menu. Aggregate information (queries by caller and component) will not be separated.

Do you accept donations?

No, I do not accept donations. If you like the plugin, I’d love for you to leave a review. Tell all your friends about the plugin too!


I wish I had used this plugin first!

My site was hanging, but I didn't know why... I consider myself somewhat WordPress-savvy and thought I could pinpoint the exact plugin conflict problem by deactivating one plugin at a time. Though I was able to narrow it down to two plugins, I didn't know why the problem was occurring. Using different plugins was not a feasible option for me to remedy the conflict. Query Monitor brought to my attention that one of the plugins was doing multiple callbacks to an external URL for logging purposes. Once I realized that, I removed my API Key login information so that logging wouldn't take place. Now my site is running fine! Thanks for an amazing plugin! This will be my go-to for future plugin troubleshooting.

Essential if you have lots of Plugins

Query Monitor is essential if you run lots of plugins, or develop code. It shows any problems immediately, so you can keep everything running smoothly.

A WordPress Must Have

This plugin helps identify problems and plugins that are slowing your site down quickly and easily. This is a must-have for any site developer on WordPress

Reveals so much — excellent!

Thanks for a great plugin. It seems to reveal everything that's going on under the hood and how long everything takes. It's just a pity it can't magically make everything faster for me too!
Посмотреть все 288 отзывов

Участники и разработчики

«Query Monitor» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:


«Query Monitor» переведён на 11 языков. Благодарим переводчиков за их работу.

Перевести «Query Monitor» на ваш язык.

Заинтересованы в разработке?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Журнал изменений

For Query Monitor’s changelog, please see the Releases page on GitHub.