Network Performance Metrics

Network Performance Metrics gives you a detailed timing breakdown for every intercepted request, helping you identify exactly where latency is introduced in the network stack.

Note

Network Performance Metrics is a Pro feature. Free users can see the Timing tab but the data is blurred — upgrade to Pro to unlock full access.

How It Works

When WePROXA intercepts a request, it measures each phase of the network lifecycle and records precise timing data. This data is displayed as an interactive waterfall chart inside the request details panel.

The following phases are measured when they apply:

Phase	Description
DNS Resolution	Time to resolve the hostname to an IP address
TCP Connect	Time to establish a TCP connection to the server
TLS Handshake	Time to complete the TLS/SSL handshake (HTTPS only)
TTFB	Time to First Byte — time from sending the request to receiving the first byte of the response

Some requests reuse an already-open pooled connection, so DNS, TCP, or TLS phases may be absent. In that case, the request has skipped those setup costs and usually shows only the response-side timing that happened for that specific request.

HTTP/2 and Pooled Connections

WePROXA can reuse HTTP/1.1 keep-alive connections and multiplex HTTP/2 requests over a shared upstream session. The first request to an origin may show DNS, TCP, and TLS setup time, while later requests to the same origin can reuse the warm connection.

Connection prewarming and TLS session reuse reduce cold-start latency for HTTPS captures. During very large bursts, WePROXA also limits how many fresh connections are opened at once so one busy origin cannot overwhelm the proxy or the upstream server.

Viewing Timing Data

1. Select a completed request in the request list
2. In the response section of the details panel, click the Timing tab
3. You’ll see:
   • A waterfall bar showing the relative duration of each phase, color-coded for quick identification
   • A detail table listing each phase with its exact duration

Hover over any segment in the waterfall bar to see the phase name and exact timing.

Reading the Waterfall

The waterfall bar visualizes how time is distributed across the network phases:

• 🟢 Teal — DNS Resolution
• 🟠 Orange — TCP Connect
• 🟣 Purple — TLS Handshake
• 🔵 Blue — TTFB

The total time displayed is the sum of all measured phases. Phases that don’t apply (e.g., TLS Handshake for plain HTTP requests) are automatically omitted.

Use Cases

Diagnosing Slow Requests

If a request feels slow, the timing breakdown helps you pinpoint the bottleneck:

• High DNS Resolution — DNS server may be slow or the hostname isn’t cached. Consider using a faster DNS resolver.
• High TCP Connect — The server may be geographically distant or experiencing connection issues.
• High TLS Handshake — Certificate chain verification or key exchange may be slow. Check if the server supports TLS session resumption.
• High TTFB — The server is taking a long time to generate the response. This usually points to backend processing delays.
• Missing setup phases — The request likely reused a pooled connection, especially for HTTP/2 traffic where many requests share one TLS session.

Comparing Endpoints

Select different requests to compare their timing profiles. This is useful for:

• Identifying which API endpoints are slowest
• Verifying that caching is reducing response times
• Checking whether a CDN is improving latency

Before and After Testing

Use timing data alongside Network Conditioning to validate how your application handles different latency profiles, then measure the real performance to compare.