Full Diagnostic Report Export

Every silent check in one run, exported as a dated PDF for tickets, claims and resale.

Build the report

Runs every check that needs no permission and no input — connection, latency and jitter, clock drift, browser and device capabilities, privacy signals — and assembles the results into one dated, exportable report. Nothing is uploaded; the report exists only on this machine until you choose where to send it.

How this calculation works

One button runs every check on this site that needs no permission and no participation: what the connection looks like from outside, twenty timed round trips for latency and jitter, system clock drift against a reference, what the browser reports about the device and display, and which privacy signals it sends. The results are assembled into a single dated report, and the export button turns it into a PDF built entirely in your browser. The date matters more than it looks. A warranty desk wants evidence from before the return window closed; a buyer wants the listing's claims tested on the day of sale; a repair shop wants the state of the machine as it arrived, not as remembered. A report generated on the spot, timestamped, answers all three — and because nothing is uploaded anywhere, the only copy is the one you choose to attach.

What the results mean

Overall status: The worst status any check produced. One failing check makes the report a fail, because that is the line a reader will scan for — the details name which check it was.
Latency and jitter: Round-trip timing to the nearest edge and how much it varies. The jitter figure is the one that predicts whether calls break up.
Clock drift: How far the machine's clock is from the reference. Drift of minutes breaks logins and certificate checks in ways that look like random network errors.
Not in this report: Anything interactive — camera, microphone, speakers, keyboard, dead pixels, touch. Each has its own page, and each result exports the same way if the ticket needs it.

Common problems and fixes

The repair shop wants proof the fault existed before I shipped the device: Run the report while the fault is present and export the PDF — it is dated at generation. Pair it with the specific failing test's own export (dead pixels, keyboard, battery) for the fault itself; this report establishes the machine's baseline around it.
I am selling a laptop and the buyer wants evidence it works: Run this report on the machine and export it into the listing. Then add the interactive results a buyer actually worries about — screen defects and keyboard — from their own pages. Three PDFs beat a paragraph of assurances.
The report says a check could not run: Usually the connection checks on a deployment where the measuring endpoint is unavailable, or a network blip mid-run. Run it again; if one check persistently cannot run, export anyway — the report states what did not run rather than hiding it.
Support wants hardware details the report does not include: That is the report being honest: a browser cannot read serial numbers, SMART health or installed memory. Use the operating system's own tools for that layer — System Information on Windows, System Report on macOS — and let this report cover what the browser can measure.

Frequently asked questions

Where does the report go when I export it?

To your downloads folder, and nowhere else. The checks run in the page, the PDF is assembled in the page, and no copy exists anywhere until you attach it to something. That is deliberate: a diagnostic report describes your machine, and it should be yours to distribute or not.

Will a warranty desk or repair shop actually accept this?

As supporting evidence, generally yes — it is a dated, structured account of the machine's state, which beats a description from memory. What settles a claim is usually the specific fault, so pair this baseline with the export from the test that shows the fault itself.

Why doesn't it test my camera and microphone too?

Because those need permission prompts and your participation, and a report that fires permission dialogs while claiming to run silently would be both annoying and empty — denied prompts produce holes, not data. The interactive tests live on their own pages, take a minute each, and export identically.

Can I get the data as JSON instead of a PDF?

Yes — the same result card offers a copyable JSON payload alongside the PDF, with every check's figures. That is the version to attach to a ticketing system that parses attachments, or to diff against a report from last month.

Put this on your own site

Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.

Embed code

<iframe src="https://runthetests.com/embed/diagnostic-report/" width="100%" height="560" style="border:1px solid #e5e5e5;border-radius:8px" title="Full Diagnostic Report Export" loading="lazy"></iframe>

Preview it at https://runthetests.com/embed/diagnostic-report/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.