ReflexTimer

Editorial team & standards

Last updated: November 7, 2026

ReflexTimer is an independent, browser-based testing site. It is run by a small editorial and engineering team rather than by a laboratory or a media company; read more about the site. This page explains who is responsible for what we publish, how the tests are built and checked, how the articles are researched, and how we handle corrections.

What we publish

We publish two kinds of pages. The first are interactive tests: the reaction time test, CPS test, aim trainer, ruler drop calculator, number memory test, spacebar clicker, and the embeddable widget. The second are explanatory articles about reaction time, measurement error, age, training, and the tools people use to compare themselves.

Our goal is narrow on purpose: give a visitor a trustworthy personal measurement in the browser, and explain what that measurement does and does not mean. We do not sell supplements, coaching, or medical services, and we do not publish content solely to fill a keyword.

Author and operator

This site is written and operated by the independent publisher behind github.com/oogwaaay. The work includes the browser tests, the scoring logic, the editorial pages, and the corrections process. The operator is the responsible party for everything published here.

Public identity: oogwaaay is the owner-selected public byline for this site; the legal name is not published. That choice is recorded here for transparency and can be revisited by the owner at any time.

We do not publish a legal name or a personal biography on the public site, and we do not claim credentials we do not hold. What we can verify is the work itself: the test code is inspectable in the browser, the guides cite their sources, the correction process is public, and the contact address reaches the operator. If a named author or specialist reviewer joins, their name, relevant background, and disclosure will appear here before their byline is used.

Who is responsible

ReflexTimer is operated by an independent publisher. The operator is accountable for what is published here and can be reached at Contact. We publish under a team byline rather than individual personal names, and we do not claim medical, clinical, or academic credentials that we do not hold. If a named author or specialist reviewer joins the site, their biography, relevant credentials, and disclosure will appear on this page before their byline is used.

That is a deliberate honesty choice, not an attempt to avoid accountability: the operator is the responsible party, corrections are handled through the process below, and every page carries a review date.

How the tests are built and checked

Every test runs locally in the browser. Scores are calculated from performance.now() timestamps and the same arithmetic shown on the page. Before a test ships, we run functional checks on desktop and mobile: start and reset paths, early clicks, multiple rounds, history storage, keyboard and pointer input, and the behaviour of the result panel. We also keep a regression record for changes that touch scoring, timers, or input handling.

We do not treat a browser score as a laboratory measurement. Display refresh, input polling, browser scheduling, and the operating system's compositor all contribute latency, and we state that limitation on the test pages rather than hiding it. Where we compare scores across devices or against published research, the comparison is labelled as approximate and the source is cited.

How articles are researched

Numbers in our articles are drawn from peer-reviewed papers, published reviews, or clearly identified public data sets. We link to the source so a reader can check it. Where the evidence is mixed, we say so; where a popular claim outruns the evidence, we say that too. Numerical ranges used across several pages (for example, the typical adult reaction time range of 200–250 ms, the age bands, and the ruler-drop physics) are kept consistent across the site and reconciled when one page changes.

We avoid inventing statistics about our own audience. When a page mentions site-wide results, it is showing an actual server-side count; when there is not enough data, the page says so instead of presenting an empty sample as a distribution.

AI tools and human review

We use software, including AI-assisted drafting and checking tools, to help produce and review pages. Those tools do not get the final word: factual claims are checked against the cited sources, test behaviour is checked in a real browser, and every page is reviewed before publication. We do not publish AI-generated pages that have no independent review or no verifiable source. If a page contains an error, the correction policy below applies regardless of how the draft was produced.

Independence and funding

The site is free to use. It currently carries no advertising. If advertising is added in the future, it will be disclosed on the page and in the privacy policy, and advertisers will have no influence over test results, ratings, or editorial conclusions. The embeddable widget is free and carries a visible credit line; we do not sell white-label versions that remove attribution.

Corrections and updates

If you find a factual error, a broken source, or a test that behaves differently from its description, email hello@reflextimer.com with the URL and what you observed. We will check it, correct the page if needed, and update the date at the top of the page. Substantive corrections are noted in the page itself when they change a claim rather than a typo.

Contact

Editorial questions and corrections: hello@reflextimer.com. For data and privacy questions, see the Privacy Policy; for commercial and embedding terms, see the Terms of Service.