The best choice is usually both: Query Monitor for quick WordPress admin debugging, and New Relic for server-wide performance tracing over time. Query Monitor is free, runs inside WordPress, and has more than 200,000 active installations on WordPress.org [source: WordPress.org]. New Relic is stronger when a slow admin screen is caused by PHP workers, database load, cron jobs, external APIs, or hosting limits.
TLDR: Query Monitor is better for finding the exact plugin, query, hook, or template part slowing down a WordPress admin page. New Relic is better for proving whether the real bottleneck sits in PHP, MySQL, Redis, external services, or server resources. In one common WooCommerce case, an orders screen taking 8.4 seconds may show 412 duplicate database queries in Query Monitor, while New Relic may show that a shipping API call adds 2.1 seconds on every request. A serious team should use Query Monitor first, then confirm the wider cause in New Relic.
Why WordPress Admin Performance Gets So Bad
WordPress admin slowdowns are often more annoying than front-end issues because they block real work. Editors wait to save posts. Store managers wait to load orders. Developers stare at a white screen and wonder which plugin decided to ruin the afternoon.
Admin pages are heavy by nature. They load plugins, user permissions, dashboard widgets, update checks, AJAX calls, custom fields, reports, and background tasks. A front-end cache may make public pages feel fast, while wp-admin still crawls. That is why normal speed tests often miss the real problem.
The main bottlenecks usually fall into a few groups:
- Slow database queries, especially on orders, users, products, and post meta tables.
- Too many duplicate queries from plugins asking for the same data again and again.
- Heavy hooks attached to admin actions.
- External API calls to payment, shipping, license, CRM, or analytics services.
- Low PHP worker limits or weak database resources.
- Bad cron behavior that runs during admin requests.
Query Monitor: Best for Fast WordPress-Level Clues
Query Monitor is a developer tool that appears in the WordPress admin bar. It shows what happened during the current page load. That includes database queries, PHP errors, hooks, scripts, styles, HTTP API calls, REST API requests, block editor activity, and more.
Its biggest strength is context. If an admin page takes five seconds to load, Query Monitor can show whether one plugin caused 280 queries, whether a theme function triggered an error, or whether a remote request stalled for 900 milliseconds.
For WordPress admin performance, Query Monitor is especially useful for:
- Finding slow queries and seeing which component created them.
- Spotting duplicate queries that repeat without good reason.
- Checking HTTP API calls that contact outside services.
- Reviewing hooks and actions that fire on admin screens.
- Finding PHP warnings and notices that point to sloppy plugin code.
Honestly, it feels like Query Monitor saves the first hour of guessing. Instead of disabling 20 plugins one by one, a developer can load the slow screen and see that one reporting plugin added 7,000 ms of database time.
Its weakness is scope. Query Monitor only shows the current request. It does not build a long-term picture across all users, all requests, and all server processes. It also adds overhead, so it should not be left visible for everyone on a busy production site.
New Relic: Best for Full Application Tracing
New Relic APM watches the application from a higher level. It tracks transactions, response times, database calls, external services, errors, throughput, and host behavior. It can show patterns across minutes, days, or weeks.
This matters when the site owner says, “The admin is slow sometimes.” Query Monitor is great when the problem can be reproduced. New Relic is better when the issue appears during traffic spikes, background jobs, imports, or checkout surges.
New Relic can help identify:
- Slow PHP transactions, such as
/wp-admin/edit.phporadmin-ajax.php. - Database pressure, including slow MySQL calls and high query time.
- External services that delay admin requests.
- Error rates tied to plugins, payment systems, or custom code.
- Resource problems, such as memory pressure or saturated PHP workers.
New Relic’s transaction traces are the real prize. A trace can show that a slow WooCommerce admin request spent 42% of its time in MySQL, 31% waiting on an external tax service, and 18% inside plugin code. That kind of split is hard to get from WordPress alone. New Relic explains its APM transaction tracing in its own documentation [source: New Relic].
The annoying part is setup. New Relic often needs server access, an agent install, license keys, and configuration. On managed hosting, the team may need host support. Expect to waste time on permissions if the hosting panel hides the useful settings.
Query Monitor vs New Relic: Which Finds Bottlenecks Faster?
For a single slow admin page, Query Monitor usually wins. It gives immediate WordPress-specific detail. A developer can inspect a slow product edit screen and quickly see plugin names, query counts, hooks, and remote calls.
For recurring or unclear slowdowns, New Relic wins. It shows trends and confirms whether the bottleneck is inside WordPress, the database, the server, or an outside service. It also helps prove the problem to a host, plugin vendor, or internal team.
| Need | Better Tool |
|---|---|
| Find which plugin runs a slow query | Query Monitor |
| Analyze admin performance over several days | New Relic |
| See duplicate queries on one request | Query Monitor |
| Track PHP workers, MySQL time, and external APIs | New Relic |
| Debug without server access | Query Monitor |
| Investigate random admin slowdowns | New Relic |
A Practical Workflow That Works
A smart debugging process starts small and then widens.
- Reproduce the slow admin screen. The team should record the URL, user role, time, and action.
- Open Query Monitor. It should check total queries, slow queries, duplicate queries, HTTP calls, hooks, PHP errors, and memory usage.
- Identify the likely component. If one plugin creates 70% of query time, it becomes the first suspect.
- Confirm in New Relic. The team should check whether the same transaction is slow across many requests.
- Fix and measure again. A real fix should reduce request time, query count, memory use, or external wait time.
An example is simple. A membership site has a user list that loads in 11 seconds. Query Monitor shows a custom CRM plugin creating 1,200 meta queries. New Relic then confirms that /wp-admin/users.php is the slowest admin transaction from 9 a.m. to 11 a.m. After indexing and plugin changes, the page drops to 2.6 seconds. That is a fix worth keeping.
When Query Monitor Is Enough
Query Monitor may be all a small site needs if the issue is easy to reproduce. It is ideal for staging sites, plugin audits, theme changes, and debugging new features. It also helps agencies give quick evidence to clients without installing server agents.
It is not enough when slowdowns appear randomly, during traffic spikes, or only for certain background processes. It also cannot replace server monitoring.
When New Relic Is Worth It
New Relic is worth it for WooCommerce stores, membership sites, LMS platforms, publishers, and any company where admin delays cost money. If staff members lose 10 seconds on 300 order actions per day, that is nearly 50 minutes of wasted admin time daily.
New Relic also helps when a host says “the server looks fine.” Instead of arguing, the team can show transaction traces, database timing, and external call delays.
FAQ
Is Query Monitor better than New Relic for WordPress?
Query Monitor is better for WordPress-specific debugging on a single request. New Relic is better for long-term tracing, server behavior, and production patterns.
Can Query Monitor slow down WordPress admin?
Yes, it can add overhead. It should be used by administrators or developers, not exposed to regular users on busy production sites.
Does New Relic show which WordPress plugin is slow?
Sometimes. It may show PHP functions, database activity, and transaction traces. Query Monitor is usually clearer when the goal is to name the plugin or hook.
Which tool should a WooCommerce store use?
A WooCommerce store should use both if possible. Query Monitor helps inspect slow orders, products, and reports. New Relic shows whether checkout, cron, admin AJAX, or external APIs are causing wider delays.
What is the first metric to check in WordPress admin?
The first metric should be total page generation time. After that, the team should check database query time, query count, memory usage, and external HTTP calls.
Can these tools fix performance issues automatically?
No. They find evidence. A developer still needs to remove bad queries, replace heavy plugins, add indexes, tune hosting, reduce external calls, or improve custom code.