Note: This feature is available in Web Workers

Secure context

This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.

The PerformanceServerTiming interface surfaces server metrics that are sent with the response in the Server-Timing HTTP header.

This interface is restricted to the same origin, but you can use the Timing-Allow-Origin header to specify the domains that are allowed to access the server metrics. Note that this interface is only available in secure contexts (HTTPS) in some browsers.


PerformanceServerTiming.descriptionRead only
A DOMString value of the server-specified metric description, or an empty string.
PerformanceServerTiming.durationRead only
A double that contains the server-specified metric duration, or value 0.0.
PerformanceServerTiming.nameRead only
A DOMString value of the server-specified metric name.


Returns a DOMString that is the JSON representation of the PerformanceServerTiming object.


Given a server that sends the Server-Timing header, for example a node.js server like this:

const http = require('http');

function requestHandler(request, response) {
  const headers = {
    'Server-Timing': `
      cache;desc="Cache Read";dur=23.2,
    `.replace(/\n/g, '')
  response.writeHead(200, headers);
  return setTimeout(_ => {
 }, 1000)

http.createServer(requestHandler).listen(3000).on('error', console.error);

The PerformanceServerTiming entries are now observable from JavaScript via the PerformanceResourceTiming.serverTiming property:

let entries = performance.getEntriesByType('resource');
// 0: PerformanceServerTiming {name: "cache", duration: 23.2, description: "Cache Read"}
// 1: PerformanceServerTiming {name: "db", duration: 53, description: ""}
// 2: PerformanceServerTiming {name: "app", duration: 47.2, description: ""}


Specification Status Comment
Server Timing
The definition of 'PerformanceServerTiming' in that specification.
Working Draft Initial definition.

Browser compatibility

BCD tables only load in the browser

See also