Query Monitor for WordPress

Query Monitor and DebugHawk: when to use each

Query Monitor is one of the most useful plugins in WordPress development. Load a page as an administrator and it shows every database query, hook and HTTP request behind it.

But a slowdown often happens on a visit you never see: a busy afternoon, a logged-out shopper, a phone on a slow connection. DebugHawk records performance from every visitor over time, so you can find those moments, then dig in with Query Monitor.

Last updated

Credit where it's due

What Query Monitor does well

The gap

The Query Monitor gap

1

Your requests only

Query Monitor shows the request you are making. By default only administrators see its output, and visitor requests aren't recorded.

2

No history

Data covers the current page load. When you reload, it's replaced, so trends over days or weeks are out of scope.

3

Server side only

It reports what happens in PHP. How the page then renders in a visitor's browser, Core Web Vitals included, isn't measured.

4

One site at a time

Each site has its own install, with no overview across the sites you manage.

The difference

What DebugHawk adds

1

Every visitor

DebugHawk records requests from real visitors, logged in or not, so you see slowdowns you never triggered yourself.

2

History and trends

Look back over days or weeks to see when a slowdown started and which pages it hit.

3

Front end and back end

Core Web Vitals from real browsers sit next to PHP time, database time, slow queries and external requests.

4

All your sites in one place

An overview ranks every site you manage, and a share link lets each client see their own report.

Side by side

Query Monitor and DebugHawk compared

Attribute Query Monitor DebugHawk
Whose requests Yours, as an administrator or with its authentication cookie Every visitor, in full or sampled
History Current request only 30 to 90 days on paid plans
Database queries Every query on the request, with its caller Query count and time for every request, plus full details of slow queries
Hooks and PHP errors Yes, in detail Not covered
Ajax, REST API and cron Ajax and REST API requests Not covered, page loads in the browser only
Frontend performance Not measured LCP, INP, CLS, FCP and TTFB from real browsers
Multiple sites One install per site One dashboard for every site
Client reports Not included Live share links
Price Free Free for one site, paid plans from $29/month
Get started for free

No credit card required

Use cases

Which tool for which job

When to use Query Monitor

  • Debugging a page while you build it
  • Inspecting hooks and every query on one request
  • Checking a fix before you deploy

When to use DebugHawk

  • Finding slowdowns that happen when you aren't looking
  • Seeing which pages and plugins are slowest across all visits
  • Showing clients how their site performs

When to use both

  • DebugHawk shows which page and plugin to look at
  • Query Monitor shows the full detail of that request
  • DebugHawk confirms the fix worked for real visitors

How to use the Query Monitor plugin

Install Query Monitor from the WordPress plugin directory and activate it. It adds a menu to the admin toolbar with an overview of the current page.

Select an item in that menu to open its panel. The database queries panel flags slow, duplicate and failed queries, and filters them by query type, by the plugin, theme or core component responsible, and by calling function. That is the quickest way to see which plugin is behind the queries on a page.

Only administrators see Query Monitor by default. To see its output while logged out, set its authentication cookie in the Query Monitor settings panel.

Query Monitor shows one request at a time. To find which pages are slow for real visitors, start with DebugHawk, then open the slowest page with Query Monitor to see the full detail.

Query Monitor vs Debug Bar

Debug Bar is a free debugging plugin from WordPress.org. It adds a debug menu to the admin bar with query, cache and other debugging information. It lists database queries when SAVEQUERIES is enabled in wp-config.php, and PHP warnings and notices when WP_DEBUG is on. Add-on plugins extend it with more panels.

Query Monitor shows more without add-ons, including queries grouped by plugin or theme, hooks and actions, HTTP API calls, and support for block themes.

Both show the request you are making. Neither records your visitors' page loads or keeps a history, which is what DebugHawk adds.

Getting started

Up and running in a few minutes

No server access or agents to install. Follow the setup guide or start here.

1
Create a free account
Sign up without a credit card. The free plan monitors one site with every feature.
2
Install the plugin
Add DebugHawk from the WordPress plugin directory, on any host.
3
Add your snippet
Paste your endpoint and secret into wp-config.php. Data arrives from the next visit.

Questions, answered

Yes. They do different jobs and work alongside each other. Many developers use DebugHawk to find where to look, then Query Monitor to inspect that request in detail.
Query Monitor is a debugging panel: it shows everything about the request you are making right now. DebugHawk is performance monitoring: it records every visitor's page loads over days and weeks, front end and back end, across all your sites.
DebugHawk records the query count and database time for every request, and captures the full details of queries slower than your threshold, 50ms by default. You can change the threshold and how many are captured per request in wp-config.php.
Yes. Admin pages are monitored by default, which helps when the WordPress admin feels slow. You can turn this off with the trace_admin_pages setting.
The plugin is lightweight and collects data from real visits without heavy server agents. On high-traffic sites you can also sample a percentage of requests.

Ready to take flight? Stop losing hours to performance debugging

Join WordPress professionals who've reclaimed their time and delighted their clients with faster sites.

Get started for free Or explore the live demo first