Free · No Signup · 100% Client-Side

Internet feels slow
even though your speed
test looks fine?

NetSymptom pinpoints the real bottleneck in under 30 seconds — bufferbloat, ISP congestion, DNS lag, Wi-Fi interference, and more.

Zero data collected Runs entirely in your browser Deterministic weighted engine Always free
1
Get Speed
2
Calibrate
3
Results
Step 1 Recommended

Get Your Real-World Speed Data

Run an official speed test first. You'll enter those numbers into Step 2 — this is what makes our diagnosis accurate. Fast.com is powered by Netflix's global CDN and gives honest results.

Launch Verified Speed Test (Fast.com)

Opens in a new tab. Returns here automatically. Note your Download speed, Upload speed, and Latency.

Step 2

Calibration Matrix

Excellent <20msGood <50msFair <100msPoor 100ms+
Step 3

Diagnostic Report

Network Health Score

--
/ 100

Probable Root Causes

Network Path Bottleneck

Network Paradox Translator

Priority Fix Checklist

Step-by-Step Repair Guides

Recommended Fix

View Best Options
Deep-Dive Knowledge Base

The Science Behind Slow Internet

Understanding why your connection misbehaves is the first step to fixing it permanently. These are the four mechanisms responsible for the overwhelming majority of real-world slowdowns.

Bufferbloat: The Hidden Latency Killer

Primary cause of gaming lag & call drops

Bufferbloat is one of the most misunderstood networking phenomena of the modern internet era. To understand it, imagine your home router as a post office sorting room. When mail arrives faster than it can be processed and sent out, it piles up in a back room — the buffer. In networking, data packets behave identically. Modern routers are equipped with enormous packet buffers — sometimes hundreds of milliseconds deep — intended to prevent packet loss during temporary traffic surges.

The catastrophic side effect is that when your connection is under load — say, a family member downloads a large file — your router's outbound buffer fills completely. Every packet trying to leave your network must wait in that queue. A gaming packet that normally takes 8ms to reach a server might now wait 400ms in your own router's buffer before it even leaves your home. This is bufferbloat: massive latency caused not by the internet infrastructure, but by your own router's memory.

The cruel irony of bufferbloat is that it is completely invisible to speed tests. A speed test downloads a large file using your maximum bandwidth — it fills the buffer intentionally and measures throughput. The test passes with flying colours. Your ping looks fine because the test pings a nearby server before the buffer is loaded. But the moment real mixed traffic flows — streaming while browsing while someone else downloads — latency explodes.

The engineering solution is Active Queue Management (AQM), specifically algorithms like FQ-CoDel (Flow Queuing Controlled Delay) or CAKE. These algorithms intelligently drop or delay packets before the buffer fills completely, keeping latency consistently low even under heavy load. Consumer-grade routers rarely implement these by default. OpenWRT-based routers with SQM (Smart Queue Management) enabled solve this problem elegantly. DD-WRT and commercial routers from Netgear's Nighthawk line also offer QoS settings that partially address this.

You can test for bufferbloat yourself at waveform.com/tools/bufferbloat. A grade of A or B means your router handles queuing well. A grade of D or F means bufferbloat is almost certainly causing your real-world slowdowns regardless of what your speed test shows.

ISP Peering Agreements & Selective Throttling

Why Netflix buffers at 7pm even on 500 Mbps

The internet is not a single unified network. It is a collection of thousands of independent networks — called Autonomous Systems — operated by internet service providers, content delivery networks, universities, and corporations. These networks interconnect at physical facilities called Internet Exchange Points (IXPs). The agreements governing how traffic flows between these networks are called peering agreements, and they have profound effects on your everyday internet experience.

When you load YouTube, your data travels: from Google's servers → through Google's network → to a peering point → through your ISP's backbone → to your home. Each of those handoffs is governed by a commercial agreement. ISPs that have paid for or negotiated strong peering with Google will deliver YouTube at full speed. ISPs with weak or distant peering arrangements route that traffic through congested intercontinental links — and you experience buffering even on a gigabit connection.

This is why you might have 500 Mbps service and still see YouTube buffer at 7pm on weeknights. It is not your home network. It is the link between your ISP and Google's content delivery infrastructure. A speed test to a nearby server — often hosted by the ISP itself — shows 500 Mbps because that path is uncontested. The path to YouTube traverses different, congested infrastructure.

Beyond peering, many ISPs practice deep packet inspection (DPI) throttling — identifying traffic types by their network signature and artificially limiting bandwidth to specific services. Netflix, Twitch, and BitTorrent have all been confirmed targets of ISP throttling in published research and regulatory proceedings. The FCC's 2015 Open Internet Order prohibited this, but regulatory enforcement has varied significantly across administrations.

The most reliable way to detect ISP throttling is to run a speed test to a content-specific server, then run the same test through a commercial VPN. If speeds increase dramatically through the VPN, throttling is almost certainly occurring. Tools like the M-Lab NDT test can also reveal throttling patterns across time-of-day measurements.

DNS Resolution: The Hidden Pre-Loading Tax

Why fast connections still have slow page starts

Every time you type a web address or click a link, your device must first resolve the domain name to an IP address before a single byte of actual content can flow. This is DNS — the Domain Name System — and it is the internet's global directory service, operating as a hierarchical distributed database spanning millions of servers worldwide. The speed of this lookup is entirely separate from your connection bandwidth and is invisible to speed tests.

By default, DNS queries go to your ISP's resolver. These resolvers are often poorly maintained, geographically distant from you, under-resourced during peak hours, and slow to propagate updates from authoritative name servers. A typical ISP DNS lookup takes 40–150ms. Cloudflare's 1.1.1.1 — the world's fastest public DNS resolver according to independent benchmarks — returns results in 2–14ms. That 100ms difference happens on every single page load, every image, every JavaScript file, every API call.

Modern web pages make dozens to hundreds of DNS lookups per page load. A news site loading 80 resources from 20 different domains will trigger up to 20 unique DNS lookups. At 100ms per lookup (ISP) versus 5ms per lookup (Cloudflare), the difference is 1,900ms — nearly two full seconds — added to every page's load time, invisible to speed tests, completely fixable in under five minutes.

Beyond raw speed, DNS also affects privacy. ISP DNS resolvers log all your queries by default, creating a complete browsing history tied to your account. Cloudflare's 1.1.1.1 and Quad9 (9.9.9.9) explicitly log no identifying query data. DNS-over-HTTPS (DoH) further encrypts these queries so even your ISP cannot intercept them in transit. Chrome, Firefox, and Edge all support DoH natively in settings.

For technically oriented users, running a local DNS resolver with prefetching and caching — such as Pi-hole on a Raspberry Pi or NextDNS — can reduce DNS lookup times to near-zero for frequently visited domains, as the resolver caches results locally and answers from RAM rather than querying remote servers at all.

Packet Loss, Physical Transit & the Bandwidth Pipeline

Why raw Mbps is not the whole story

Bandwidth — measured in Megabits per second — describes the theoretical maximum volume of data your connection can carry, like the diameter of a pipe. But the actual performance of your internet depends on three distinct properties that bandwidth alone cannot capture: latency (how fast each individual packet travels), jitter (how inconsistently packets arrive), and packet loss (what percentage of packets disappear entirely). A 1 Gbps connection with 5% packet loss performs catastrophically worse than a 100 Mbps connection with 0% loss for most real-world applications.

TCP — the protocol underlying most internet traffic — was designed to handle packet loss gracefully by retransmitting lost data. But retransmission takes time. When a packet is lost, TCP waits for a timeout period, then retransmits. During this wait, your video pauses, your game stutters, your file download stalls. Even 1% packet loss reduces TCP throughput dramatically and causes visible buffering in adaptive streaming video. Real-time protocols like the ones used in gaming and video calls cannot retransmit at all — lost packets mean visible lag or frozen frames.

Packet loss on your Wi-Fi connection — the most common source — is caused by signal interference, distance from the router, physical obstructions, and competing networks on the same channel. The 2.4GHz band, used by most older Wi-Fi devices, is shared with microwave ovens, Bluetooth devices, baby monitors, and dozens of neighbouring networks. Switching to 5GHz dramatically reduces interference-related packet loss, at the cost of reduced range. Wi-Fi 6 and Wi-Fi 6E introduce OFDMA multi-user access and BSS colouring to further reduce interference in dense environments.

Beyond your home, packet loss occurs at ISP interconnects under congestion, at international undersea cable links, and at content server infrastructure during traffic surges. Tools like MTR (My Traceroute) can trace the exact path your packets take and identify which network hop is causing loss. Most operating systems include a variant: run mtr google.com on Linux/Mac or winmtr.exe on Windows to see a real-time map of where your packets are being delayed or dropped.

Common Questions

Frequently Asked Questions

Everything you need to know about diagnosing and fixing internet performance issues.

Speed tests measure the maximum theoretical bandwidth between your device and a nearby, often ISP-owned server, under ideal unloaded conditions. They are not measuring the full journey your data takes to reach Netflix, YouTube, Zoom, or Steam servers. Several factors cause the paradox:

  • Bufferbloat: Your router's buffers fill under load, causing latency to spike from 8ms to 400ms or more — invisible to throughput tests.
  • ISP Peering Congestion: The path from your ISP to a specific content provider may be congested even when your access line is clear.
  • DNS Latency: Slow domain lookups add 100-200ms before any content loads, on every page, every resource.
  • Packet Loss: Even 0.5% packet loss from Wi-Fi interference causes TCP retransmissions that dramatically reduce effective throughput for streaming and real-time applications.
  • Server-Side Limitations: The content server itself may be throttling connections or geographically distant.

The speed test passes because none of these issues affect a single large-file download to a nearby server. But all of them affect your everyday browsing, streaming, and gaming experience continuously.

DNS — the Domain Name System — is the internet's phonebook. When you type "google.com" your browser cannot use that name directly; it needs the IP address (like 142.250.80.46). A DNS query is sent to a name server which looks up and returns that IP. Only then can your browser open a connection and start loading content.

This lookup must complete before any data flows. If your ISP's DNS server takes 120ms to respond (common on overloaded ISP infrastructure), that 120ms delay is added to every single resource your browser loads — every image, every script, every font, every API call.

How to change your DNS:

  • Cloudflare 1.1.1.1 — Fastest globally, privacy-focused, free. Secondary: 1.0.0.1
  • Google 8.8.8.8 — Reliable, widely supported. Secondary: 8.8.4.4
  • Quad9 9.9.9.9 — Blocks malicious domains, privacy-respecting. Secondary: 149.112.112.112

Change DNS in your router's admin panel to apply it to all devices simultaneously. Or change it per-device in Network adapter settings. The improvement is immediate — no restart required.

Yes — but only in a specific scenario. The condition is ISP throttling. Many ISPs use deep packet inspection to identify Netflix, YouTube, or Twitch traffic and deliberately reduce its bandwidth allowance, particularly during peak evening hours. A VPN encrypts all your traffic into an undistinguishable tunnel, making DPI-based throttling impossible for your ISP to apply.

When a VPN helps streaming speeds: If your ISP is actively throttling video streaming services. Independent research has confirmed this practice with major US ISPs including Comcast, AT&T, T-Mobile, and Verizon in published studies.

When a VPN hurts streaming speeds: If your ISP is not throttling, a VPN routes traffic through an extra server, adds encryption overhead, and may route data over a less optimal path — typically reducing speeds by 5–20% depending on the VPN provider's infrastructure quality.

How to test: Run a speed test to fast.com without VPN, then with VPN active (connected to a nearby server). If VPN speeds exceed non-VPN speeds by more than 10%, throttling is likely occurring.

Premium VPN services with dedicated high-bandwidth infrastructure — Mullvad, ProtonVPN, ExpressVPN — perform best for streaming. Free VPNs are too congested to improve streaming speeds reliably.

The FCC (Federal Communications Commission) updated its broadband benchmark in March 2024 to 100 Mbps download / 20 Mbps upload as the minimum threshold for a connection to qualify as "high-speed broadband." This replaced the prior 25/3 Mbps standard established in 2015, which had become woefully inadequate for modern multi-device households.

The FCC's stated long-term goal is 1 Gbps download / 500 Mbps upload as the target benchmark for future infrastructure investment under the $42.5 billion BEAD (Broadband Equity, Access, and Deployment) program funded by the Infrastructure Investment and Jobs Act.

What these numbers mean in practice:

  • 100 Mbps download supports 4K streaming on 2-3 devices simultaneously.
  • 20 Mbps upload enables a single 4K video call or multi-stream upload.
  • For 4+ person households with active gaming, cloud work, and streaming, 500 Mbps+ download is the practical comfort zone.
  • Symmetrical gigabit (1000/1000) is increasingly available via FTTH fiber providers and is the recommended standard for power users and home office setups.

If your ISP advertises speeds that meet these thresholds but your real-world experience is consistently poor, the issue is almost certainly one of the factors NetSymptom diagnoses — not your plan tier.

Accessing your router's admin panel is the most direct way to control how bandwidth is distributed across your home network. Here is the complete process:

  1. Find your router's IP: Windows — open Command Prompt, type ipconfig, look for "Default Gateway." Mac — open Terminal, type netstat -nr | grep default. Most common addresses: 192.168.1.1, 192.168.0.1, 192.168.2.1, or 10.0.0.1.
  2. Open admin panel: Type the IP address directly into your browser's address bar. You'll see a login screen.
  3. Login credentials: Check the label on the bottom or back of your router — credentials are printed there. Common defaults: admin/admin, admin/password, admin/1234. If these were changed and forgotten, a factory reset restores defaults (hold reset button 10 seconds).
  4. Find QoS settings: Look under Advanced, Wireless, or Traffic Management. Labels vary by manufacturer: "QoS," "Bandwidth Control," "Traffic Priority," "Device Priority."
  5. Prioritize your device: Enter your device's IP or MAC address (found in your device's network settings) and set its priority to Highest. This ensures gaming or work traffic gets bandwidth first when the network is contested.

If your router does not offer QoS controls, upgrading to a current-generation Wi-Fi 6 router with full QoS support is the most impactful single hardware upgrade for households with multiple active users.

The two Wi-Fi frequency bands have fundamentally different characteristics that make each suitable for different situations:

2.4GHz: Longer range, better wall penetration, much more congested (shared with microwaves, Bluetooth, baby monitors, and all neighbouring networks that also default to 2.4GHz). Maximum practical speeds of 150-300 Mbps. More susceptible to interference-induced packet loss.

5GHz: Shorter range, less wall penetration, far less congested (more available channels, fewer competing devices), maximum practical speeds of 600 Mbps to 2.4 Gbps depending on Wi-Fi generation. Dramatically lower interference and packet loss when in range.

6GHz (Wi-Fi 6E): Available only on Wi-Fi 6E capable routers and devices. Nearly zero congestion, highest speeds, shortest range. Ideal for devices within the same room or adjacent rooms.

Recommendation: For gaming, video calls, and streaming — always use 5GHz when within range (typically within 10 metres with normal walls). Use 2.4GHz only for IoT devices, smart home sensors, and devices far from the router where speed is less critical. Modern dual-band routers can broadcast both simultaneously; most recent devices will auto-select the better band.

About NetSymptom

Bridging the Gap Between Metrics and Experience

NetSymptom was built out of frustration. After years of watching technically literate people get told "your speed test looks fine" by ISP support agents while their Netflix buffered and their Zoom calls dropped, we decided to build the tool we wished existed.

The diagnostic engine is a deterministic, weighted rule matrix developed from published networking research, ISP performance studies, and real-world troubleshooting patterns. It runs entirely in your browser — no data leaves your device, no account is required, no server processes your inputs.

Our goal is simple: transform opaque network metrics into clear, actionable explanations that any user can understand and act on immediately.

Feedback & Bug Reports