Manual-sync mirror of chromium.googlesource.com/external/github.com/WebKit/Speedometer.git
Find a file
2023-05-24 10:51:30 -07:00
.github/workflows Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
resources use home link (#182) 2023-05-24 10:51:30 -07:00
tests position iframe (#170) 2023-05-19 16:29:25 -07:00
.eslintignore Tentative Workload: Embed TodoMVC-React in a big DOM with complex CSS. (#150) 2023-05-24 10:50:04 -07:00
.eslintrc Todomvc angular update / cleanup (#142) 2023-05-12 09:19:16 -07:00
.gitignore Add a new charting workload using observable plot (#144) 2023-05-15 13:27:53 -07:00
.npmrc Dev setup (#55) 2023-01-30 14:52:46 -08:00
.prettierignore Tentative Workload: Embed TodoMVC-React in a big DOM with complex CSS. (#150) 2023-05-24 10:50:04 -07:00
.prettierrc Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
babel.config.json Ember - Step 2 - format from root / cleanup (#119) 2023-03-30 18:13:18 +02: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 Add detailed JSON downloads (#146) 2023-05-23 19:57:15 +02:00
InteractiveRunner.html adding favicon (#111) 2023-03-16 20:50:14 +01:00
LICENSE Update LICENSE (#64) 2023-02-10 20:09:27 -08:00
package-lock.json Todomvc angular update / cleanup (#142) 2023-05-12 09:19:16 -07:00
package.json Todomvc angular update / cleanup (#142) 2023-05-12 09:19:16 -07: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.