Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.
Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Connection tests
Full Diagnostics guide
Run a combined browser diagnostic covering throughput, latency, stability, loss and protocol details.
Open Full DiagnosticsWhat you need
- Optional connection context or expected service details
How to use it
- 1Prepare the connection and close heavy traffic.
- 2Start Full Diagnostics.
- 3Keep the page active through every stage.
- 4Review findings and export a support report if needed.
Understanding the results
- Use the evidence for each component; do not rely only on the overall score.
Recommended next actions
- Repeat weak components individually and provide consistent evidence to support.
Common problems
- Interrupted tabs, VPNs and changing wireless conditions can produce incomplete results.
Privacy and security
- Review labels and device details before sharing an exported report.
Worked example
- Scenario
- Preparing evidence for an intermittent connection
- Example input
- Run once during the fault and again when stable
- How to read it
- Differences in loss and loaded latency help narrow the symptom without proving its cause.
Limitations
- The combined report is not a certified fault diagnosis.
Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.