Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesQuery Monitor helps you explain a slow or broken WordPress request by showing what happened during that request: page-generation time, memory use, database queries, PHP errors, hooks, templates, scripts, styles, and outbound HTTP calls. It is most useful when you reproduce the exact slow page, dashboard action, AJAX request, or REST request and then read the panels for that single request.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Use it as an attribution and investigation tool, not as a verdict that a plugin is inherently defective. Work on staging when possible, change one variable at a time, and remove or restrict debugging access when you finish.
As an Amazon Associate I earn from qualifying purchases.
What Query Monitor can and cannot tell you
Query Monitor is a free, open-source WordPress debugging plugin. It instruments the current request and adds its findings to the WordPress toolbar for an authorized user. The toolbar summary reports four immediate measurements: page-generation time in seconds, peak memory usage, total SQL-query time in seconds, and total SQL-query count.
The scope is deliberately narrow. Query Monitor does not provide a historical performance database. A report belongs to the request that has just completed, so an earlier page load cannot be compared with a later one unless you repeat the same request and record both results yourself. This also means that a home page, an editor screen, an AJAX action, a REST endpoint, and a redirect must each be reproduced as separate requests.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Use a controlled test, not a hunch
A plugin name beside a slow query is a lead for code review. It is not proof that the plugin alone caused the delay. A query may be slow because of the data set, missing indexes, another component changing the query, a remote service, cache state, or the server itself. Confirm the finding by repeating the request with one controlled change, preferably on a staging copy with a rollback plan.
Install Query Monitor and capture the right request
Check the supported environment
The WordPress.org listing captured on 20 June 2026 recorded Query Monitor 4.0.7, more than 200,000 active installations, WordPress 6.2 or later, and PHP 7.4 or later. The listing reported testing through WordPress 7.0.7 at that time. Plugin and WordPress requirements change, so verify the current listing before installing or upgrading.
Free tools Windows power users keep installed
One-click scans. No signup required.
Installation choices
- On a staging site, open Plugins → Add New in the WordPress dashboard.
- Search for Query Monitor, confirm that the author and package are the expected open-source project, then choose Install Now.
- Choose Activate. The Query Monitor menu appears in the admin toolbar for a user who has the required capability.
- If your deployment process uses source packages, the project also distributes releases through WordPress.org, GitHub, and Composer. Keep the package under version control and use the same version on staging and production when reproducing a problem.
Before testing, write down the URL or admin action, whether you are logged in, the browser or user role, and whether the symptom is a normal page load, an AJAX request, a REST request, a cron-like operation, or a redirect. Those details determine which request you need to inspect.
Reproduce before opening panels
- Open the exact page or screen that is slow or incorrect, or trigger the exact action that sends the AJAX or REST request.
- Wait for that request to finish. Do not read a toolbar report from a different page and assume it represents the failing action.
- Open the Query Monitor item in the admin toolbar. The top line gives the page-generation time, peak memory, SQL time, and query count for that request.
- Repeat the request if the result looks anomalous. Intermittent network responses, cache misses, and changing data can make one capture unrepresentative.
Read the panels in a useful order
1. Start with Timeline
The Timeline is the quickest overview of where request time is spent. It lays out recorded events so you can see whether the delay is concentrated in database work, a remote HTTP request, PHP execution, or late rendering. Use it to choose the next panel rather than opening every panel at random.
A long-looking event is a place to investigate, not an automatic diagnosis. Correlate it with the component, stack trace, query, or HTTP call shown elsewhere before changing code.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
2. Inspect Queries and Queries by Component
The queries panels show total SQL time and count, query type, calling function, and notices for slow, duplicate, or failed queries. The component view aggregates activity by WordPress core, the active theme, and individual plugins. Sort or scan for the component with unusually high aggregate time, a large number of queries, or repeated duplicates.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Finding | What to inspect next | What it does not prove |
|---|---|---|
| High total SQL time | The named function, query arguments, data volume, indexes, and whether a persistent object cache is available | That the named component is the sole cause or that rewriting one query will fix every request |
| Many duplicate queries | Repeated calls in the stack, missing caching, and whether the same value can be fetched once and reused | That every duplicate is harmful; some are conditional or required by the request |
| Query errors | The error text, calling file, hook path, and the component that issued the query | That the database server is necessarily at fault; malformed SQL can originate in application code |
Follow the caller and stack information to the responsible code path. Check query arguments and the relevant tables or indexes in a safe environment. If you deactivate a plugin for comparison, disable only one component at a time, record the change, and restore it immediately after the test if it is not the cause.
3. Check HTTP API Calls
The HTTP API panel exposes server-side requests that may not be visible in a browser’s page-timing waterfall. For each call, examine the URL, response code, duration, timeout state, and responsible component. A slow or failed remote service can make a page appear to have a database problem when the application is actually waiting on an external endpoint.
Test the remote service separately and inspect the responsible code for sensible timeouts, error handling, and retries. Do not hide a recurring timeout by simply increasing the page timeout. If an application uses Guzzle rather than WordPress’s HTTP API, its requests can be added to Query Monitor through the project’s documented middleware, allowing the same timing and attribution workflow.
4. Open PHP errors and “Doing it Wrong” notices
Use the PHP error panels for warnings, notices, deprecations, and fatal errors. Follow the component name, file, line, and stack trace to the hook or callback that generated the message. Reproduce with the same user role and request context before editing: a notice may occur only in the editor, only for an administrator, or only when a particular query variable is present.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Never paste passwords, API keys, authentication cookies, payment data, or personally identifiable request data into a public support ticket. Redact request values before sharing a stack trace.
5. Use hooks, templates, and blocks for rendering symptoms
If the output is wrong, a block disappears, or a callback runs in the wrong order, inspect the hooks panel and its priorities. The template and block panels show which template hierarchy and block rendering path handled the request. A hook can be technically fast yet still explain a visible defect if it runs before or after the callback that expects it.
For a controlled test, compare the affected page with a minimal theme and an isolated plugin set on staging. Restore the original theme and plugins after each test so that the comparison remains attributable.
6. Inspect scripts and styles for front-end symptoms
When a page is visually broken, interactive code fails, or asset order is suspect, use the scripts and styles panels. Check which component enqueued each file, whether dependencies and enqueue order are correct, and whether an asset is loaded on a request where it is not needed. Query Monitor identifies what WordPress enqueued during the request; browser developer tools can then confirm the resulting network or console behavior.
7. Confirm request and environment details
The request and environment diagnostics prevent false conclusions. Confirm rewrite and query variables, conditional tags, the active theme, the current user capability, PHP limits, object-cache status, and other values that differ between staging and production. For REST and AJAX failures, verify the endpoint, method, nonce or permission context, and the user under which the request was made.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Debug common WordPress problems step by step
A page is slow
- Capture the same URL several times and record the four top-line measurements.
- Use Timeline to decide whether the time is concentrated in SQL, PHP, or an HTTP call.
- For SQL-heavy requests, open Queries by Component and inspect slow and duplicate notices.
- For a remote-call delay, open HTTP API Calls and record duration, status, timeout, URL, and component.
- Change one suspected component or setting on staging, then reload the identical URL.
- Compare the new capture with the baseline and run functional checks before promoting the change.
A plugin appears beside a slow query
Open the query’s caller and arguments, then inspect the component aggregate. Check whether the query count and time remain high when the plugin is the only variable changed. Also test data volume, indexes, cache state, and interactions with the active theme or other plugins. A component attribution tells you where to begin code review; it does not establish that the plugin is intrinsically bad.
An AJAX action is slow or fails
- Record the exact button, form, or editor action and the logged-in user who triggers it.
- Trigger the action again so the AJAX request is the request being captured.
- Review the Timeline, SQL, PHP error, and HTTP panels for that request rather than for the page that contained the button.
- Check the request context, nonce, capability, posted values, and response status.
- Retest after one code or configuration change on staging.
A REST endpoint returns an error
Call the exact endpoint with the same authentication and permission context. Use the request, PHP error, query, and HTTP panels to distinguish a permission failure, malformed data, a database error, or a remote dependency. A successful browser page load does not demonstrate that the REST request is healthy; they are separate requests.
WordPress reports no persistent object cache
Query Monitor can flag the absence of persistent object caching. WordPress’s default object cache is non-persistent, so values normally do not survive between page loads. A persistent cache can reuse results across requests, but enabling one is an infrastructure decision: test invalidation, stale data behavior, memory limits, and compatibility with the application before deploying it. Query Monitor reports the cache condition; it does not configure or validate a cache for you.
Recommended Free Tools
Access control, overhead, and production safety
Who can see the output
By default, Query Monitor output is shown to Administrators on single-site installations and Super Administrators on multisite. An authentication cookie can grant access to a logged-out or otherwise unauthorized user. Enable that mechanism only deliberately, protect the cookie, and remove or rotate the access after troubleshooting.
Why staging is the safer default
Query Monitor’s FAQ describes its impact on page generation as small, but requests with hundreds of database queries can consume additional memory. Instrumentation also exposes URLs, query arguments, stack traces, and environment details. WordPress’s debugging handbook states that WP_DEBUG and related debugging tools are intended for local or staging use rather than live sites.
If you must investigate production, restrict visibility to the smallest possible group, avoid sharing captures that contain secrets, and monitor memory and response time. Disable or limit collection for long-running operations when the investigation ends.
Turn off SAVEQUERIES after debugging
WordPress’s SAVEQUERIES setting stores each query together with timing and caller information. That storage has a performance cost. If you enabled it to support debugging, turn it off when the work is complete, remove temporary logging, and verify that debug output is not displayed to visitors.
A repeatable investigation checklist
- Use staging whenever the change could affect data or availability.
- Record the exact URL, action, request type, user state, and baseline measurements.
- Capture the request again after every single change.
- Start with Timeline, then follow the relevant SQL, HTTP, PHP, hook, template, block, script, or style panel.
- Treat component names as leads and verify them with controlled deactivation or configuration tests.
- Check cache, PHP limits, permissions, rewrite variables, and other environment differences before changing application code.
- Redact credentials, cookies, tokens, and personal data from shared diagnostics.
- Run functional tests as well as speed measurements before promotion.
- Remove temporary authentication access and disable verbose debugging and
SAVEQUERIESwhen finished.
What a useful Query Monitor conclusion looks like
A defensible conclusion names the reproduced request, the measured symptom, and the evidence chain: for example, a particular editor request spent most of its time in repeated SQL calls attributed to one component, while a separate capture showed a remote HTTP timeout. It then records the controlled change, the new measurements, and the functional result. That is stronger than saying that a plugin is “slow” because its name appeared beside one query.
Frequently Asked Questions
Does Query Monitor show historical performance data?
No. Its panels describe the current request. Repeat the same request after each change and record the measurements yourself if you need a before-and-after comparison.
Can I use Query Monitor to find a slow external API call?
Yes. Open HTTP API Calls for the reproduced request and inspect the URL, response code, duration, timeout state, and responsible component. Guzzle requests require the project’s documented middleware to be added to Query Monitor.
Is Query Monitor safe to leave enabled on a live site?
It adds some overhead and exposes detailed request information. Prefer local or staging use; if production troubleshooting is unavoidable, restrict access, protect any authentication cookie, avoid sharing sensitive output, and disable verbose collection when finished.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Why does Query Monitor say there is no persistent object cache?
WordPress’s default object cache is non-persistent. A persistent cache can reuse values across requests, but enabling one requires testing invalidation, stale-data behavior, memory limits, and application compatibility.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
