w3c / perf-timing-primerLinks
A Primer for Web Performance Timing APIs
☆21Updated 4 years ago
Alternatives and similar repositories for perf-timing-primer
Users that are interested in perf-timing-primer are comparing it to the libraries listed below
Sorting:
- User Timing☆27Updated 5 months ago
- Web Performance Group charter☆27Updated 6 years ago
- Page Visibility☆36Updated 3 years ago
- Performance Timeline☆113Updated last month
- Finding on polyfills☆19Updated last year
- Reporting API☆80Updated 3 weeks ago
- UX Speed calculator☆12Updated 2 years ago
- ☆41Updated 5 years ago
- Beacon☆50Updated 5 months ago
- Resource Hints☆81Updated 2 years ago
- Battery Status API☆24Updated 8 months ago
- Working Group effectiveness Task Force☆39Updated 10 months ago
- Performance APIs, Security and Privacy☆11Updated 4 years ago
- Temporary documentation for developer features in the Chrome beta, canary, and dev channels.☆27Updated 8 years ago
- A proposal for an Event Timing specification.☆45Updated last month
- ☆28Updated 3 years ago
- Device Memory☆68Updated 5 months ago
- Proximity☆13Updated 5 months ago
- Preload☆82Updated 3 years ago
- The screen orientation lock specification☆28Updated 9 months ago
- Playground for better understanding Web APIs☆19Updated 4 years ago
- Service and API for Web API Confluence: Metrics for web platform health☆92Updated 2 weeks ago
- Documenting the state of the extensible web☆36Updated 9 years ago
- Sources for http://testthewebforward.org/☆10Updated 8 years ago
- [On hold for now] A mechanism for origins to set their origin-wide configuration in a central location☆34Updated 3 years ago
- Explainer and spec for the Content Indexing proposal☆30Updated 4 years ago
- An application to create nodejs.org distribution index files: index.json and index.tab☆19Updated last month
- Up-to-date listing of Google Chrome's latest versions across stable, beta, dev and canary☆56Updated 7 years ago
- Document describing the process for making changes to ECMA-262☆30Updated 5 months ago
- A JavaScript client for the W3C API☆29Updated this week