Dated entries: which check was added, what was fixed and why — with a link to try each change.
An entry is written when something changes for the person using the site: a new check appears, a check starts reporting something it did not report before, or a fault that gave a wrong answer is corrected. Each entry carries a link straight to the thing that changed, so you can see it rather than read about it.
Nothing is written for changes you cannot notice. Reworded paragraphs, adjusted spacing, a different shade of a button — these are not improvements to report, and a log padded with them stops being worth opening. The same goes for the plumbing: which libraries the site uses and how it is deployed are our problem, not news.
Entries carry the real date on which the change went live, and they are never backdated to make the site look busier. When several changes land on one day they are still written as separate entries, because they answer separate questions — but they are published across the following days rather than dumped together, since three entries under one date read as a one-off tidy-up rather than as a project that is actually being worked on.
If a change turns out to be wrong and gets reverted, that reversal gets its own entry too. A log that only records successes is a marketing page with dates on it.
A single average hides the thing people actually complain about. A connection averaging 60 ms that keeps jumping breaks up a call far worse than a steady 120 ms one, so the check now reports the spread alongside the median, and draws every probe as its own bar. An even row means a steady line; a ragged row is the reason voices stutter.
Measure your latency →The site opens with checks for the keyboard, microphone, camera, speakers, latency, frame rate and screen, plus a summary page that collects whatever you have run. The summary is assembled in your own browser and shared by copying text, not by uploading a report — which is why the promise on every check page, that nothing you produce is recorded or sent, stays true on the page that gathers it all together.
Open the summary →The domain was pointed at its server and the first pages went up behind a closed door — nothing here was reachable from a search engine yet. Starting closed is deliberate: an unfinished site that reaches the index gets in quickly and takes a long time to leave.
See what is here now →