English guide
IPTV speed test: Mbps, jitter and what they actually mean
Buffering is usually the connection, not the channel. This test downloads a fixed, incompressible payload from our own worker and measures how long it takes, then repeats small requests to see how much the response time wobbles. Two numbers decide whether 1080p is comfortable — and neither of them is your provider’s advertised speed.
Open the speed test →This test measures the download speed and response-time variation between your device and the Cloudflare edge. Whether your ISP restricts IPTV ports (8080, 25461…) cannot be measured from a browser; the result is an indication, not a diagnosis.
Running a test that means something
1. Test on the device that watches
A TV box on Wi-Fi and a laptop next to the router have different links. If the box stutters, run the test on the box — or at least on the same Wi-Fi band (2.4 GHz vs 5 GHz changes everything).
2. Read Mbps against the quality you watch
Rough references: SD 3–5 Mbps, 1080p 8–12 Mbps, 4K 25–40 Mbps. Watching on two devices means adding those numbers, because the line carries both streams.
3. Read jitter, not just the average ping
Jitter is the variation between consecutive response times. A 20 ms average with 90 ms swings still produces micro-freezes and audio drift on live TV, which is why the tool reports both.
4. Repeat at peak time
A 21:00 measurement is the one that matters: neighbourhood congestion shows up exactly when you want to watch. One test at 11:00 proves nothing about the evening.
5. Compare two networks
Run it twice — once on home Wi-Fi, once on mobile data. If mobile is fine and Wi-Fi is not, the problem is your router or line, not the provider.
How to read the verdict
- • 8 Mbps and above + under 60 ms — Comfortable for 1080p; 4K needs roughly 25 Mbps of stable throughput.
- • 3–8 Mbps — Borderline: 1080p channels will buffer now and then, HD is safer.
- • Under 3 Mbps — Freezing is likely at any HD quality; drop to SD or fix the link first.
- • Jitter above 60 ms — Low average speed is not the issue here — the line is unstable, which hits live TV hardest.
- • Port 443 only — The browser cannot open 8080 or 25461, so this measures the general link, not a port-level block.
What the browser cannot measure
Be clear about the scope: a browser can only make standard HTTPS requests, so this is not a port-level IPTV test and it cannot prove that your ISP throttles port 8080. It measures the route between you and our server, which is not the same route as you and your panel — a fast test plus a slow panel is entirely possible. What it does measure reliably is your line’s ceiling and its stability.
FAQ
How many Mbps do I need for IPTV?+
SD 3–5, 1080p 8–12, 4K 25–40 Mbps per stream. Add them for simultaneous viewers and keep a margin: a line that measures 12 Mbps will struggle with two 1080p streams.
Can this prove my ISP is blocking IPTV?+
No. The browser only speaks HTTPS on port 443, while panels often use 8080 or 25461. Compare a mobile-data run with your home line instead — a big difference points at your ISP or router.
Why does jitter matter more than the average ping?+
Live TV cannot buffer ahead like VOD. If response times swing by 60 ms or more, the player’s buffer drains and refills — that is what you see as a micro-freeze or a sound drop.
Is anything stored?+
No. The test downloads a fixed payload and times it; there is no result table on the server, no IP log, and refreshing the page clears everything.
Related guides · Bandwidth calculator · Stream diagnostics · Türkçe