The Complete WooCommerce Query Monitor Guide 2026
Query Monitor is the essential WooCommerce debugging tool — see slow database queries, hooks fired, HTTP API calls, PHP errors and template loads to find what is slowing your store.
WooCommerce Query Monitor — the Query Monitor plugin used on a WooCommerce store — is the developer’s first tool for diagnosing why a store is slow. It surfaces every database query on a page (flagging slow and duplicate ones), every hook fired, every HTTP API call WooCommerce makes, PHP errors and notices, and which templates loaded. When a WooCommerce page is sluggish, WooCommerce Query Monitor tells you exactly where the time and queries went, turning guesswork into evidence. This guide is the debugging workflow.
Search intent: informational/procedural — WooCommerce developers debugging performance and behaviour. We cover what WooCommerce Query Monitor shows, finding slow queries, hooks and HTTP calls, isolating the culprit plugin, production cautions, and a debugging workflow. It pairs with our WooCommerce performance and Redis caching guides.
WooCommerce Query Monitor: Finding Slow Queries
The headline use of WooCommerce Query Monitor is the Database Queries panel. It lists every SQL query the page ran, the time each took, and — crucially — which component (core, theme, or a specific plugin) triggered it, flagging slow queries and duplicates in red. On a slow WooCommerce page, WooCommerce Query Monitor immediately shows whether the problem is a handful of expensive queries or hundreds of small ones, and points at the culprit by plugin. The “Queries by Component” view is the fastest way to see that, say, a reviews plugin is firing 400 queries on every product page. This is evidence you cannot get from intuition.
WooCommerce Query Monitor: Hooks, HTTP Calls and Errors
Beyond SQL, WooCommerce Query Monitor exposes the rest of the request. The Hooks panel shows every action and filter fired and what is hooked to them — invaluable for understanding WooCommerce’s execution order and why a customisation runs (or does not). The HTTP API Calls panel is especially important for WooCommerce: it shows every outbound request (payment gateways, shipping rate lookups, license checks, analytics) with timing — a slow synchronous HTTP call during page load is a frequent, hidden cause of slow TTFB that WooCommerce Query Monitor makes obvious. It also surfaces PHP errors and notices (often hidden in production — see WordPress debugging), template loads, and the memory and time the request consumed. The Query Monitor site and plugin page document every panel.
| Panel | What it reveals | Use it to |
|---|---|---|
| Database Queries | Every SQL query, time, component | Find slow / duplicate queries |
| Queries by Component | Which plugin caused queries | Identify the culprit plugin |
| Hooks & Actions | What fired and what is hooked | Debug execution order |
| HTTP API Calls | Outbound requests + timing | Catch slow synchronous calls |
| PHP Errors | Hidden warnings + notices | Surface silent bugs |
WooCommerce Query Monitor: Production Caution and Workflow
One firm rule: WooCommerce Query Monitor is a development and staging tool, not something to leave active for all visitors in production — it adds overhead and can expose internal details. Run it on staging, or restrict its output to logged-in administrators if you must use it on a live site, and disable it when done. The practical WooCommerce Query Monitor workflow: reproduce the slow page, open the Database Queries and Queries by Component panels to find the heaviest contributor, check HTTP API Calls for slow synchronous requests, confirm with the Hooks panel which code is involved, then fix the specific plugin, query or call — and re-measure. Used this way, WooCommerce Query Monitor turns “the site feels slow” into a precise, fixable diagnosis. Our WooCommerce performance team uses it on every audit.
How we use Query Monitor on WooCommerce audits
Queries by Component is where we start every audit. It instantly names the plugin responsible for the most queries. More often than not, a single poorly-built plugin firing hundreds of queries per page is the whole performance problem — Query Monitor finds it in seconds, where guessing would take hours.
The HTTP API Calls panel catches the invisible killer. A synchronous outbound call — a shipping rate API, a license check — blocking page render is a classic WooCommerce slowdown that nothing else surfaces clearly. We check this panel on every slow-TTFB investigation; it has solved cases that looked like database problems.
Never leave it on in production. We have inherited sites running Query Monitor live for everyone, adding overhead to every request. It is a staging/admin-only tool. We use it to diagnose, fix the finding, then disable it — it is a scalpel, not a permanent fixture.
Frequently Asked Questions About WooCommerce Query Monitor
What is Query Monitor for WooCommerce?
Query Monitor is a free developer debugging plugin that, on a WooCommerce store, surfaces every database query, hook fired, HTTP API call, PHP error and template load on a page. WooCommerce Query Monitor is the first tool for diagnosing why a store is slow, showing exactly where time and queries are spent.
How do I find slow queries in WooCommerce?
Use Query Monitor’s Database Queries panel, which lists every SQL query, its time, and the component that triggered it, flagging slow and duplicate queries. The Queries by Component view then names the responsible plugin. This is the fastest way WooCommerce Query Monitor pinpoints what is making a page slow.
Can Query Monitor show which plugin is slowing my store?
Yes. The Queries by Component panel groups database queries by the plugin, theme or core code that caused them, so you can see at a glance that, for example, a reviews plugin fires hundreds of queries per product page. This makes WooCommerce Query Monitor the quickest way to identify a culprit plugin.
Does Query Monitor show HTTP API calls?
Yes, and for WooCommerce this is vital. The HTTP API Calls panel lists every outbound request — payment gateways, shipping rate lookups, license checks — with timing. A slow synchronous call during page load is a common hidden cause of poor TTFB, and WooCommerce Query Monitor makes it immediately visible.
Is it safe to run Query Monitor in production?
Not for all visitors. WooCommerce Query Monitor adds overhead and can expose internal details, so it is a development and staging tool. If you must use it live, restrict its output to logged-in administrators and disable it when finished. Never leave it active for every production visitor.
Is Query Monitor free?
Yes, Query Monitor is a free, open-source plugin on the WordPress.org repository. It works on any WordPress site and is especially valuable on WooCommerce, where database query volume and HTTP API calls are high. WooCommerce Query Monitor is an essential, no-cost addition to any developer’s toolkit.
WooCommerce Store Running Slow?
Our team runs Query Monitor-driven performance audits — finding the slow queries, calls and plugins behind it.
