Reading your scores

Higher scores mean faster performance. Each detailed test runs three times, and its median is converted to a score. Category and overall scores combine these results into a balanced average. Even on the same device, the browser, power settings and heat can change the result, so compare runs under the same conditions. Open the category details to see which workloads contributed to a result and which were skipped. Higher throughput and lower latency both lead to higher scores. A change in the total does not guarantee the same change in every application. Repeat runs after the device has cooled, and keep the measurement mode, supported tests and optional AI selection consistent when comparing results.

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.