Evidence methodology

No borrowed benchmark becomes our test

Web Host Lens is a secondary-research publication. Findings stay attached to their author, tested configuration, observation period and limitations; official claims and independent observations are never merged into a synthetic fact.

Primary product and contractIndependent observed testsCommunity issue signalsExplicit uncertainty

Research pipeline

  1. 01

    Define the decision

    Write the buyer question and the minimum facts needed to answer it.

  2. 02

    Capture primary evidence

    Use the provider’s current pricing, terms, policy and documentation for product claims.

  3. 03

    Seek independent evidence

    Prefer disclosed plan, region, workload, method, dates and raw or repeated observations.

  4. 04

    Normalize cautiously

    Convert units or ownership periods only when the original amount, currency and assumptions remain visible.

  5. 05

    Triangulate

    Explain conflicts by plan, location, time, cache, workload or method before considering aggregation.

  6. 06

    Draft with boundaries

    Attribute findings and state what the evidence cannot establish.

  7. 07

    Review and date

    Check links, product identity, arithmetic, commercial relationships and expiration triggers.

  8. 08

    Update transparently

    Append material observations and correct errors with a visible date rather than rewriting history silently.

Evidence taxonomy

Different sources answer different questions

Authority and independence are separate dimensions. Provider terms can be authoritative for a refund rule while being unsuitable evidence of comparative performance.

Official commercial

Price, term, renewal and included product. Capture market and date.

Official contractual

Eligibility, exclusions, remedy and procedure. Quote sparingly and link directly.

Official technical

Supported features and documented procedures, not proof of real-world outcomes.

Independent test

Observed result for the disclosed setup and interval; do not generalize beyond it.

User survey

Perception from a defined sample; inspect recruitment, sample size and question wording.

Community report

A lead for investigation, not incidence, prevalence or a provider-wide conclusion.

Benchmark acceptance record

Configuration

Provider, product, plan, region, runtime, resources and account age

Required before comparative use
Workload

Application, dataset, cache state, request path, concurrency and test origin

Required before comparative use
Window

Start/end dates, run frequency, warm-up and excluded incidents

Required before comparative use
Metrics

Definition, collection tool, percentile or average and missing data

Required before comparative use
Independence

Funding, affiliate relationship, supplied account and editorial control

Required before comparative use
Limitations

What changed, what was not tested and where the result should not be generalized

Required before comparative use

Conflict and expiry

Uncertainty is part of the result

When credible sources conflict, retain both, inspect configuration and time differences, and narrow the claim. Recheck price and promotional terms frequently; recheck policies after a terms revision; retire performance evidence when the tested plan, platform or method changes materially.

Correction rule

Fix factual or arithmetic errors promptly and state the corrected observation date.

Affiliate rule

Commercial links must not change eligibility rules, evidence treatment or conclusions.

No score laundering

Do not average incompatible benchmarks, star ratings and contract facts into a precise-looking score.

No firsthand implication

Secondary testing is attributed to its publisher; Web Host Lens does not claim it ran the test.

Inspect the current evidence register

Open evidence lab →