Cold-Air-Networks/mirror-speedometer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Manual-sync mirror of chromium.googlesource.com/external/github.com/WebKit/Speedometer.git
17 commits 14 branches 0 tags 53 MiB
Find a file
Camillo Bruni ef8d58c988
Fix interactive runner (#31) 
* Make the client callbacks async
* Move the interactive runner into a separate interactive.mjs module
* Update code to use URLSearchParams instead of custom parsing
2023-01-25 13:10:55 +01:00
resources Fix interactive runner (#31) 2023-01-25 13:10:55 +01:00
.gitignore Create a new Speedometer repository 2022-05-16 21:31:43 -07:00
Governance.md Add Speedometer Governance Policy (#10) 2022-07-28 20:09:12 -07:00
index.html Convert to ES6 Modules (#19) 2022-10-31 10:28:25 +01:00
InteractiveRunner.html Fix interactive runner (#31) 2023-01-25 13:10:55 +01:00
LICENSE Reviewed by Addy Osmani and Jonathan Bedard. (#2) 2022-06-29 11:40:19 -07:00
README.md Add development notice (#25) 2022-11-03 16:24:07 -07:00

README.md

⚠️ Speedometer 3 is in active development and is unstable. You can follow along with development in this repository, but see Speedometer 2.1 for the latest stable version.

What is Speedometer?

Speedometer is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads. Our primary goal is to make it reflect the real-world Web as much as possible. When a browser improves its score on the benchmark, actual users should benefit. In order to achieve this, it should:

  • Test end-to-end user journeys instead of testing specific features in a tight loop. Each test should exercise the full set of what’s needed from the engine in order for a user to accomplish a task.
  • Evolve over time, adapting to the present Web on a regular basis. This should be informed by current usage data, and by consensus about features which are important for engines to optimize to provide a consistent experience for users and site authors.
  • Be accessible to the public and useful to browser engineers. It should run in every modern browser by visiting a normal web page. It should run relatively quickly, while providing enough test coverage to be reflective of the real-world Web.