Why Measure Web Performance?
Peak-hour congestion, peering bottlenecks, slow name servers, sluggish servers, and TCP behaviour on long or lossy paths all slow a connection down, and link utilisation counters do not show it.
Such measurements provide figures that can be compared across regions, access technologies and providers and used in SLAs and regulatory reports.
What the User Waits For
A single web or file transfer passes through several phases. Each one can be measured on its own, and each points to a different part of the chain.
| Phase | What it shows |
|---|---|
| DNS resolution | Whether name servers are reachable and fast |
| Connection setup | Round-trip time to the server and server responsiveness |
| Time to first byte | How quickly the service starts delivering |
| Download and upload throughput | The capacity available to an application |
| Transfer success | Reliability: completed, failed and aborted transfers, with the reason for each failure or abort |
From Network Tests to Service Tests
Web performance can be tested on several complementary layers.
One Connection or Many?
A single TCP connection is sensitive to latency and loss. Several parallel connections fill even fast lines.
Utilisation: 80% with 1 connection
Utilisation: 92% with 4 connections
Running uploads and downloads at the same time reveals effects that sequential tests miss, such as growing latency when buffers fill under load.