Skip to main content

Last updated: · Author: Daniel Rozin

How We Test & Score Web Browsers

This page describes every attribute, data source, and editorial decision behind the browser comparison guide.

1. Scoring dimensions

AttributeWhat we measurePrimary source type
Engine / rendererRendering engine, JavaScript engineVendor developer docs / Chromium blog / MDN
Version (current stable)Stable channel version numberVendor release notes (official blog or changelog)
PlatformsOS and mobile coverageVendor system-requirements or download page
Market shareDesktop + mobile % shareStatCounter GlobalStats (gs.statcounter.com), monthly
Privacy postureTelemetry defaults, tracker blocking, fingerprinting protectionVendor privacy whitepaper or policy
Extension ecosystemStore availability, estimated item countOfficial extension store front page (dated snapshot)
Memory usageRAM under standardized tab loadMethodology-disclosed independent benchmark (browserbench.org / Tom's Hardware)
Standards complianceWeb Platform Tests pass rate, Acid3 scorewpt.fyi dashboard (permalink snapshot)
Pricing / licenseCost to end-user, open-source statusVendor download page + GitHub license file

2. Data sources

  1. Tier 1: Vendor official documentation, release notes, or privacy whitepaper — cited with URL and access date.
  2. Tier 1: StatCounter GlobalStats for market share — monthly CSV download, methodology publicly disclosed at gs.statcounter.com/methodology.
  3. Tier 1: web-platform-tests.org (wpt.fyi) for standards compliance — open public dataset.
  4. Tier 2: Methodology-disclosed benchmark publications (Tom's Hardware, PCMag) for memory/performance data.
  5. Disallowed: SimilarWeb (panel bias, methodology undisclosed), G2/Capterra user scores, our own pages.
  6. Wikipedia and any Wikipedia mirror/fork — never a cite-worthy source for a cell value. The about.sameAs Wikipedia link (schema §1) is an entity reference only, never a citation. This prevents circular sourcing (WP:CIRCULAR).

3. Recency policy

Market share figures carry “as of [YYYY-MM]” labels referencing the StatCounter monthly data release. Version numbers are updated when a new stable channel release is announced. The page dateModified stamp reflects the last real-content edit.

4. Conflict-of-interest disclosure

A Versus B has no paid relationships with any browser vendor. No browser vendor reviewed or approved this guide before publication. Affiliate links, if present, are clearly labeled and do not influence any data or ranking.

5. Correction policy

Errors can be reported to contact@aversusb.net. Please include the specific claim, your correction, and a primary source. We aim to respond within 48 hours and publish corrections with a visible notice and updated dateModified.

CC-BY-4.0 covers aversusb.net editorial text and table layout; vendor names, logos, and marks remain the property of their owners.

← Back to browser comparison
How We Test Browsers — Methodology | A Versus B | A Versus B