AnalyticsVS
Menu

Methodology

How AnalyticsVS sources pricing data, writes comparisons, and records script performance benchmarks.

Editorial independence

AnalyticsVS is an independent comparison site. We are not owned by any analytics vendor. Some links are affiliate links (see our disclosure page), but affiliate relationships do not influence our comparisons or benchmark results.

Tool review methodology

Each tool review declares a review scope — the exact product edition we are evaluating. Vendors often ship related products under one brand (for example, hosted SaaS vs a self-hosted “Lite” edition). We document those as variants so comparisons do not conflate them.

  • Feature checklists and pricing tables reflect the primary product unless a variant is explicitly noted.
  • Self-hosted variants require a dedicated vendor source URL and appear on the tool review page.
  • Build-time checks flag reviews that deny capabilities a documented variant provides.

Comparison methodology

Each "X vs Y" comparison is built from our verified tool reviews. We lead with a direct verdict, assemble side-by-side fit, pricing, setup, and limitations from those reviews, and add comparison-specific FAQ and bottom-line judgment where automation cannot replace editorial context.

  • Both tools in a comparison must have a published review before the page ships.
  • Head-to-head sections align review topics by dimension (privacy, scope, deployment, etc.).
  • Feature data is sourced from vendor documentation and verified manually.
  • Pricing data is checked against vendor pricing pages and dated on each profile.
  • We note when a tool is better for a specific audience rather than declaring universal winners.

Pricing calculator methodology

The pricing calculator uses published vendor tier data stored in our tools directory. Each tool has its own pricing model:

  • Pageview-based (Plausible, Fathom): tier lookup by monthly pageviews.
  • Free tier (GA4, PostHog): free up to published limits.
  • Session-based (Hotjar): estimated from pageviews with stated assumptions.

Calculator results are estimates. Vendor pricing changes, promotional offers, and annual billing discounts are not always reflected. Always confirm on the vendor's website.

Benchmark methodology

Script performance benchmarks are recorded by AnalyticsVS on controlled test pages hosted atbench.analyticsvs.com. We measure transfer size, decoded body size, and main-thread blocking time under defined network and device conditions.

Fixture: minimal-v1

  • Page: static HTML only — no fonts, images, frameworks, GTM, or consent managers.
  • Install: vendor default eager <script> snippet in <head>.
  • Network: Fast 4G (150ms RTT, 1.6 Mbps down) via Chromium CDP.
  • Runs: 7 cold navigations per tool; published values are arithmetic means.
  • Scope: initial page load only (first 5 seconds after load), not SPA navigation or session replay over time.
  • We never publish estimated, scraped, or AI-generated performance numbers.
  • Benchmarks marked "pending" have not yet been recorded.
  • Each published benchmark includes the test date and environment details.
  • Raw JSON run files are stored in the repository under benchmarks/results/ when published.

Updates and corrections

Analytics tools change frequently. Each page shows a "last updated" date. If you find inaccurate information, please reach out so we can correct it.