Check whether the problem is widespread
Try another ordinary website and another device on the same network. If only one service is slow, it may have a distant server or its own incident. If only one laptop is affected, check background transfers, browser extensions and whether it is connected to the intended Wi-Fi network.
Measure capacity and consistency
Run the Speed Test with large transfers paused. Then run the Jitter Test. Fast download results with inconsistent response times explain a different problem from low transfer capacity. These tests use the MyLaptopTools edge and cannot measure every internet route.
Compare Ethernet and Wi-Fi
If possible, connect directly to the router by Ethernet and repeat. Otherwise move nearer the router without changing other conditions. Improvement points toward the wireless path, though it does not identify a specific faulty component. A stronger internet subscription will not necessarily fix weak coverage inside the home.
Check uploads and VPN routing
Cloud backups, large attachments and other devices can fill the upload path. Compare a quiet run with normal use. If policy permits, compare VPN on and off while avoiding sensitive browsing during the comparison. A VPN changes both the route and the destination visible to services.
Work through a controlled comparison
Write down the time, connection type, VPN state and whether other devices are busy. Run each comparison more than once; a single improved reading can be a coincidence. Use this sequence to narrow the problem before changing equipment or your subscription.
- Establish a quiet baseline. Pause your own downloads and backups, then run a speed and connection test in a visible tab.
- Repeat near the router. Keep the laptop and browser the same. An improvement suggests that signal strength or interference deserves attention.
- Try Ethernet if available. A consistently better wired result helps isolate Wi-Fi from the wider connection.
- Compare normal use. Let your usual applications run again. A large change while a backup or upload runs suggests contention for capacity.
- Compare a second device. Similar symptoms on both devices make a single browser extension or laptop setting less likely.
Example: fast downloads but a poor video call
Suppose a quiet test shows 180 Mbps download, while calls become choppy during a cloud backup. That download figure alone does not explain the call. Pause the backup and repeat the call or connection check, then resume it and compare. If the problem returns repeatedly, inspect upload activity and any available bandwidth controls. This is an illustrative example, not a benchmark or a diagnosis of your connection.
What to tell your provider
A useful report is specific: “Two devices have the same problem on Ethernet at 19:00 and 20:00; several websites are affected; no downloads were running.” Include repeated measurements and the endpoints tested. Avoid claiming packet loss from failed HTTP requests alone: browser requests can fail for several reasons.
Collect evidence before escalating
Record the time, connection type and repeated readings. The Connection Test can show failed browser requests, not direct packet-loss percentages. If the problem persists on multiple wired devices and services, share that evidence with your provider. Keep IP addresses out of public forum posts.