resource-timing
resource-timing copied to clipboard
w3c
Resource Timing
Introducing HTTP response status code. (https://github.com/w3c/resource-timing/issues/90) Fetch changes : https://github.com/whatwg/fetch/pull/1468 Explainer : https://github.com/abinpaul1/resource-timing/blob/explainer-resource-response-status/Explainers/Response_Status_Code.md *** Preview | Diff
Right now, it's hard to tell which resources were actually render blocking and which ones were not. Developers can try to heuristically guess that, based on when those resources were...
In most cases a single RT entry corresponds to a single completed fetch (successful or non-aborted network error). However, in the case of iframes this is a bit murky, especially...
Introducing a render blocking status field. (https://github.com/w3c/resource-timing/issues/262) Fetch changes : https://github.com/whatwg/fetch/pull/1449 ~~HTML changes: https://github.com/whatwg/html/pull/7979~~ Explainer : https://github.com/abinpaul1/resource-timing/blob/render-blocking-status-explainer/Explainer/Render_Blocking_Status.md *** Preview | Diff
I'd like to be able to use Resource Timing to programmatically get a sense of where my application is spend its performance budget, but unfortunately I cannot because resource timing...
Navigation Timing is sharing many attribute definitions with Resource Timing, but doesn't use TAO, as it makes no sense in NT's context. We need to provide an internal flag that...
https://wpt.fyi/results/resource-timing?label=master&label=experimental&aligned Filing bugs for failing tests: Safari: * [TAO related](https://bugs.webkit.org/show_bug.cgi?id=216540) * TAO-case-insensitive-null-opaque-origin.sub.html * TAO-crossorigin-port.sub.html * resource_TAO_multi_wildcard.html * resource_TAO_match_wildcard.htm * resource-reload-TAO.sub.html * nextHopProtocol-tao-protected.https.html * crossorigin-sandwich-TAO.sub.html * [ServiceWorker related](https://bugs.webkit.org/show_bug.cgi?id=216541) * workerStart-tao-protected.https.html *...
This is an attempt to address both w3c/navigation-timing#163 and #303 by exposing a `deliveryType` attribute on `PerformanceResourceTiming` (as mentioned in https://github.com/w3c/resource-timing/issues/303#issuecomment-1099078362), specifically the entry that may consume (rather than populate)...
