PerformanceResourceTiming: secureConnectionStart property
The secureConnectionStart read-only property returns a timestamp immediately before the browser starts the handshake process to secure the current connection. If a secure connection is not used, the property returns zero.
Value
The secureConnectionStart property can have the following values:
- A
DOMHighResTimeStampindicating the time immediately before the browser starts the handshake process to secure the current connection if the resource is fetched over a secure connection. 0if no secure connection is used.0if the resource was instantaneously retrieved from a cache.0if the resource is a cross-origin request and noTiming-Allow-OriginHTTP response header is used.
Examples
Measuring TLS negotiation time
The secureConnectionStart and requestStart properties can be used to measure how long it takes for the TLS negotiation to happen.
js
const tls = entry.requestStart - entry.secureConnectionStart;
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.
js
const observer = new PerformanceObserver((list) => {
list.getEntries().forEach((entry) => {
const tls = entry.requestStart - entry.secureConnectionStart;
if (tls > 0) {
console.log(`${entry.name}: TLS negotiation duration: ${tls}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:
js
const resources = performance.getEntriesByType("resource");
resources.forEach((entry) => {
const tls = entry.requestStart - entry.secureConnectionStart;
if (tls > 0) {
console.log(`${entry.name}: TLS negotiation duration: ${tls}ms`);
}
});
Cross-origin timing information
If the value of the secureConnectionStart property is 0, the resource is either not using a secure connection or it is 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:
http
Timing-Allow-Origin: https://developer.mozilla.org
Specifications
| Specification |
|---|
| Resource Timing # dom-performanceresourcetiming-secureconnectionstart |
Browser compatibility
BCD tables only load in the browser