Estándar

El Web Performance Working Group es el equipo que plantea distintas especificaciones que utilizar a la hora de trabajar con mediciones y buenas prácticas de Web Performance.

  • Navigation TimingRecommendation
    This document provides an interface for web applications to access timing information related to navigation and elements.
  • 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 TimelineRecommendation
    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 1Candidate Recommendation
    This specification defines an interface for web applications to access timing information related to HTML elements.
  • Navigation Timing Level 2Working Draft
    This document provides an interface for web applications to access timing information related to navigation and elements.
  • BeaconCandidate 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 2Recommendation
    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 LoggingWorking Draft
    Navigation Error Logging defines an API to store and retrieve error data related to the previous navigations of a document.
  • Resource HintsWorking Draft
    Resource Hints provides hints that authors may use to assist the user agent in fetching resources to improve page performance.
  • Frame TimingGroup Note
    Frame Timing helps web developers measure the performance of their applications by giving them access to frame performance data to facilitate smoothness measurements.
  • Server TimingWorking 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 2Working Draft
    This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.
  • PreloadCandidate Recommendation
    This specification defines the relationship of the HTML Link Element (). preload<link>
  • Cooperative Scheduling of Background TasksProposed Recommendation
    The requestIdleCallback method is a more appropriate way for scheduling background tasks during times when the browser would otherwise be idle.
  • Reporting APIWorking 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 2Proposed 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 2Recommendation
    This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
  • Resource Timing Level 2Working Draft
    This specification defines an interface for web applications to access the complete timing information for resources in a document.
  • Long Tasks API 1Working 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 1Working 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 MemoryWorking 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 3Working 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 RegistryWorking 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.