External Dependency Monitor

Tracks every outbound HTTP request your WordPress site makes — because a slow or failing third-party API can silently cripple your WordPress page load times.

  • Per-Host Latency Breakdown
  • 0 Database Writes
  • Read-Only Architecture

What This Module Does

Every external API call your WordPress site makes is a dependency you don't control. A payment gateway that's slow. An analytics endpoint with intermittent failures. A font CDN that occasionally times out. Each of these can double your WordPress page load time without generating a single PHP error or WordPress notice. The External Dependency Monitor captures every outbound HTTP request, measures its latency, and surfaces the ones that are slowing you down or failing entirely.

Features at a Glance

Per-Host WordPress Request Summary

Groups all captured outbound WordPress HTTP requests by host and shows request count, average latency, maximum latency, and error rate per host. Immediately tells you which third-party services your WordPress site depends on and how reliably they're responding.

WordPress Slow Request Identification

WordPress HTTP requests taking longer than 500ms are flagged individually with their URL, latency, and HTTP status code. These are the requests most likely to be adding visible delay to your WordPress page loads.

WordPress Failing Request Detection

HTTP errors (4xx, 5xx) and connection timeouts from WordPress outbound requests are listed separately with their status codes. A failing external request on every WordPress page load can be the root cause of admin slowness or broken checkout flows.

Blocking vs. Non-Blocking WordPress Requests

Classifies WordPress HTTP requests as blocking (fired synchronously, holding up WordPress page execution) or non-blocking (fired asynchronously). Blocking external requests are far more damaging to WordPress page performance.

Passive WordPress Background Collection

WordPress HTTP request data is captured passively during normal page loads — no special testing mode required. The monitor hooks into WordPress's HTTP API and records latency data without adding overhead to the actual requests.

Why It Matters

  • Discover that a third-party API is adding 800ms to your WordPress TTFB without generating any errors
  • Identify the exact external service causing intermittent WordPress page load slowdowns
  • Find abandoned API integrations making failed HTTP requests on every WordPress page load
  • Distinguish between blocking and non-blocking external WordPress requests and their relative performance impact
  • Give external service providers precise WordPress latency data when escalating performance issues

Frequently Asked Questions

How does the module capture external WordPress request data?

It hooks into WordPress's pre_http_request and http_response filters to intercept and time every call made through wp_remote_get(), wp_remote_post(), and the WordPress HTTP API. Direct PHP curl calls are not captured.

Does monitoring WordPress HTTP requests affect site performance?

No. The monitor adds a timestamp before and after each request to measure latency. This takes microseconds and has no effect on actual request execution or response.

What counts as "slow" for a WordPress external request?

The default slow threshold is 500ms. Requests taking longer are flagged individually. Hosts with an average latency above 300ms across all WordPress requests are also highlighted.

Is this available in the free Lite version?

No. The External Dependency Monitor is a Pro-exclusive module.

Find Out Which Third-Party APIs Are Slowing Down Your WordPress Site

Captures every outbound WordPress HTTP request and surfaces the ones costing you page load time.

Get Full Pro Access

External Dependency Monitor 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