This page is In Progress

Notice: The WebPlatform project, supported by various stewards between 2012 and 2015, has been discontinued. This site is now available on github.

Timing and performance standards

Summary

This section documents the timing and performance-based standards supported by Windows Internet Explorer and Windows Store apps.

Navigation Timing

Abstract

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

The Navigation Timing API basically provides timings of all things going on from initiating navigating to another document (e.g. clicking a link, settings location.href) until the end of document onload event.

  • Navigation Timing API Recommendation [1] (17 December 2012)
  • Tutorial: Measuring page load speed with Navigation Timing [2]
  • Browser Support: FF7+, Chrome6+, IE9+, Android Browser 4.0+, Mobile Chrome 33+ [3]
  • Polyfill: [4]

Resource Timing

Abstract

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

The Resource Timing API provides timings for all resources linked into a page.

  • Resource Timing API Candidate Recommendation [5] (25 March 2014)
  • Tutorial: An Introduction to the Resource Timing API [6]
  • Browser Support: FF15+, IE10, Chrome? (2012)

User Timing

Abstract

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

Helps to get rid of Date.now() in performance measuring code. Can be used to measure random parts of code.

  • User Timing API Recommendation [7] (12 December 2013)
  • Tutorial: User Timing API [8]
  • Polyfill: [9]
  • Browser Support: IE10+, Chrome25+, Android Browser 4.4+, Mobile Chrome 33+ [10]

Page Visibility

Abstract

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.

Enables developers to listen to visibility change event (e.g. user switches to another browser tab) and to determine visibility state of the page. Thus, expensive operations in means of performance can be stopped on invisible pages.

  • Page Visibility API Recommendation [11] (29 October 2013)
  • Tutorial: Using the PageVisibility API [12]
  • Browser Support: FF10+, IE10+, Chrome14+, Safari 6.1+, mobile Safari 7+, Android Browser 4.4+, Mobile Chrome 33+ [13]

Animation Timing

Abstract

This document defines an API web page authors can use to write script-based animations where the user agent is in control of limiting the update rate of the animation. The user agent is in a better position to determine the ideal animation rate based on whether the page is currently in a foreground or background tab, what the current load on the CPU is, and so on. Using this API should therefore result in more appropriate utilization of the CPU by the browser.

  • Animation Timing API Recommendation [14] (31 October 2013)
  • Tutorial: The secret to silky smooth JavaScript animation! [15]
  • Browser Support: FF4+, Chrome10+, Safari 6+, mobile Safari 6+, Android Browser 4.4+, Mobile Chrome 33+ [16]

Efficient Script Yielding

Abstract

This specification defines an interface for web applications to flush the browser event queue and receive an immediate callback.

  • Efficient Script Yielding Editor’s Draft [17] (editor’s draft, 28 July 2011)
  • Browser Support: IE10+

In this section

{

Attributions