Web Bench
☰

No installation. Right in this browser.

Measure your device with real workloads.

Measurements run on your device. The latest 20 results stay in this browser and can be removed by clearing site data. Share results as PNG cards or links. Results are sent to the server only when you agree to ranking registration.

Start measurement ↗Quick benchmarkStress test
  • 58 detailed tests
  • No installation
  • Opt-in rankings

How to use it

  1. On the test screen, choose a quick test, a standard test or a stress test.
  2. Press Start and keep the tab in front until the test finishes.
  3. Check your score and per-category results, then save a PNG card or compare with your recent history.

Browser battle

Switch browsers on the same device to compare scores and execution environments side by side.

Start measurement ↗

What does it measure?

CPU single-core

CPU Single measures how fast one core finishes real-world work such as text processing, JSON parsing, compression, hashing, image processing, sorting, pathfinding, physics simulation, ray tracing and linear algebra. Page loading, app responsiveness and programs that do one thing at a time tend to feel close to this value. The unit is operations per second, so higher means more work done in the same time. Tests that need browser APIs such as AES-GCM or Deflate are skipped when unsupported, and the score is calculated from the remaining tests.

CPU multicore

CPU Multi runs the same kind of work split across several Workers to measure throughput when cores work together. You notice the difference in video encoding, large file processing and when running many tabs and apps at once. The unit is operations per second and higher is better. However, results depend on how many Workers the browser uses and how it synchronizes them, so do not read them purely as a physical core count. Tests that rely on encryption or compression APIs are skipped where those APIs are unavailable.

Memory

Memory looks at the throughput of reading, writing and copying a contiguous 16 MB block, along with the latency of chasing data through random access. It relates to heavy data movement such as editing large images or video, keeping many tabs open and loading games. Throughput is in GB/s, so higher is better, while random access latency is in ns, so lower is better. Because access sizes are varied, you can also tell where speed changes across the cache hierarchy.

GPU graphics

GPU Graphics renders large numbers of triangles, 131,072 particles and bloom and blur post-processing off-screen and measures the average FPS. It relates to how smoothly web games, 3D maps and effect-heavy pages run. The unit is FPS and higher is better. If WebGPU is unavailable, the test may run on the WebGL2 path instead, and if neither is available this category is skipped.

GPU compute

GPU Compute measures speed when you hand calculations, not graphics, to the GPU. It runs f32 and f16 matrix multiplication, image convolution, particle simulation and parallel sums, and also verifies that the result buffers are correct. It is closest to heavily parallel work such as in-browser video processing and AI inference. Matrix multiplication is shown in GFLOPS and the rest in elements processed per second, and higher is better for all of them. Without WebGPU or the shader-f16 feature, the affected tests are skipped.

Browser

The Browser category measures DOM manipulation and layout, Canvas 2D drawing, screen refresh rate and frame consistency. It maps directly to everyday experience such as how responsive a complex web app feels and how smooth scrolling and animation are. DOM and Canvas are in operations per second, so higher is better, while frame intervals are in ms, so lower is better. These tests depend heavily on the browser engine and display settings as well as hardware, so compare results within the same browser.

Storage

Storage creates a temporary file in the browser's OPFS to measure sequential write, sequential read, random write and random read speed, then deletes the file when finished. It relates to downloading large files and loading offline app data. The unit is MB/s and higher is better. If the browser does not support OPFS or it is blocked, for example in a private browsing mode, this category is skipped.

AI inference (optional)

AI inference is optional and runs only if you agree to download the models. It feeds fixed test sentences and images to measure how fast text generation and image models run inside the browser, and it never uses your personal files. It is a reference for how smooth on-device AI features might feel, and a higher processing speed is better. If you do not agree, it is not run and is left out of the total score. If WebGPU is unavailable it runs on the WASM path instead, and that is shown separately.

How to read scores

Higher scores mean faster performance. Each test runs three times, and its median is converted to a score. Category and overall scores combine these scores using a balanced average. Scores are reference values affected by browser, power mode and heat. Close other apps, connect power and keep this tab visible. Measurement pages have no ads.

Performance Guides