Use repeated measurements and context rather than treating one number as an absolute diagnosis.
TEST / LAB0BPS / MODULE
DIAGNOSTIC SESSION
Run one guided Cloudflare edge session and read throughput, idle latency, jitter, latency under load, callback consistency and the established Connection Score together.
01IDLE LATENCY02DOWNLOAD03UPLOAD04LOAD LATENCY05QUALITY
DOWNLOAD—Mbps
UPLOAD—Mbps
LATENCY—ms
JITTER—ms
DOWNLOAD LOAD—increase above idle
UPLOAD LOAD—increase above idle
CALLBACK CONSISTENCY—awaiting real updates
CONNECTION SCORE—Established model v1
MEASURED EVIDENCE—
MAIN WATCH ITEM—
BUFFERBLOAT SIGNAL
—
NEXT CHECK
—
ONE EDGE SESSIONSame measured result feeds throughput, load evidence and score interpretationNO CLOUD PROFILEHistory remains browser-localMETHOD ↗
The guided phases describe one Cloudflare edge measurement session. 0bps does not secretly run a different test for each card, and it does not create a new score model.
REFERENCE / FAQ
COMMON QUESTIONS
Does the diagnostic session run several unrelated tests?
No. It uses one guided Cloudflare edge measurement session and exposes the throughput, idle latency, jitter and loaded-latency phases in sequence, then applies the established Connection Score to those measured core values.
Does the session upload my local history?
No. Completed session results can be stored in this browser history and exported explicitly by you, but 0bps does not intentionally upload the browser-local history values.
Browser APIs and network paths can limit what a web tool can observe.