PerformanceResourceTiming: redirectStart property

Value

The redirectStart property can have the following values:

• A timestamp representing the start time of the fetch which initiates the redirect.
• 0 if there is no redirect.
• 0 if the resource is a cross-origin request and no Timing-Allow-Origin HTTP response header is used.

Examples

Measuring redirection time

The redirectStart and redirectEnd properties can be used to measure how long the redirection takes.

const redirect = entry.redirectEnd - entry.redirectStart;

Example using a PerformanceObserver, which notifies of new resource performance entries as they are recorded in the browser's performance timeline. Use the buffered option to access entries from before the observer creation.

const observer = new PerformanceObserver((list) => {
  list.getEntries().forEach((entry) => {
    const redirect = entry.redirectEnd - entry.redirectStart;
    if (redirect > 0) {
      console.log(`${entry.name}: Redirect time: ${redirect}ms`);
    }
  });
});

observer.observe({ type: "resource", buffered: true });

Example using Performance.getEntriesByType(), which only shows resource performance entries present in the browser's performance timeline at the time you call this method:

const resources = performance.getEntriesByType("resource");
resources.forEach((entry) => {
  const redirect = entry.redirectEnd - entry.redirectStart;
  if (redirect > 0) {
    console.log(`${entry.name}: Redirect time: ${redirect}ms`);
  }
});

Cross-origin timing information

If the value of the redirectStart property is 0, the resource might be a cross-origin request. To allow seeing cross-origin timing information, the Timing-Allow-Origin HTTP response header needs to be set.

For example, to allow https://big.rakal.top to see timing resources, the cross-origin resource should send:

Timing-Allow-Origin: https://big.rakal.top

Specifications

Browser compatibility

See also

• PerformanceNavigationTiming.redirectCount
• Timing-Allow-Origin