Per-request WordPress execution time, peak memory, database query counts, and hook timelines — the data you need to pinpoint exactly where slowdowns originate.
When a WordPress page is slow, the cause is almost always one of three things: a slow database query, a slow external request, or a CPU-intensive hook callback. The Request Profiler captures all three for every frontend page visit — passively, without modifying any WordPress code — and presents the data in a sortable table that makes the culprit immediately obvious.
Captures the total PHP execution time and peak memory usage for every profiled WordPress request. The memory delta shows the difference between memory at request start and peak — a large delta often indicates an inefficient data loading pattern in a plugin or theme.
Records the total number of WordPress database queries executed per request and their combined execution time. Aggregate metrics are always available; per-query timing requires SAVEQUERIES to be enabled in wp-config.php.
When SAVEQUERIES is active, identifies the slowest individual WordPress database queries with their execution time, the SQL statement, and the hook context in which they fired — tracing a slow query directly to the responsible plugin.
Captures WordPress performance data for every frontend page visit passively. The historical table shows execution time, memory, and query count per URL over time — making it easy to identify consistently slow WordPress pages.
When opt-in hook capture is enabled, renders a timeline of WordPress hook execution showing relative time spent per action and filter callback — making it immediately clear whether a single hook is consuming a disproportionate share of execution time.
Passive collection adds a few milliseconds per request for storing metrics. The detailed profiling mode with SAVEQUERIES adds more overhead and is not recommended for sustained use on high-traffic production WordPress sites.
No — aggregate WordPress query count and total query time are available without it. Individual query-level timing data and SQL statement capture require SAVEQUERIES = true in wp-config.php.
Performance snapshots are stored in the WordPress options table. No personal data is captured — only execution metrics, memory figures, query counts, and page URLs. Stored snapshots can be cleared from within the module.
No. The Request Profiler is a Pro-exclusive module.
Exactly where your WordPress execution time is going — per request, per page, per hook.
The Request Profiler is included in every Pro plan alongside all seventeen diagnostic modules.
Download Lite to get started with the nine core WordPress diagnostic modules — completely free.
