Slow Internet: A Reversible Troubleshooting Checklist

Record the symptom, compare local conditions, and gather evidence before resetting equipment or changing your plan.

By Younes Kirat : Publisher and maintainer
Source-linked guidance · Not a comparative benchmark

Define the affected task

Record which application, device, destination, and time are affected. Distinguish a slow transfer from a failing connection, a delayed game, or a call problem. Check the application’s status and displayed units. A browser speed result does not isolate the cause, and a specific percentage of an advertised rate is not a universal fault or contract-violation threshold.

Compare the local connection

On the same device, compare Wi-Fi with Ethernet to the same router if available. Disable the unused interface and record local link speed, device load, VPN use, and placement. Follow Microsoft’s connection checks. An improvement narrows a contributor; poor results on both interfaces do not prove that the provider is at fault.

Keep quiet and busy conditions separate

With permission, pause nonessential transfers for a quiet comparison and record ordinary busy behavior separately. Repeat the same task and destination at different times. Keep unsuccessful runs and validity warnings. An evening pattern can justify further investigation but does not establish deliberate throttling or a saturated neighborhood node.

Make one reversible change

Save the current configuration, follow device documentation, and change one setting at a time. Check supported updates and physical connections. Do not factory-reset shared equipment or bypass provider hardware without a recovery plan, including authentication and phone-service requirements. No reboot duration or ten-minute procedure guarantees a fix.

Escalate with a useful record

Send support dated observations, affected tasks, active interfaces, local link details, and warnings. Compare the actual plan terms and Broadband Consumer Label where available. Ask which further checks can narrow the cause. Verify the original symptom after a change and restore the prior settings if service worsens.

Method and sources

Read the HTTP timing limits and validity warnings and testing policy. VelocityVerify does not measure end-to-end packet loss or a separate upload-loaded latency series. New letter grades are withheld.

Editorial update: Earlier calculation or capability claims were revised. See editorial corrections.