大网数据广告活动
Web 标准与前端开发

PerformanceResourceTiming: finalResponseHeadersStart property

· 52CE 我爱测

The **`finalResponseHeadersStart`** read-only property returns a DOMHighResTimeStamp immediately after the browser receives the first byte of the final document response (for example, ) from the server.

Performance API

The finalResponseHeadersStart read-only property returns a DOMHighResTimeStamp immediately after the browser receives the first byte of the final document response (for example, ) from the server.

This differs from PerformanceResourceTiming.requestStart (which may also be represented as PerformanceResourceTiming.firstInterimResponseStart), as this starts from the first bytes of any response including interim responses (for example, 103 Early Hints) with the final response coming potentially much later.

When there are no interim responses, requestStart is the same as finalResponseHeadersStart and firstInterimResponseStart is 0.

There is no end property for finalResponseHeadersStart.

Value

The finalResponseHeadersStart property can have the following values:

  • A DOMHighResTimeStamp immediately after the browser receives the first bytes of the final response from the server.
  • 0 if the resource is a cross-origin request and no Timing-Allow-Origin HTTP response header is used.

Examples

Measuring request time

The finalResponseHeadersStart and PerformanceResourceTiming.requestStart properties can be used to measure how long it takes for the browser to start receive the final response after the sending the request.

const request = entry.finalResponseHeadersStart - entry.requestStart;

The following example uses a PerformanceObserver to notify of new resource performance entries as they are recorded in the browser's performance timeline. The buffered option is used for accessing entries from before the observer creation.

const observer = new PerformanceObserver((list) => {
  list.getEntries().forEach((entry) => {
    const request = entry.finalResponseHeadersStart - entry.requestStart;
    if (request > 0) {
      console.log(`${entry.name}: final response time: ${request}ms`);
    }
  });
});

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

The following example uses Performance.getEntriesByType(), which only shows resource performance entries present in the browser's performance timeline at the time you call the method.

const resources = performance.getEntriesByType("resource");
resources.forEach((entry) => {
  const request = entry.finalResponseHeadersStart - entry.requestStart;
  if (request > 0) {
    console.log(`${entry.name}: final response time: ${request}ms`);
  }
});

The following example shows how to measure the time between the first and final response headers.

const observer = new PerformanceObserver((list) => {
  list.getEntries().forEach((entry) => {
    const diff = entry.finalResponseHeadersStart - entry.responseStart;
    if ((entry.finalResponseHeadersStart > 0) & (diff > 0)) {
      console.log(
        `${entry.name}: time between first and final response start: ${diff}ms`,
      );
    }
  });
});

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

Cross-origin timing information

If the value of the finalResponseHeadersStart 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://developer.mozilla.org to see timing resources, the cross-origin resource should send:

Timing-Allow-Origin: https://developer.mozilla.org

Specifications

Browser compatibility

See also

  • Timing-Allow-Origin
  • PerformanceResourceTiming.firstInterimResponseStart

来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。

资料来源与适用范围

资料来源
MDN Web Docs / Mozilla 贡献者
适用范围
请按文中版本与环境说明核对
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 2.5

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。