The internet is fast but pages crawl: the DNS check before you blame the line

When a video plays smoothly but a new website takes several seconds to appear, the internet connection may be fine. Your device first asks a DNS resolver for the site's address; only then does it connect to the site. A tired resolver, a broken router cache or a filtering service can make the first step slow while an already-open stream looks perfect. The fix begins by proving which step is late.

The two comparisons

• Compare devices: open the same new site on a phone and a laptop on the same Wi-Fi, then once on the phone's mobile data. One slow device points to its local DNS or browser; every device on the Wi-Fi points to the router, resolver or line.
• Compare new and known connections: an already-playing stream is a poor speed test because its address was found earlier. Open several unrelated sites and an app that uses a different service. If all new connections hesitate but downloads are steady after they begin, name resolution is a reasonable suspect.
• Watch the first request: a terminal lookup tool such as nslookup or dig can show whether the name query waits before an answer. You do not need to understand every field; compare the delay for the same name through the router's resolver and a trusted public resolver. A failed lookup is stronger evidence than a feeling that browsing is slow.

The least destructive fix

Restart the router once and check whether its firmware is current. Then set a trusted DNS service on one device, not the whole house, and compare for a day. The exact menu differs by operating system; use the device's network settings and write down the old values before changing them. Faster is not guaranteed: a resolver close to you may beat a famous resolver, and a DNS service can also apply filtering or logging policies that matter more than a small timing difference. If the comparison changes nothing, put the old setting back and investigate Wi-Fi interference, packet loss or the provider's route instead.

Never use a DNS change to hide a security warning or to make an unreachable service appear legitimate. A resolver can translate a name; it cannot repair a bad cable, a congested radio channel or a server that is down. The desk's boundary is the useful one: if names are slow, test DNS; if every address is slow after lookup, stop editing resolver boxes and return to the network.