Streaming guide
Speed test for smart TVs (4K and HDR)
Test the television's real connection, compare it with the selected service's current 4K recommendation, and distinguish network buffering from app, device, or format support.
Netflix, Disney+, and YouTubeTV vs same-room comparisonPlayback and format diagnosis
Speed TestResults
Test your internet speed
Measure download, upload, and latency instantly—no installs.
Download
—
Upload
—
Latency
—
Actionable insights
See how your results stack up for streaming, gaming, and remote work.
Run again after tweaks to confirm Wi-Fi and device improvements.
Runs in your browser. No account or download required.
Setup checklist
Get faster, steadier results
Follow these focused steps, run a fresh speed test, and compare the numbers against your goals.
4K requirements are service-specific
- Netflix: Netflix currently recommends a stable 15 Mbps or higher for its 4K UHD playback. See the Netflix speed table.
- Disney+: Disney+ currently recommends 25 Mbps for 4K UHD content. See its internet speed recommendations.
- YouTube: YouTube lists an approximate sustained 20 Mbps recommendation for 4K UHD. See YouTube's system requirements.
- These are per-service playback references, not a universal household plan size. Add simultaneous streams and other real household demand, then test the television's actual connection.
- Updated July 24, 2026. The guide now separates platform-specific sustained-speed recommendations from unsupported latency, jitter, HDR, and audio claims.
Controlled smart TV test workflow
- Use the TV or external streaming device's built-in network test or browser when available. Record whether it uses Ethernet or Wi-Fi, the connected band, and the app being diagnosed.
- If the television has no suitable test, Disney+ advises testing another device close to the TV on the same network. Treat that as a proxy—not proof of the TV's own radio performance. See Disney+ connection-test guidance.
- Run one quiet test and one during the time buffering occurs. Keep the SwiftSpeedTest endpoint fixed when possible and record download, loaded latency, jitter, unsuccessful probes, and confidence.
- Play a known 4K title in the affected app and use the app's playback statistics or diagnostics when available. Browser speed and actual CDN playback are different evidence.
- Repeat on an approved Ethernet connection or a capable same-room device to isolate the TV radio, room coverage, and internet path.
Decision table: interpret buffering and quality changes
- Quiet test meets the service recommendation; peak-time test does not: shared household or provider congestion is more likely than an incompatible TV.
- Same-room phone is fast; TV test is slow:inspect the TV's Wi-Fi band, signal, firmware, app, radio capability, and placement. The phone is not a substitute for the TV result.
- Ethernet good; TV Wi-Fi poor: improve the wireless path or keep a supported wired connection. Do not buy a faster plan before addressing the local link.
- All apps buffer: inspect network demand, Wi-Fi or Ethernet, gateway, and provider performance. Test a second supported device before resetting the TV.
- Only one app buffers:check that service's status, app update, account, title availability, cache or reinstall procedure, and service-specific diagnostics.
- Mbps looks sufficient; loaded responsiveness degrades: pause a competing download or upload and retest. Queueing under load can interrupt adaptive playback even when idle speed looks strong.
HDR, Dolby Vision, and audio are not speed-test grades
- A throughput result cannot confirm HDR10, Dolby Vision, Dolby Atmos, frame rate, color depth, or resolution. Those also depend on the title, subscription, app, TV or streamer, HDMI path, receiver, display settings, and service support.
- If playback is smooth but HDR or immersive audio is missing, verify the service plan and title badge, device compatibility, app settings, HDMI input or cable, and receiver or soundbar configuration.
- Do not use an arbitrary latency or jitter threshold to diagnose on-demand 4K. Compare actual playback, loaded responsiveness, and service diagnostics under the same workload.
- Live sports and low-delay streams can behave differently from on-demand video. Use the service's live-playback help and test at the actual event time.
- A 4K-capable screen does not guarantee that every app, input, account tier, or title will deliver 4K.
Safe network changes in the right order
- Pause one nonessential household transfer and replay the same scene. Keep the change only if the symptom is reproducibly improved.
- Move the access point or remove nearby obstructions only when a room-level comparison shows a wireless problem; do not hide the router in the TV cabinet.
- Try approved Ethernet where practical, but confirm the TV, adapter, switch, and cable link are supported and negotiated correctly.
- Update the TV or streaming device and affected app using the manufacturer's procedure. Restart after saving evidence; do not factory-reset first.
- Lower the app's video quality temporarily when the connection cannot sustain that service's current recommendation, then restore and retest after the network issue is resolved.
QoS and router settings without overpromising
- Do not assume a “streaming” QoS toggle can identify or prioritize every encrypted app flow. It may help only when the router manages the actual bottleneck and the policy is implemented correctly.
- Capture a failing busy-network result, change one documented router setting, and replay the same content. Remove the change if other calls, games, or devices regress.
- Apple recommends keeping WMM enabled on modern routers and using automatic channel selection, supported bands, current security, and firmware. Read its official Wi-Fi router settings guide alongside the router manufacturer's instructions.
- Do not disable other devices, encryption, firewalls, or required VPN and DNS policy as a permanent streaming fix. Schedule or isolate the actual competing workload instead.
- Add mesh hardware only after the same-room and TV-location tests prove a coverage or backhaul issue. More radios are not an automatic improvement.
Measurement limits and evidence to save
- Save the service, title type, time, TV or streamer model, app version, connection type, room, selected endpoint, playback symptom, and paired test results.
- SwiftSpeedTest measures one browser-to-endpoint path. It cannot certify a streaming CDN, DRM license, app, television decoder, HDMI chain, subscription, or title encoding.
- Adaptive streaming changes bitrate and resolution with current conditions. A short successful test does not guarantee an entire movie or live event will remain at 4K.
- Repeated speed tests transfer data. Consider plan data allowances before testing multiple televisions or mobile connections.
- Review the SwiftSpeedTest methodology for adaptive transfers, loaded latency, confidence, and known limitations.
Retest and log improvements
Run SwiftSpeedTest after each change. Note the download, upload, and latency shifts to lock in better performance.