w3c/resource-timing

View on GitHub

Resource Timing

Stars: 135
Forks: 40
Open beginner issues: 0
Indexed issues: 52

Dominant language: Bikeshed
License: No license data
Last GitHub push: Sep 1, 2026
Latest indexed: Sep 20, 2026
Contributing guide: Contributing guide
Code of conduct: Code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Beginner friendly Everything

Open All

52 open issues indexed

Clarify Resource Timing semantics for Early Hints preloads Open

Difficulty 4/5 3-5 days Newbie friendliness 45/100

w3c/resource-timing#435 · 16 comments · Opened Jul 9, 2026
Should we be exposing same-origin redirects? Open

w3c/resource-timing#434 · 1 assignee · Opened Jun 3, 2026
Relation to the `PerformanceEntry` interface missing Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

w3c/resource-timing#433 · 3 comments · Opened May 21, 2026
Render-blocking status of a CSS preload which is subsequently requested while in flight Open

Difficulty 4/5 3-5 days Newbie friendliness 38/100

w3c/resource-timing#420 · 2 comments · 1 reaction · Opened Nov 3, 2025
Clarify nextHopProtocol value for cached fetch, part 2 Open

w3c/resource-timing#419 · 1 assignee · Opened Sep 16, 2025
Resource Timing Buffer/Secondary Buffer properties have vague location Open

w3c/resource-timing#414 · 1 assignee · Opened Mar 6, 2025
Inconsistent "response body info" vs "resource info" names Open

w3c/resource-timing#403 · 1 comment · 1 assignee · Opened Aug 22, 2024
Add service worker static routing API information to resource timing Open

Difficulty 4/5 3-5 days Newbie friendliness 38/100

w3c/resource-timing#389 · 18 comments · 2 reactions · Opened May 16, 2024
sendBeacon() integration Open

Difficulty 4/5 3-5 days Newbie friendliness 35/100

w3c/resource-timing#377 · 4 comments · Opened May 3, 2023
Adding resource discovery time to ResourceTiming API structure Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#374 · 3 comments · Opened Mar 31, 2023
Adding HTTP method to ResourceTiming API structure Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 30/100

w3c/resource-timing#373 · 8 comments · 1 reaction · Opened Mar 22, 2023
Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO Open

w3c/resource-timing#371 · 10 comments · 1 assignee · Opened Mar 9, 2023
Capturing basic auth credentials in URLs, part 2 Open

w3c/resource-timing#368 · 1 comment · 1 assignee · Opened Jan 20, 2023
Why is there noticeable gap between requestStart and connectEnd? Open

Difficulty 4/5 3-5 days Newbie friendliness 25/100

w3c/resource-timing#365 · 2 comments · Opened Dec 15, 2022
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#363 · 8 comments · Opened Nov 23, 2022
Cache and Proxy information Open

Difficulty 4/5 3-5 days Newbie friendliness 25/100

w3c/resource-timing#362 · 4 comments · 1 reaction · Opened Nov 21, 2022
InitiatorType for module scripts Open

w3c/resource-timing#346 · 2 comments · 1 assignee · Opened Sep 2, 2022
Reflect preload information (in ResourceTiming?) Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#303 · 23 comments · Opened Oct 26, 2021
initiatorType for favicon Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#298 · 6 comments · Opened Oct 3, 2021
Clean up cross references/versioning Open

w3c/resource-timing#271 · 7 comments · 2 assignees · Opened Apr 21, 2021
Resource initiator information to enable creation of dependency trees Open

enhancement

w3c/resource-timing#263 · 9 comments · 1 assignee · Opened Apr 1, 2021
Resource direct lookup support Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#255 · 7 comments · 2 reactions · Opened Feb 1, 2021
Rationalize Resource-Timing opt-ins with CORS/CORP Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 20/100

w3c/resource-timing#240 · 5 comments · Opened Dec 10, 2020
ResourceTiming Test Triage 9/2020 Open

hackathon_15_09_20 hackathon_2020

w3c/resource-timing#233 · 1 comment · 1 assignee · Opened Sep 15, 2020
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent accidental application state leakage Open

privacy-needs-resolution

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#223 · 2 comments · 1 reaction · Opened Feb 5, 2020
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage Open

privacy-needs-resolution

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#222 · 42 comments · 5 reactions · Opened Feb 5, 2020
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy Open

privacy-needs-resolution

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#221 · 11 comments · 3 reactions · Opened Feb 5, 2020
Provide a TAO-bypass for Navigation timing Open

Clarification editorial hackathon_15_09_20 hackathon_2020 requires Fetch integration

Difficulty 4/5 3-5 days Newbie friendliness 32/100

w3c/resource-timing#220 · 16 comments · Opened Jan 22, 2020
Cross-origin IFRAME opting-in to sharing ResourceTiming data Open

enhancement requires Fetch integration

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#210 · 8 comments · 3 reactions · Opened Jun 11, 2019
Add tests for not-same-site nested contexts Open

test:missing-coverage

w3c/resource-timing#204 · 3 comments · 1 reaction · 1 assignee · Opened Mar 29, 2019
Register TAO as Permanent Message Header Field Name Open

w3c

w3c/resource-timing#198 · 1 assignee · Opened Jan 15, 2019
Expose JavaScript code caching information in PerformanceResourceTiming Open

enhancement whiteboard

Difficulty 5/5 Over a week Newbie friendliness 30/100

w3c/resource-timing#190 · 7 comments · 1 reaction · Opened Jan 2, 2019
Test multiple DNS responses and connection failures Open

test:missing-coverage

w3c/resource-timing#188 · 3 comments · 1 assignee · Opened Dec 18, 2018
Test domainLookup values in the connection coalescing case Open

test:missing-coverage

w3c/resource-timing#186 · 1 comment · 1 assignee · Opened Dec 18, 2018
Access to the Remote Address information Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 30/100

w3c/resource-timing#180 · 4 comments · Opened Nov 28, 2018
Make TAO a subset of CORS Open

enhancement requires Fetch integration

Difficulty 5/5 Over a week Newbie friendliness 30/100

w3c/resource-timing#178 · 5 comments · 2 reactions · Opened Nov 13, 2018
Allow semi-wildcard `Timing-Allow-Origin` values (for subdomains) Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#175 · 2 comments · 6 reactions · Opened Oct 24, 2018
consider adding attributes to track Cache API performance in a service worker FetchEvent handler Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#162 · 6 comments · Opened Aug 16, 2018
Critical path length? Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#149 · 2 comments · Opened Mar 17, 2018
`InitiatorType` should not single out XHR Open

Clarification

Difficulty 4/5 3-5 days Newbie friendliness 35/100

w3c/resource-timing#142 · 14 comments · Opened Jan 24, 2018
Proposal: API for exposing resource requests Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 20/100

w3c/resource-timing#137 · 19 comments · 3 reactions · Opened Jan 10, 2018
Resource processing time Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#133 · 5 comments · Opened Dec 18, 2017
Collect initiatorType use-cases Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#132 · 3 comments · Opened Dec 15, 2017
Would like a precise way to map PerformanceTimings to FetchEvent Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#259 · 16 comments · Opened Aug 8, 2017
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object Open

enhancement requires Fetch integration

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#102 · 5 comments · 19 reactions · Opened Feb 21, 2017
Add information about local cache performance Open

enhancement whiteboard

Difficulty 5/5 Over a week Newbie friendliness 35/100

w3c/resource-timing#76 · 6 comments · Opened Nov 9, 2016
Expose the TLS certificate + other TLS parameters for a resource Open

enhancement whiteboard

Difficulty 5/5 Over a week Newbie friendliness 20/100

w3c/resource-timing#75 · Opened Nov 8, 2016
Add fields for identifying the security protocol, cipher, signature and so on Open

enhancement whiteboard

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#74 · 22 comments · 1 reaction · Opened Nov 8, 2016
For all resources, add timestamp of when it was available to the browser Open

enhancement

Difficulty 5/5 Over a week Newbie friendliness 25/100

w3c/resource-timing#60 · 3 comments · Opened Jun 24, 2016
initiatorType definition doesn't define initiator in multiple element scenarios Open

Clarification whiteboard

w3c/resource-timing#54 · 10 comments · 1 assignee · Opened May 23, 2016

w3c/resource-timing

Get new issues in your inbox