Tangled Wi‑Fi signal around a small router icon
Wi‑Fi can say “Connected” while Chrome still won’t load anything. The trick is to match what you’re seeing (the symptom) to the most likely cause, then do the smallest fix that tests that cause.

We’ll start mobile-first, then desktop.

Before you begin: try one non-Chrome app on the same Wi‑Fi (a different browser, or a simple app like Weather). That single check tells you whether you’re dealing with Chrome-only or the whole connection.

Use the section that matches your symptom best.

1. Symptom: Chrome says “No internet” (but the Wi‑Fi icon looks fine) on your phone

Likely causes

  • Captive portal is blocking traffic (hotel/coffee shop Wi‑Fi that needs a sign-in page).
  • Private DNS / VPN / content blocker is intercepting requests.
  • Router has internet issues, but your phone is still associated to Wi‑Fi.

Fix map (mobile-first)

  • Force the captive portal to appear: Turn Wi‑Fi off/on, then open Chrome and try visiting http://neverssl.com (plain HTTP often triggers login pages). If a sign-in page appears, complete it and retry your original site.
  • Temporarily disable VPN: If you use a VPN app or “VPN” toggle, turn it off for 2 minutes and re-test Chrome. If that fixes it, the Wi‑Fi network may block VPN traffic, or your VPN DNS is failing.
  • Check Private DNS (Android): Settings → Network & Internet → Private DNS. Switch to Off or Automatic, test Chrome, then switch back later if you prefer using a custom DNS.
  • Forget and re-join the Wi‑Fi: Tap the Wi‑Fi network → Forget → reconnect and re-enter the password. This can fix a “connected but not routed” state.

Phone connected to Wi‑Fi with a portal key icon

If other apps also can’t load, the issue is probably the Wi‑Fi network or its upstream internet—not Chrome.

2. Symptom: Only some sites load on Wi‑Fi in Chrome (others time out)

Likely causes

  • DNS problems (the network can’t resolve certain domains).
  • IPv6 routing is broken on that network (some sites prefer IPv6 and fail oddly).
  • A “security” filter on the network/router is blocking categories of sites.

Fix map (mobile-first)

  • Switch to cellular briefly: Turn off Wi‑Fi, load the same site on mobile data. If it loads on cellular but not Wi‑Fi, you’ve confirmed it’s the Wi‑Fi path (DNS/routing/filtering).
  • Change DNS inside Chrome (if you can reach Chrome settings): Chrome → Settings → Privacy and security → Use Secure DNS. Try Automatic, and if that fails try a provider option. Re-test the problem site.
  • Try another browser once: If the same sites fail in another browser on Wi‑Fi, it’s almost certainly DNS/routing/filtering on the network.
  • Try “Forget network” + reconnect: It’s simple, but it often refreshes DNS and routing assignments from the router.

If you’re on a work/school Wi‑Fi, selective blocking can be intentional. The safe next step is to test on a different Wi‑Fi network (or your hotspot) rather than fighting the policy.

3. Symptom: Chrome loads very slowly on Wi‑Fi on your phone, but speeds are fine elsewhere

Likely causes

  • Chrome data saver / preloading behavior interacting poorly with the network.
  • Bad cached network state (stale sockets) after switching between networks.
  • Router congestion or weak signal causing retries that look like “Chrome is slow.”

Fix map (mobile-first)

  • Toggle Airplane mode for 10 seconds: This resets radios cleanly without changing settings. Then turn Wi‑Fi back on and re-test.
  • Restart Chrome: Fully close it (app switcher) and reopen.
  • Clear Chrome cache (not cookies) first: Chrome → Settings → Privacy and security → Clear browsing data → select Cached images and files. Keep cookies unchecked initially so you don’t get logged out.
  • Check signal quality: Move closer to the router for one test. If it suddenly improves, it’s not a Chrome problem—focus on Wi‑Fi coverage (2.4 GHz vs 5 GHz, mesh node placement, interference).

When the “slow” feeling is actually Wi‑Fi retries, no Chrome setting will fully fix it—you have to stabilize the connection.

4. Symptom: Chrome works on your phone via hotspot/cellular, but fails on home Wi‑Fi (desktop also affected)

Likely causes

  • Router DNS is misbehaving or upstream DNS is down.
  • Router firmware is stuck or memory-leaking (common after long uptime).
  • ISP outage or partial outage (some routes work, others don’t).

Fix map (do this at home, in order)

  • Power-cycle modem + router: Unplug both. Wait 60 seconds. Plug in modem first, wait until it’s fully online, then plug in router. Re-test Chrome.
  • Try a different DNS on the router (or device): If you’re comfortable, set DNS to a well-known provider on the router, or use Secure DNS in Chrome as a quicker test. DNS issues often look like “spinning” or “server IP address could not be found.”
  • Check if only one device is affected: If desktop and phone both fail on the same Wi‑Fi, stop clearing browser data—focus on the network path.

Router link to DNS server with a broken connection symbol

If a full reboot fixes it for a day and then it returns, look at router firmware updates or replace aging hardware.

5. Desktop checks (Windows/Mac/Linux): Wi‑Fi connected, Chrome won’t load or says DNS errors

Likely causes

  • Bad DNS cache on the computer.
  • Proxy setting or security software intercepting traffic.
  • Chrome profile/network stack stuck after sleep or network switching.

Fix map (desktop)

  • Try a non-Chrome app first: If another browser also fails, don’t spend time resetting Chrome—fix Wi‑Fi/DNS on the machine or router.
  • Disable proxy (quick check): If you don’t intentionally use one, ensure system proxy is off. A leftover proxy can make Chrome look “offline.”
  • Flush DNS cache: On Windows, flush DNS from an elevated command prompt; on macOS, restart the device (simplest) or flush via Terminal if you’re comfortable. Re-test the same site.
  • In Chrome, try Secure DNS: Settings → Privacy and security → Security → Use Secure DNS. Toggle it and re-test. If toggling changes behavior, the problem is strongly DNS-related.
  • Reset Chrome network state (light touch): Close Chrome completely and reopen. If it’s still stuck, restart the computer before doing heavy resets like “Reset settings.”

Laptop Wi‑Fi icon with shield and ethernet plug nearby

If the issue happens only on one Wi‑Fi network (but not on hotspot), that’s your cleanest clue: it’s not your Chrome profile.

Final thoughts

“Connected to Wi‑Fi” only means you joined the local network. The symptom→cause approach helps you confirm whether the break is login portal, DNS, VPN, router, or Chrome itself.

If you can reproduce the problem on multiple devices on the same Wi‑Fi, stop clearing browser data and focus on the router/ISP path instead.