Evidence before rankings
Controller performance is easy to summarize and difficult to compare fairly. A drift complaint may depend on software settings; a button-life number may depend on a narrow cycle protocol; an input delay may include an entire display pipeline. We make those boundaries visible. Our guides explain what a test observes, what it cannot establish and which conditions a reader should preserve when repeating it.
We are not affiliated with controller manufacturers, game publishers or platform holders. Product names, when discussed, identify the equipment being examined and do not imply endorsement. We do not treat a player’s report as laboratory evidence, or a laboratory result as a universal account of play. Both can be valuable when their scope is clear.
How the ledger is organized
The pathway follows a controller through states and use: establish a baseline, look for unexpected neutral movement, examine repeated contact, define the timing chain and consider sustained hand fit. The order is editorial rather than a claim that one failure mode causes another. Each guide pairs cause-and-confounder definitions with a test protocol, so a reader can distinguish the intended variable from other influences.
We prefer direct observations, repeated trials, stated sample counts and retained notes. When a method has uncertainty, we say so. A result may be inconclusive; that is not a reason to omit it. It is a reason to explain what additional measurement would help. Images are component-level illustrations that support explanation and do not imply a tested device was opened or found defective.
What repeatability means here
Repeatability is not the promise that every future test will produce an identical number. It means that the procedure is described well enough to be repeated, that variation is not hidden and that changes to the setup are documented. Whenever practical, compare multiple readings and maintain one baseline. Change one condition at a time when looking for a likely influence. Keep raw observations so summaries can be checked.
Our approach borrows the discipline of measurement without pretending every question can be reduced to a laboratory instrument. Ergonomic comfort includes subjective response; the correct approach is to record it carefully, not to discard it. A bench protocol can standardize a task while still leaving room for different hands and experiences.
Reader contributions
Readers can prepare a Bench Note through the contact page. The tool builds plain text in the browser and offers copy or download; it does not send a message. Include controller and platform details, the exact symptom, test conditions, repetition count and what changed between runs. Avoid including sensitive personal information. If a note is used to inform future editorial work, its claim will be checked against the available evidence and described with appropriate context.
We welcome corrections that identify a specific passage, method or factual error. A clear correction is more useful than a broad disagreement: cite the page, state the issue and, where possible, provide a source or repeatable observation. Editorial changes should improve accuracy and preserve the distinction between a result and its interpretation.
Scope and independence
This site offers educational material, not repair instructions or a guarantee of device condition. Hardware varies, and safe procedures depend on the equipment and the person performing them. Our published methods are intended to encourage careful observation rather than replace manufacturer guidance or qualified technical evaluation.
The central rule is simple: explain the conditions, show the evidence, mark uncertainty and avoid claiming more than the test supports.
Questions about the editorial approach are welcome through Contact. The legal pages explain how correspondence and site preferences are handled.