Fix what the test found
Start with the guide the test linked you to. It picks the result that hurts most, in this order: packet loss, then bufferbloat, then jitter, then ping, then speed. Each guide starts from that result, gives steps taken from the maker's or provider's own documentation, and ends with the test to run again.
Which guide
| What the test found | Start here |
|---|---|
| Packet loss above 1% | Fix packet loss |
| Bufferbloat grade C, D or F | Fix bufferbloat |
| Jitter above 10 ms, or ping higher on Wi-Fi than on a cable | High ping and jitter on Wi-Fi |
| Ping above 50 ms in games | Lag in online games |
| Speed below what you pay for | How to test Wi-Fi against Ethernet |
On Starlink or T-Mobile 5G home internet, read the guide for your service as well: both behave differently from cable and fiber.
All guides
- BufferbloatHow to fix bufferbloat with smart queue management (SQM, cake, fq_codel): steps for OpenWrt, eero, UniFi and ASUS, and what to do if your router has none.
- Packet lossFix packet loss step by step: test on Wi-Fi and on a cable, then at the modem, check cables and interference, and know what to tell your internet provider.
- High ping on Wi-FiFix high ping and jitter on Wi-Fi: use a cable where you can, move to 5 or 6 GHz, place the router better, pick a clear channel and wire your mesh nodes.
- Lag in gamesFix lag in online games: tell network lag from low frame rate, pick the nearest server region, play on a cable, fix bufferbloat and pause background uploads.
- StarlinkFix Starlink lag: what Starlink says about its latency, how to clear obstructions, using your own router in bypass mode, and SQM to control bufferbloat.
- T-Mobile home internetFix jitter and lag on T-Mobile 5G home internet: gateway placement near a window, signal checks in the T-Life app, your own router, and testing by time of day.
- Wi-Fi vs EthernetCompare Wi-Fi with a wired connection in about 15 minutes: same device, same spot, three runs on each, then compare ping, jitter, speed and bufferbloat grade.
Before you change anything
Run the full test two or three times and note the numbers. Change one thing at a time, then test again. If a change doesn't help, undo it before trying the next. That way you know which step fixed it, and you don't leave a setting behind that slows the line for nothing.
Every step in these guides links the page it comes from: router makers' help centers, OpenWrt's documentation, bufferbloat.net, and Starlink, T-Mobile, Microsoft, Sony and Nintendo support. Menus change with firmware updates, so if yours looks different, check the linked page first.