What does the redirect time measure in web performance?

Redirect time specifically measures the duration it takes for a browser to follow a redirect after making an initial request. This time includes the moment the initial request is made to the redirect response being received and processed, as well as any time spent on any follow-up HTTP requests that must occur due to the redirection.

When a user attempts to access a URL that has been redirected, the server responds with a redirect status code (like 301 or 302), and the browser must then make another request to the new URL. The metric tracks the total time from the initial request until the redirected request is complete, including the associated latency.

This makes redirect time a critical metric for understanding how efficiently content is delivered when URLs are subject to relays through various locations on the web. It helps pinpoint issues that might affect user experience, as excessive redirect time could lead to delays in loading content.

The other options represent different facets of web performance measurement but do not accurately define redirect time. For example, DNS resolution focuses on how quickly a domain name can be translated into its corresponding IP address, while establishing a secure connection pertains to SSL/TLS handshake times. Total page load time aggregates various metrics, including the initial request, but does not isolate the specific time spent on