Diagnose WordPress slowness methodically with Query Monitor

Exercise goal: inspect database activity on a test page without treating one observation as a complete performance diagnosis.

Install Query Monitor from the official link below and review the listed version requirements before activation.

Stay signed in as an administrator and open a test page. The admin bar should display a timing and query summary.

Open Queries from the Query Monitor menu and record the total count and total query time first.

Reload the same page under the same conditions. Do not remove a plugin or change code from a single measurement.

Use Queries by Component to identify the theme or plugin associated with queries, but do not assume correlation proves the cause.

If Duplicate Queries appears, open Caller to inspect the recorded call location.

For a controlled test, temporarily disable one nonessential plugin on staging only and measure the same page again.

Record query count, total time, and errors before and after. Keep cache, traffic, and page data as consistent as possible.

If nothing changes, reactivate the plugin and test another hypothesis such as the theme or an HTTP request.

Query Monitor exposes sensitive technical details. Restrict administrator access and do not publish screenshots containing paths or errors.

Success check: you have a repeatable difference with a specific caller. Keep the plugin active on production only when needed.

Related tutorials