Resource Timing
Copyright © 2025 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply. This specification defines an interface for web applications to access the complete timing information for resources in a document. This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C standards and drafts index. This document was published by the Web Performance Working Group as an Editor's Draft. Publication as an Editor's Draft does not imply endorsement by W3C and its Members. This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to cite this document as other than a work in progress. This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; t
Resource Timing Resource Timing Editor’s Draft , 20 April 2026 More details about this document This version: https://w3c.github.io/resource-timing/ Latest published version: https://www.w3.org/TR/resource-timing/ Feedback: public-web-perf@w3.org with subject line “ [resource-timing] … message topic … ” ( archives ) GitHub Editors: Yoav Weiss ( Shopify ) Noam Rosenthal ( Google ) Former Editors: Ilya Grigorik ( Google ) Todd Reifsteck ( Microsoft Corp. ) Arvind Jain ( Google Inc. ) Jatinder Mann ( Microsoft Corp. ) Zhiheng Wang ( Google Inc. ) Anderson Quach ( Microsoft Corp. ) Copyright © 202
Explore this link on the map →related reading
- Timing-Allow-Origin header - HTTP | MDNdeveloper.mozilla.org
- What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? · Issue #124 · w3c/navigation-timing · GitHubgithub.com
- Populating the page: how browsers work - Performance | MDNdeveloper.mozilla.org
- abseil / Performance Hintsabseil.io
- GitHub - GoogleChrome/lighthouse: Automated auditing, performance metrics, and best practices for the web. · GitHubgithub.com
- 40 maps that explain the internetvox.com
- Can You Afford It?: Real-world Web Performance Budgets - Infrequently Notedinfrequently.org
- Measure the Critical Rendering Path | Articles | web.devdevelopers.google.com
- Proton Mailmail.protonmail.com
- The Web Animation Performance Tier List | Motion Magazinemotion.dev
- 分析關鍵轉譯路徑效能 | Articles | web.devdevelopers.google.com
- Analyzing Critical Rendering Path Performance | Articles | web.devdevelopers.google.com