Microsoft Announces More Web Performance APIs Now W3C Candidate Recommendations

In a recent post on the IEBlog, Microsoft unveiled that three more W3C Web Performance Working Group specifications have become W3C Candidate Recommendations.

Starting with this month, the User Timing, Performance Timeline and Page Visibility specifications have become Candidate Recommendation (CR).

Following this stage of standardization, the three specifications should become Proposed Recommendation (PR).

“This stage of standardization is prior to the PR stage and reflects that the W3C believes this specification has been widely reviewed and satisfies the Working Group's technical requirements,” Jatinder Mann, program manager, IE Performance, explains.

“Resource Timing was published as CR just two months ago, along with High Resolution Time, which went from an Editor’s Draft to CR in just three months.”

Additionally, there is the Navigation Timing specification that has been published as a Proposed Recommendation (PR) this month.

This is the final step of standardization before the specification becomes an official W3C Recommendation.

“Additionally, this interface has been broadly adopted in browsers, including support since Internet Explorer 9, Chrome 6 and Firefox 7. The working group recently started incorporating feedback and working on Navigation Timing 2, the next version of the specification,” Mann continues.

He also explains that these APIs can be given as great examples of how fast new ideas can become interoperable standards that developers can leverage in HTML5-enabled browsers.

All four specifications have been designed to provide developers with the possibility to more accurately measure the performance of Web applications.

The first three of them were meant to provide developers with info on navigation of documents, page resources, and developer scripts, respectively.

As for the Performance Timeline specification, it was designed to deliver a unifying interface for timing data. Developers did not have the option to accurately measure the performance of their sites before the APIs.

“Accurately measuring the performance characteristics of Web applications is critical to making the Web faster. In addition, developers need the ability to effectively use the underlying hardware to improve the performance of their a pplications,” Mann explains.

“Over the last two years, companies including Microsoft, Google, Mozilla, Intel, and Facebook have been working toward these goals through the working group. This is a great example of what’s possible when the industry and community come together through the W3C.”

Via: Microsoft Announces More Web Performance APIs Now W3C Candidate Recommendations