Differences between browsers

A browser benchmark includes the browser engine and security policy as well as hardware. JavaScript optimization, WebAssembly SIMD, worker scheduling, timer precision and graphics drivers can differ. A lower browser score does not directly describe a slower physical CPU. OPFS, encryption or compression APIs may be restricted and tests excluded. WebGL2 graphics and WASM AI are different execution paths from WebGPU. Check the support information before comparing. Use the same power and cooling conditions, record browser versions and extensions, and avoid running two browsers simultaneously. Private browsing can also change storage policy. Alternate repeated runs to avoid always testing one browser on a colder device.

Before measuring, write down the conditions you want to compare: operating system and browser versions, power connection, energy mode, external display and device model. Wait for downloads, video playback, backups and updates in other apps to finish. Keep the screen on and this tab visible throughout the run. Hiding the tab discards the current round and repeats it when you return, so frequent interruptions create different conditions from a continuous run.

Repeat the measurement two or three times under the same conditions and look at the range rather than selecting only the highest score. Allow the device to return to a comparable state between runs. If a small difference changes direction on repetition, treat it as variation rather than proof of superiority. Check valid test counts and exclusion reasons too. Missing support does not necessarily indicate defective hardware, but it changes what the overall score summarizes.

Change one condition at a time. Changing the browser, power mode and cooling together makes it hard to identify the cause of a difference. Use quick mode to check that the test runs, then use full mode for detailed comparisons. When sharing, include score version, mode, GPU backend and whether AI was included. Read the raw units: higher throughput is usually better, while lower latency is better. Normalized scores account for that direction. Rounded display digits alone cannot establish an improvement. These measurements describe web workloads; they do not guarantee game frame rates, battery life or performance in every desktop application.

Share a result and open its link in another browser on the same device. Select Benchmark this browser and compare to use the same benchmark mode. Compare categories, detailed values and environments in the battle card, keeping power and thermal conditions consistent.