Manual-sync mirror of chromium.googlesource.com/external/github.com/WebKit/Speedometer.git
Find a file
2023-03-08 20:33:42 -08:00
.github/workflows Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
resources Initial dev mode param implementation (#89) 2023-03-08 20:33:42 -08:00
tests Use performance.measure api instead of manually tracking with performance.now() (#79) 2023-02-27 12:53:55 -08:00
.eslintignore Todomvc es5 updates (#82) 2023-03-07 14:58:05 -08:00
.eslintrc Adding prefer-template rule to Eslint (#66) 2023-02-13 11:54:51 -08:00
.gitignore Todomvc es5 updates (#82) 2023-03-07 14:58:05 -08:00
.npmrc Dev setup (#55) 2023-01-30 14:52:46 -08:00
.prettierignore Todomvc es5 updates (#82) 2023-03-07 14:58:05 -08:00
.prettierrc Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Development.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Governance.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
index.html Update titles to "Speedometer 3.0" (#75) 2023-02-21 19:56:47 +01:00
InteractiveRunner.html Update titles to "Speedometer 3.0" (#75) 2023-02-21 19:56:47 +01:00
LICENSE Update LICENSE (#64) 2023-02-10 20:09:27 -08:00
package-lock.json Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
package.json Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
README.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Testing.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00

⚠️ 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.