Method 2.0
Scores you can understand—and challenge.
A browser score is only useful when its method is visible. Here is exactly what method 2.0 runs, how eligible measurements are combined, and where the limits are.
Calibrate, sample, median
Performance calibrates first and records five samples. Frame and network phases use robust timing summaries rather than one reading.
Run sequentially
CPU, rendering, display, network, and audit work never run together and distort each other.
Record the context
Every saved run includes method version, browser, platform, viewport, display, and exposed capability hints.
Score model
Five reports. Eligible signals form the overall score.
Method 2.0 calculates the overall score from supported results marked eligible, then rebalances the reference weights across those results. Accessibility is reported separately, private-LAN network measurements are excluded, and display cadence is excluded when browser automation is detected. Coverage is shown separately and describes how many selected domains produced a result.
| Domain | Reference weight | Overall use | Measured signals |
|---|---|---|---|
| Performance | 30% | Included when measured | Five calibrated fixed-seed JavaScript samples. |
| Gaming | 25% | Included when measured | Visible Canvas 2D FPS, 1% low, and frame-pacing stability. |
| Network | 20% | Public-server runs only | Eight round trips and an adaptive uncached payload transfer. |
| Display | 15% | Excluded under automation | Visible browser presentation cadence and timing stability. |
| Accessibility | 10% | Reported separately in method 2.0 | Custom audit of the current Test page and exposed preferences. |
Measured phases
What actually runs—and for how long.
A full method 2.0 run usually takes about 14–25 seconds. Device speed, frame scheduling, server distance, and transfer rate can make it shorter or longer.
- PerformanceAbout 3–5 seconds
- Worker calibration followed by five fixed-seed samples; the median throughput drives the score.
- GamingAbout 5 seconds
- A 650 ms unloaded baseline followed by three 1.4-second visible Canvas 2D workload levels.
- DisplayAbout 3 seconds
- A 500 ms warm-up followed by 2.5 seconds of visible requestAnimationFrame intervals.
- NetworkUsually 2–10 seconds
- A warm-up, eight same-origin round trips, 512 KB calibration, and an adaptive 2–16 MB transfer. Slow routes can take longer.
- AccessibilityUnder 1 second
- A custom DOM audit of this page's controls, names, landmarks, headings, targets, language, and exposed preferences.
Reliable comparisons
Control what you can.
- Use the same browser window size and zoom.
- Keep the tab visible and avoid moving the window.
- Close heavy applications, streams, and background tabs.
- Use the same plugged-in or battery power mode.
- Run two or three times and compare the middle result.
Test measures a browser session, not the maximum native capability of a CPU, GPU, display, or internet plan. Canvas FPS is limited by browser presentation cadence. Thermal state, battery policy, extensions, server distance, VPNs, browser throttling, variable refresh rate, and background work can all change a result.
Network results describe the route to the server hosting Test; localhost and private-LAN measurements are reported but excluded from the overall score. Accessibility is a custom automated audit of the current Test page and exposed preferences. It does not certify WCAG compliance or score a person’s needs.
Ready for a controlled run?
The dashboard records method 2.0 and the browser context with every result.
Open the browser lab