Guides
Each guide answers one question people actually ask — and shows the numbers that settle it. Start with the symptom you have.
Start from the symptom
Six guides, each answering one question. Pick the line that sounds like your problem:
| The speed test is fine but the game lags | Why you lag when the speed test says everything is fine |
| Everything crawls while something downloads or uploads | Why your ping spikes when the connection is busy |
| The ISP says the line is normal and closed my ticket | Evidence your provider cannot wave away |
| Some sites hang or fail while others load | How to find your Path MTU on iPhone |
| I measured an MTU and now I need to set it | Where is the MTU setting on my router? |
| My VPN connects but nothing loads through it | WireGuard handshake fails on iOS but not on other devices |
Why you lag when the speed test says everything is fine
Speed tests miss the two numbers that decide whether a game or call is playable: jitter and loss. How to read median, jitter and loss per server on iPhone.
Why your ping spikes when the connection is busy
Your speed test looks fine, yet calls freeze and games lag. Measure latency under load from an iPhone and learn whether your router or ISP is queueing.
Evidence your provider cannot wave away
A ticket that says “the internet is slow” gets closed. One with per-hop loss, latency under load and timestamps gets escalated. What to measure and export.
How to find your Path MTU on iPhone
Measure the real Path MTU of your connection from an iPhone in 30 seconds — no manual ping payload guessing. Works on 4G/5G, Wi-Fi, PPPoE and VPN tunnels.
Where is the MTU setting on my router?
Admin addresses and exact menu paths to the MTU field on the routers ISPs hand out most: Huawei, ZTE, TP-Link, Zyxel and Nokia.
WireGuard handshake fails on iOS but not on other devices
Handshake did not complete on Wi-Fi but the tunnel works on 5G? A handshake is 148 bytes, so MTU cannot break it. What to test instead, from the iPhone.
The method behind all of them
Each guide follows the same three steps, because attribution is the whole problem. Measure the near thing first — your own router — so you know whether the rest of the numbers are trustworthy. Then measure the far thing under the condition that breaks it, which usually means under load rather than idle, since a queue only shows when something is filling it. Then compare the two and let the gap name the culprit: a router that stays fast while the internet slows puts the queue outside your flat, and a router that slows with everything else puts it inside. Every number in the guides is one you can reproduce yourself, on a phone, in under a minute.
Download on the App StoreFree · 27 tools · one-time purchase removes ads · no subscription