See which outbound call held up the request

Inspect the request and response together

For supported Laravel HTTP client activity, the inspector retains method, safe URL, status, duration, bounded request and response headers and bodies, failure details, and a short application stack.

Separate remote wait from local work

The section summary totals observed outbound HTTP duration. A call at or above slow_http_request_ms is marked as slow; the default threshold is 250 milliseconds.

Use the Timeline to see whether calls run one after another, repeat with similar URLs, or sit beside expensive local work. Then decide whether the source can batch, cache, defer, parallelize, or avoid the call.

Distinguish HTTP responses from connection failures

• A completed response has an HTTP status and retained response details.
• A connection failure has no response status and includes the safe exception class and failure state.
• An application may accept a non-2xx status, so compare the status with the code path and expected remote contract.
• Retries can create several calls; inspect their order, URLs, duration, and source before treating them as duplicates.

Open the application call site

Follow the first useful application frame into the service, action, job, controller, or client wrapper that sent the request. Inspect its timeout, retry policy, payload construction, and handling of non-success statuses.

When several calls share the same wrapper, move down the retained stack to the caller that decided this request needed the remote data.

Verify the behavior, not only duration

Repeat the same request with a controlled remote response or Laravel HTTP fake. Confirm call count, method, safe URL shape, status handling, fallback behavior, and request result before comparing duration.