A recommendation is only as useful as the evidence behind it. We label what we tested, what we researched, the conditions that shaped the result, and what remains unknown.
Three evidence labels
Hands-on testedThe contributor used the product or game and the page states the relevant configuration, duration, and conditions.
Researched, not testedThe recommendation is based on specifications, primary documentation, reputable measurements, and clearly attributed sources.
Editorial prototypeThe page demonstrates structure only. It remains excluded from search indexing until its evidence and sourcing are complete.
Manufacturer claimA vendor statement is identified as a claim and never presented as our measured observation.
Our common test rules
- Record the hardware configuration, operating system, driver, firmware, game build, resolution, and preset that can affect the result.
- Establish a baseline and change one meaningful variable at a time.
- Repeat measurements and report variability instead of selecting the best run.
- Separate average performance from frame-time consistency, 1% lows, latency, noise, thermals, and power where relevant.
- Explain limitations, failed fixes, and what evidence would change the conclusion.
Updates and corrections
Meaningful retests receive a modified date and a visible explanation. Routine copy edits do not make an old result look new. Errors can be reported through our contact page and are handled under the corrections policy.