Skip to content

wp_slow_page_load

Severity: Warning Signal: http.request — page response time exceeded threshold

What this signal means

A page request took an abnormally long time to generate a response. This is the server-side execution time — the time PHP spent generating the response, not including network latency or browser rendering.

What surprise this prevents

Page load degradation going undetected until users complain or search rankings drop — a slow path that affects every visitor but produces no visible error.

Why it matters

Slow pages are functionally broken for many users. Google Search uses page speed as a ranking factor, and slow pages increase bounce rates. On shared hosting, slow requests can also trigger PHP timeout kills.

Investigate

View entity alerts in Logystera →

Check the alert for:

  • payload.path — which URL is slow?
  • payload.execution_time_ms — how slow was it?
  • payload.is_admin — is it a frontend or admin page?
  • payload.is_cron — is it a cron request? Slow cron runs are usually separate from user-facing slowness.

  1. Identify whether the slowness is consistent. Check multiple http.request signals for the same path. Is it always slow, or occasional spikes?

  2. Install Query Monitor to find slow queries on that specific page.

  3. Check for external HTTP calls blocking page load. Plugins making external API calls (payment gateways, social media APIs, SEO tools) can stall page generation if the external service is slow or down. Use Query Monitor's HTTP API Calls tab.

  4. Enable caching. If you don't have a page cache, install one:

  5. WP Super Cache
  6. W3 Total Cache

  7. LiteSpeed Cache (if using LiteSpeed server)

  8. Check PHP execution limits. If requests are timing out at exactly 30 or 60 seconds, you've hit max_execution_time. Increase it or fix the underlying slowness: php set_time_limit( 120 );

  9. Profile with Xdebug or Blackfire (development environment) if the slow path is in custom code.

  10. Check server load. High CPU or I/O on the hosting server causes all requests to slow down. Check with your host or use top/htop if you have server access.

When to safely ignore

A single slow request on an admin page (bulk export, cache rebuild, large import) is expected. Admin operations are not user-facing and are not subject to the same latency requirements.

If the slow path is a rarely-visited archive or search results page under specific conditions (e.g., an unusual search query), assess frequency before treating it as a systemic issue.

Signal reference

{
  "event_type": "http.request",
  "payload": {
    "path": "/product/widget-pro/",
    "status": 200,
    "is_admin": false,
    "execution_time_ms": 7421,
    "peak_memory_mb": 48.2
  }
}