DeviceTriage
Troubleshooting guide

Why is my internet slow?

Use transparent transfer measurements and repeatable comparisons before blaming the browser, router, or ISP.

Measure this connection

Common symptoms

  • Downloads take longer than expected
  • Streaming quality drops or buffers
  • Performance changes by room, device, or time of day

Possible causes

  • Weak Wi-Fi signal or radio congestion
  • Other devices consuming available bandwidth
  • VPN, mobile routing, or server-region limitations
  • ISP plan, line quality, or temporary service congestion

How to diagnose it

  1. Run DeviceTriage Network Test and note its route-specific limitation
  2. Repeat near the router and, if possible, over Ethernet
  3. Pause VPNs, backups, downloads, and streaming on other devices
  4. Compare at different times and against the ISP's own test endpoint

Solutions to try

  1. Improve access-point placement and use the appropriate Wi-Fi band
  2. Use Ethernet for fixed high-bandwidth devices
  3. Limit background transfers and unnecessary VPN routing
  4. Restart equipment only as a diagnostic step, not a permanent routine
  5. Share repeatable wired test results with the ISP

The first 10-minute diagnosis

  1. Pause VPN, cloud sync, downloads, uploads, and streaming on other devices for one controlled run.
  2. Run the DeviceTriage network test twice and record the time, connection type, and range—not only the best number.
  3. Repeat near the router and over Ethernet if the device supports it.
  4. Compare a nearby independent or ISP endpoint because every server route is different.

Decision path by result

Ethernet is good but Wi-Fi is slowFocus on signal, interference, access-point placement, band, channel, and mesh backhaul.
Every device is slowInspect modem/router status, active transfers, ISP service, and wired line evidence.
Only one service is slowThe service, route, region, account, or CDN is more likely than total line capacity.
Speed is good but calls or games lagPrioritize latency, jitter, request loss, upload saturation, Wi-Fi stability, and server region.

Platform-specific checks

Wi-Fi

Compare distance, obstacles, 2.4/5/6 GHz band, interference, and access-point placement. A full signal icon does not guarantee an uncongested radio channel.

Ethernet

Use a known cable and check negotiated link speed when results remain capped. A damaged cable or 100 Mbps port can create a repeatable ceiling.

Mobile network

Signal quality, tower load, radio mode, movement, indoor coverage, and carrier routing can change within minutes. Compare the same location and time window.

What not to do first

  • Do not treat one browser-to-one-server result as the universal internet speed.
  • Do not factory-reset the router before recording wired and Wi-Fi comparisons.
  • Do not download unknown optimizer or DNS tools that promise to multiply line speed.

When to move beyond a browser test

  • Contact the ISP with time-stamped wired results, modem status, plan speed, and repeatable examples.
  • Escalate one-service problems to that service when other nearby endpoints remain healthy.

Last technical review: 2026-09-01

Frequently asked questions

Is DeviceTriage a replacement for my ISP speed test?

No. It measures transfer to the DeviceTriage region. Use it for a transparent comparison and confirm line speed with a nearby ISP or independent endpoint.

Why do repeated speed results differ?

Wi-Fi contention, server routing, browser load, mobile networks, and other traffic change continuously. A range is more useful than one number.