Benchmarks you can verify
Numbers this site measured itself, with the method and the raw data published next to them. Every figure on these pages is rendered from a source file in the repository, so a stale or hand-typed number cannot slip in unnoticed.
Zero-upload evidence
Every tool page was driven through one typical operation in a real browser while the network was recorded. The table lists the requests each page actually made and how many of them carried your input.
OpenWeb Crypto benchmark (run it yourself)
AES-GCM, PBKDF2 and the SHA digests, measured live in your own browser. The results stay in your browser, can be downloaded as JSON, and are never uploaded.
OpenWhat this proves
Each tool was driven through one typical operation in a real browser while the network was recorded. In every measured row, no request carried the test input. That is a measurement of this build, not a promise about every future build.
What it does not prove
A row covers the operation named in it, not every possible use of the tool. Two format pages could only be measured at page load because the repository has no fixture in the right input format; that reduction is published instead of a guessed number.
How to reproduce it
The zero-upload page lists the method, the environment and the raw table. The Web Crypto benchmark runs in your browser, keeps the results on your device and never uploads them.
Every figure comes from a published source file. A build check fails if a page shows a figure that is not in that file.