DOCSEARCHbyAlgolia
Submit Docs

W3C Web Performance Working Group

repository·gh-pages·Indexed 19 days ago

https://github.com/w3c/web-performance

Central hub for the W3C Web Performance Working Group, managing specifications, agendas, and meeting minutes for web performance APIs. The group focuses on three pillars: Measurement (e.g., Resource Timing, Paint Timing, Event Timing), Scheduling (e.g., requestIdleCallback, Long Tasks), and Adaptation (e.g., Device Memory). It develops standards for observing and improving application performance across desktop and mobile browsers.

Tokens
5.8K
Snippets
6
Records
39
Agent score
65%

What's inside W3C Web Performance

  1. Overview of W3C Web Performance Specifications

    gh-pages

    The W3C Web Performance Working Group develops specifications for web performance monitoring and optimization. The following specifications are currently active or linked via their respective GitHub repositories:

    Active Specifications

    • High Resolution Time: hr-time
    • Performance Timeline: performance-timeline
    • Resource Timing: resource-timing
    • Navigation Timing: navigation-timing
    • User Timing: user-timing
    • Request Idle Callback: requestidlecallback
    • Beacon API: beacon
    • Server Timing: server-timing
    • Long Tasks: longtasks
    • Paint Timing: paint-timing
    • Device Memory: device-memory
    • Reporting API: reporting
    • Network Error Logging: network-error-logging
    • Event Timing: event-timing
    • Largest Contentful Paint: largest-contentful-paint

    Past Deliverables

    • page-visibility
    • resource-hints
    • preload

    Incubations (WICG)

    Experimental features under development include element-timing, is-input-pending, layout-instability, performance-measure-memory, netinfo, unload-beacon, scheduling-apis, js-self-profiling, page-lifecycle, deprecation-reporting, intervention-reporting, and crash-reporting.

  2. Understand the scope of the Web Performance Working Group

    gh-pages

    The Web Performance Working Group focuses on developing user agent features and APIs to observe and improve application performance. The work is categorized into three primary pillars:

    • Measurement: APIs for measuring network and rendering performance, responsiveness, interactivity, memory/CPU usage, and application failures. This includes metrics for both initial application loading and continuous user interaction (e.g., in single-page apps), with an emphasis on privacy-preserving techniques.
    • Scheduling: APIs that allow developers to improve the scheduling of application work and network resource usage to minimize loading times.
    • Adaptation: APIs that enable developers to deliver resources adapted to specific user devices, preferences, or environmental conditions.

    Deliverables are intended for desktop and mobile browsers, as well as other non-browser environments, and are designed to be consistent with HTML, CSS, Web Application Security, Web Apps, Device and Sensors, and SVG specifications.

  5. Network Error Logging API

    gh-pages
    The Network Error Logging API allows developers to declare a network error reporting policy for a web application. User agents use this policy to report network errors that prevented the successful fetching of requested resources.

  6. Beacon API

    gh-pages
    The Beacon API is an interoperable API that allows site developers to asynchronously transfer data from the user agent to a web server. The API provides a guarantee from the user agent that the data will eventually be sent, even if the page is being unloaded.

  8. Cooperative Scheduling of Background Tasks (requestIdleCallback)

    gh-pages
    The Cooperative Scheduling of Background Tasks API (often associated with requestIdleCallback) allows web page authors to schedule background tasks that run only when the browser is idle. This prevents these tasks from introducing delays to high-priority activities like input processing, animations, and frame compositing.

  9. Server Timing API

    gh-pages
    The Server Timing specification enables a server to communicate performance metrics regarding the request-response cycle to the user agent. It includes a standardized JavaScript interface for applications to collect, process, and act on these metrics to optimize delivery.

  10. Navigation Timing API

    gh-pages

    The Navigation Timing specification defines an interface for web applications to access complete timing information regarding the navigation of a document.

    Note: Future development of new Navigation Timing features is planned to be merged into the Resource Timing specification.

  12. High Resolution Time API

    gh-pages
    The High Resolution Time specification defines an API that provides the current time in sub-millisecond resolution. This API is designed to be resistant to system clock skew or manual adjustments, making it suitable for precise performance measurements.