DevicedialTest plans and logs
A single reading answers today's question. A column of them with dates answers the ones that get expensive.
Gear test schedule
Set the interval once and get the next twelve dates for the tests that catch a fault early โ with an email a few days before each one, if you want it.
Headset and mic comparison
Two or three microphones side by side with the peak and the background noise you measured, and the gap between them in decibels for each one.
Input lag budget
Every wait between your hand and the screen on one sheet โ polling interval, frame time, panel response, render queue โ added into one worst-case figure in ms.
New machine test plan
A target for every check, your own reading beside it, and a count of how many the machine actually met โ run it while the return window is still open.
Stream check sheet
Every source you are sending โ camera, screen share, audio โ turned into megabits a second, added up, with headroom and the size of a two-hour stream.
Warranty claim log
A dated row for every reading, the limit it should have stayed inside, and a running count of how many went past it โ evidence instead of a description.
Free to use, Pro to keep
Every sheet on this page works straight away, with no account and no limit on how often you use it. Put your numbers in and you get the answer, exactly like the tests on the rest of the site.
What Pro adds is memory and reach. It saves a sheet to your account so it is there on your phone as well as the machine you built it on. It turns a column of readings into a page you can send to a support desk. It emails you when a date you set is coming, instead of leaving that to your own memory. And it takes the ads off โ here and on every other site we run, on one subscription.
Which sheet answers which question
The input lag budget is for the delay you can feel but cannot measure in one go: it adds the polling interval, the frame time, the panel’s response and the render queue into a single worst case in milliseconds. The new machine test plan is for the first week, while the return window is open โ a target beside every reading and a count of how many the machine met.
The gear test schedule is for everything that fails gradually: an interval per device and the next twelve dates, so a check happens on a date rather than after something has already gone wrong. When one of those readings goes the wrong way, the warranty claim log keeps it dated next to the limit it should have stayed inside, and counts the ones that went past.
The last two are about choosing and going live. The headset and mic comparison ranks two or three microphones by how little of the room they bring with them, and the stream check sheet turns your camera, screen share and audio into the megabits a second your upload actually has to carry.
See what is included on the Free and Pro page.
Frequently asked questions
Do I need an account to use these?
No. Every sheet on this page calculates in full without an account, the same as every test on the site, and none of them sends your rows anywhere. What an account adds is memory and reach: the setup saved so it is on your phone as well as the machine you built it on, a result turned into a page you can send to a support desk, an email before a date you set, and no ads.
Why is a plan different from a test?
A test answers one question once โ how loud, how fast, how many. A plan is what you do with several answers: the difference between two headsets, the four delays that make up the lag you feel, the six readings that show a stick has drifted since March. The tests produce the numbers, and none of them can see the others. These sheets are where the numbers meet.
Can I keep using these on my own numbers from somewhere else?
Yes. Nothing in these sheets is tied to the tests on this site โ a figure from a manufacturer’s datasheet, a monitoring tool or a colleague’s machine goes in the same column. The tests are simply the quickest way to get a number that is yours, measured on the hardware in front of you, rather than one from a review of a different sample.
How the test works
Sources: