Web Performance Working Group

Mission

The mission of the Web Performance Working Group is to provide methods to measure aspects of application performance of user agent features and APIs.

Specs

Page Visibility (Second Edition) - Recommendation

This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications.

Performance Timeline - Recommendation

This specification defines an interface for web applications to access timing information related to navigation and elements. It is used by other specifications, like User Timing.

Resource Timing Level 1 - Candidate Recommendation

This specification defines an interface for web applications to access timing information related to HTML elements.

Beacon - Candidate Recommendation

This specification defines an interoperable means for site developers to asynchronously transfer data from the user agent to a web server, with the user agent taking the responsibility to eventually send the data.

High Resolution Time Level 2 - Recommendation

This specification defines a JavaScript interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

Network Error Logging - Working Draft

Navigation Error Logging defines an API to store and retrieve error data related to the previous navigations of a document.

Resource Hints - Working Draft

Resource Hints provides hints that authors may use to assist the user agent in fetching resources to improve page performance.

Server Timing - Working Draft

Server Timing, part of the performance timeline metrics, provides API access to request-response cycle performance metrics communicated from the server to the user agent.

Performance Timeline Level 2 - Working Draft

This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.

Preload - Candidate Recommendation

This specification defines the relationship of the HTML Link Element ().

preload<link>
Cooperative Scheduling of Background Tasks - Proposed Recommendation

The requestIdleCallback method is a more appropriate way for scheduling background tasks during times when the browser would otherwise be idle.

Reporting API - Working Draft

The reporting API provides a generic reporting framework which allows Web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

Page Visibility Level 2 - Proposed Recommendation

Page Visibility defines a means to programmatically determine the visibility state of a document. This can aid in the development of power and CPU efficient web applications.

User Timing Level 2 - Recommendation

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

High Resolution Time - Working Draft

This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

Resource Timing Level 2 - Working Draft

This specification defines an interface for web applications to access the complete timing information for resources in a document.

Long Tasks API 1 - Working Draft

This document defines an API that web page authors can use to detect presence of “long tasks” that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input.

Paint Timing 1 - Working Draft

This document defines an API that can be used to capture a series of key moments (First Paint, First Contentful Paint) during pageload which developers care about.

Device Memory - Working Draft

This document defines a HTTP Client Hint header to surface device capability for memory i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints.

User Timing Level 3 - Working Draft

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

Timing Entry Names Registry - Working Draft

This registry is intended to provide a central location for enumerating identified interface types of PerformanceEntry objects, which contain various data metrics for the the full lifecycle of a web application.

Repos

w3c/beacon (rec-track)

Beacon

w3c/device-memory (rec-track)

Device Memory

w3c/hr-time (rec-track)

High Resolution Time

w3c/longtasks (rec-track)

Long Task API

w3c/navigation-timing (rec-track)

Navigation Timing

w3c/network-error-logging (rec-track)

Network Error Logging

w3c/page-visibility (rec-track)

Page Visibility

w3c/paint-timing (rec-track)

Paint Timing

w3c/performance-timeline (rec-track)

Performance Timeline

w3c/preload (rec-track)

Preload

w3c/reporting (rec-track)

Reporting API

w3c/requestidlecallback (rec-track)

Cooperative Scheduling of Background Tasks

w3c/resource-hints (rec-track)

Resource Hints

w3c/resource-timing (rec-track)

Resource Timing

w3c/server-timing (rec-track)

Server Timing

w3c/user-timing (rec-track)

User Timing

w3c/perf-security-privacy (note)

Performance APIs, Security and Privacy

w3c/perf-timing-primer (note)

A Primer for Web Performance Timing APIs

w3c/timing-entrytypes-registry (note)

Timing Entry Names Registry

w3c/charter-webperf (process)

Web Performance Group charter

w3c/web-performance (homepage)

W3C Web Performance Working Group repo

w3c/webperf-dashboard (tool)

W3C webperf issue tracker

Contacts

Chairs:
Nic Jansma, Yoav Weiss,
Team contacts:
Carine Bournez,

Members

Invited Experts