PerformanceResourceTiming: responseEnd property - Web APIs | MDN
Value
A DOMHighResTimeStamp immediately after the browser receives the last
byte of the resource or immediately before the transport connection is closed, whichever
comes first.
Examples
Measuring time to fetch (without redirects)
The responseEnd and fetchStart properties can be used to measure the overall time it took to fetch the final resource (without redirects). If you want to include redirects, the overall time to fetch is provided in the duration property.
js
const timeToFetch = entry.responseEnd - entry.fetchStart;
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 timeToFetch = entry.responseEnd - entry.fetchStart;
if (timeToFetch > 0) {
console.log(`${entry.name}: Time to fetch: ${timeToFetch}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 timeToFetch = entry.responseEnd - entry.fetchStart;
if (timeToFetch > 0) {
console.log(`${entry.name}: Time to fetch: ${timeToFetch}ms`);
}
});
Specifications
| Specification |
|---|
| Resource Timing # dom-performanceresourcetiming-responseend |