YuvalGGYuvalGG

Tools

Processor test

Test your CPU in the browser: speed on one thread and on all threads, how well it scales across cores, how even the threads are, and whether it slows down when it gets hot. No download, nothing uploaded.

Processor test

Runs three fixed workloads in Web Workers, first on one thread and then on all threads. Everything runs in this tab; nothing is uploaded. Scores are relative and uncalibrated, not a Cinebench or Geekbench result.

Logical processors reported

Not reported

Test

Close games and heavy apps, keep this tab in front, then press Start.

Browser JavaScript is not native code, and the browser, power plan, battery mode, heat and background apps all change the result. Compare runs on the same browser and machine, before and after a change.

How to use the processor test

  1. Close games, video exports, big downloads and other heavy apps. Plug a laptop into power, because many laptops run slower on battery.
  2. Press Start quick test. Each of three workloads runs for 3 seconds on one thread, then for 3 seconds on all threads, about 18 seconds in total. Keep the tab in front: if you switch tabs, the test pauses, because browsers slow down background tabs. Press Resume to redo the step that was interrupted.
  3. Read the single-thread and all-thread scores, the scaling factor and the per-thread bars. The table shows the raw operations per second for each workload.
  4. Choose Stability test, pick 30, 60 or 120 seconds, and start it. Every thread runs a mixed workload and the chart shows how much work was done each second.
  5. Change one thing, such as the power mode, a cooler fan curve or a browser setting, and run the same test again. Comparing your own runs is where this page is most useful.

What the test measures

The page starts one Web Worker per thread. A Web Worker is a piece of JavaScript that runs on its own thread, so the browser can spread workers across your processor's cores. Each worker repeats a fixed piece of work and counts how many times it finishes in the time it is given:

  • Integer math mixes 32-bit numbers with shifts, multiplies and XOR, the kind of work behind hashing, compression and game logic.
  • Floating point steps a small orbit simulation with multiplies, adds and square roots, closer to physics and animation code.
  • Memory and branches finds every prime number below 120,000 with a sieve in a byte array, so it also depends on cache and on how well the processor predicts jumps in the code.

Single-thread speed is one worker on its own. It is the closest match to how fast one busy game thread can run. All-thread speed is every worker at once, which matters more for compiling code, encoding video, streaming while you play and running many apps at the same time.

Scaling is all-thread speed divided by single-thread speed. With perfect scaling, 8 threads would be 8 times faster than one, but real processors fall short of that: two threads on one core share it, cores share memory and cache, processors with performance and efficiency cores have threads of different speeds, and many processors run at a lower clock when every core is busy. The per-thread bars show each worker's speed during the all-thread run, compared with one worker alone.

The 0–100 score puts each workload on a log curve and averages them. The curve is relative and uncalibrated: it is not based on any named processor, and it is not comparable with Cinebench, Geekbench, PassMark or a game benchmark. Your browser matters too, so compare runs in the same browser. The exact model of your processor is not visible to websites; the system info page explains what a browser can and cannot see.

Is my CPU throttling? Reading the stability test

Processors run faster for short bursts than they can keep up under long loads, and they slow down when they reach a temperature or power limit. The stability test keeps every thread busy and compares the start of the run with the end. The first second is left out as warm-up. For a longer run of 2 to 10 minutes, with an optional GPU load on top, use the overheating / throttle test.

  • Steady line: the cooling and power limits keep up with this load. On a desktop with good cooling this is the usual result.
  • Drop after a few seconds, then flat: the processor boosted at the start, then settled at the speed it can sustain. Many laptops and small PCs do this by design. A large drop on a desktop is worth looking into.
  • Keeps falling, or jumps up and down: often heat, a dusty cooler, a fan curve that reacts late, or a power-saving mode. Background apps that wake up during the test also cause jumps.

What to check if the end of the run is much slower than the start:

  • Power mode. On Windows 11, open Settings, then System, then Power & battery, and set Power mode to Best performance while plugged in. Laptop maker apps often have their own performance or quiet modes as well.
  • Temperature. Watch the CPU temperature and clock speed in a hardware monitor such as HWiNFO while the stability test runs. If the temperature sits at its limit while the clock falls, cooling is the problem.
  • Overheating / throttle test — Load every thread for 1–10 minutes and see if the speed falls as it heats up.
  • Cooling and airflow. Clean dust from the cooler, the fans and the case filters, and make sure the case can pull in fresh air. My guides on gaming PC cooling, airflow PC cases and gaming laptop cooling go through this step by step.

What the result means for gaming

A browser test cannot tell you how many FPS a game will run at. In many games the graphics card is the limit, not the processor, and then a faster CPU changes little. When the CPU is the limit, usually at lower resolutions, high refresh rates or in big multiplayer fights, single-thread speed and cache tend to matter most, and you often see it first in the 1% low FPS rather than the average.

To check which part holds your FPS back, measure GPU and CPU usage in a game and put the numbers in the bottleneck estimator. Test the graphics side with the graphics test, and if an upgrade is due, my best CPU for gaming guide explains when a processor upgrade helps and when the money is better spent on the GPU. For free wins first, see how to increase FPS.

Common questions

Is it safe to run a CPU test in the browser?

Yes. The quick test loads the processor for about 18 seconds and the stability test for up to two minutes, which is similar to exporting a video or loading a big game. Processors protect themselves by slowing down when they get too hot. A laptop will get warm and its fans may speed up. You can press Stop at any time.

Why does the page show fewer threads than my CPU has?

The page can only use the number the browser reports as logical processors. Some browsers and privacy features report a smaller or rounded number, and this page never starts more than 64 workers. Windows Settings > System > About and Task Manager show the real model, cores and logical processors.

Can I compare my score with Cinebench or Geekbench?

No. This score comes from JavaScript workloads running in your browser and is mapped to 0–100 with a relative, uncalibrated curve. Native benchmarks run different code outside the browser. Use this page to compare your own runs on the same browser and machine, for example before and after changing the power mode.

Why is the all-thread result not the single-thread result times my thread count?

Several things share the work. Two threads on one core share that core, processors with performance and efficiency cores have threads of different speeds, all cores share memory and cache, and many processors run at a lower clock when every core is busy. Scaling well below the thread count is normal.

Why do my results change between runs?

Background apps, the power plan or battery mode, temperature, boost clock behaviour and the browser version all change the result. Run the test two or three times with the same apps open and look at the typical result, not the single best one.

Does a higher CPU score mean more FPS in games?

Not directly. Many games are held back by the graphics card, not the processor, and games use threads in very different ways. A faster single-thread result usually helps when the CPU is the limit. The bottleneck estimator helps you check which part is holding your FPS back.

Does the processor test work on phones and tablets?

Yes, in modern mobile browsers that support Web Workers. Phones are built to stay cool and slow down quickly under load, and battery saver modes cut speed a lot, so the stability test often shows a drop on phones. Nothing is uploaded on any device.

  • Sensitivity converter — Convert sensitivity between Overwatch, Valorant, CS2, and other titles using documented yaw values.
  • cm/360 calculator — Turn mouse DPI and in-game sensitivity into centimeters per 360° turn.
  • eDPI calculator — Multiply mouse DPI by in-game sensitivity for a same-game comparison number.
  • FOV converter — Convert horizontal and vertical FOV across 4:3, 16:9, 16:10, and 21:9. Includes Overwatch, CS2, and Valorant.
  • Frame-time and Hz calculator — Convert FPS to milliseconds, compare that wait to the monitor refresh, and read a 1% low as a frame time.
  • Mouse polling-rate tester — Measure how often the browser sees pointer events. Average and max Hz.
  • Mouse raw input test — See every mouse report as a dot, spot sensor skips, and check jitter, swipe speed, and acceleration.
  • Mouse test — Check mouse buttons, the scroll wheel, double-click chatter, and a pointermove polling-rate reading in the browser.
  • Keyboard test — Press keys on a US QWERTY board, then time your typing on real sentences or random letter strings.
  • Gamepad test — See every controller button, analog trigger and stick live, check stick drift with a suggested deadzone, and test vibration.
  • System info — OS, browser, GPU, CPU threads, RAM and screen your browser reports.
  • Memory test — RAM read, write and copy speed, latency and a cache-step chart.
  • Graphics test — Detect your GPU and run a relative WebGL2 benchmark.
  • Bottleneck / FPS estimator — Check if the CPU or the GPU holds your FPS back, from usage you measured.
  • GPU compare — Put two graphics cards side by side with sourced specs.
  • PSU wattage calculator — Add up CPU and GPU power before an upgrade.
  • Best CPU for gaming — Which processor to pick if yours is holding the GPU back.

Comments

No comments yet. Be the first to share what you think.