Request Profiler

Per-request WordPress execution time, peak memory, database query counts, and hook timelines — the data you need to pinpoint exactly where slowdowns originate.

  • Per-Request Performance Data
  • 0 Database Writes
  • Read-Only Architecture

What This Module Does

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.

Features at a Glance

WordPress Execution Time & Memory Delta

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.

WordPress Query Count & Total Time

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.

WordPress Slow Query Detection

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.

Page-Level Historical Diagnostics

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.

WordPress Hook Timeline Visualisation

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.

Why It Matters

  • Identify the specific WordPress page, plugin, or query causing WordPress site slowness
  • Compare WordPress page performance before and after plugin updates to catch performance regressions
  • Give WordPress hosting providers specific execution metrics when escalating slow-site support tickets
  • Diagnose intermittent WordPress slowdowns by reviewing the historical performance capture table
  • Find which WordPress hook callbacks are consuming the most execution time on a given request

Frequently Asked Questions

Does the WordPress Request Profiler affect site performance?

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.

Does SAVEQUERIES need to be enabled in WordPress?

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.

Where is WordPress profiling data stored?

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.

Is this available in the free Lite version?

No. The Request Profiler is a Pro-exclusive module.

Stop Guessing — Start Measuring WordPress Performance

Exactly where your WordPress execution time is going — per request, per page, per hook.

Get Full Pro Access

The Request Profiler is included in every Pro plan alongside all seventeen diagnostic modules.

Get Pro Now

Try the Free Lite Version

Download Lite to get started with the nine core WordPress diagnostic modules — completely free.

Download Lite — Free