What should I check first for websites not loading?

Start by validating the scope of the issue: check whether it affects one device, one room or the whole connection, then compare Wi‑Fi and Ethernet where possible.

Can Wi‑Fi cause websites not loading?

Yes. Weak Wi‑Fi, interference, router placement and device limitations can cause many broadband symptoms even when the line itself is working.

When should I contact my provider?

Contact your provider if the problem affects Ethernet as well as Wi‑Fi, router or ONT lights show a service fault, or repeated tests prove the issue is outside your home network.

Websites Not Loading But Internet Works? Validate DNS and Browser Causes

DNS and browser troubleshooting

Websites Not Loading But Internet Works?

This guide helps you validate whether websites are failing because of DNS, browser cache, device settings, security software or a wider broadband problem.

Run speed test Broadband issue hub

Issue

Symptoms of Websites Not Loading

Use these signs to confirm that browsing is the failing layer before changing router settings, replacing hardware or contacting your provider.

Apps work but websites do not load: Apps such as Spotify, Discord or Steam can use dedicated ports and direct IP routes, while browsers depend on ports 80 and 443 plus DNS translation. If your router firewall mishandles HTTPS traffic, or your local DNS cache is corrupted, apps can keep working while web pages fail to resolve or load.
Some websites load while others time out: Larger modern services often prioritise IPv6, while smaller sites may still rely mainly on IPv4. If your provider IPv6 route is unstable, or your router miscalculates MTU size, some sites can stall because packets are too large or take the wrong path.
One browser fails while another works: If Chrome fails while Edge, Firefox or Safari works, the internet connection is probably not the root cause. A browser extension, ad blocker, privacy tool or corrupted cookie store can lock up page scripts and make that one browser appear offline.
You see DNS, certificate, proxy or connection reset errors: Secure websites rely on DNS resolution and SSL/TLS handshakes. A bad DNS cache, stale proxy setting, invalid certificate state or incorrect device clock can trigger errors that block websites even though the connection is live.
The issue affects one device more than the rest: A stale DHCP lease, orphaned VPN adapter or ghost proxy hook can trap one device's web traffic in a broken local route, leaving other household devices browsing normally.

Likely causes

Most Common Causes

The same symptom can have several different causes. Start with the causes below, then use the validation steps to prove which one is most likely.

DNS failure

ISP server overloading: DNS translates web addresses into IP addresses. If provider DNS servers are overloaded, browsers can show errors such as ERR_NAME_NOT_RESOLVED while already-connected apps continue to work.

Local cache corruption: Devices store previous website lookups locally. If that cache becomes stale after a website, certificate or network change, the browser may keep trying a dead route.

DNSSEC handshake timeouts: Secure DNS validation can fail if device time, router state or DNS responses are inconsistent, stopping websites before the page even begins loading.

Browser cache or extension issue

Extension script deadlocks: Ad blockers, tracking shields and privacy extensions inject code into pages. If they conflict with a site update, the browser can lock up and mimic a broken connection.

Corrupted DOM storage and cookies: Broken local site data can cause malformed requests, login loops, 400 errors or connection resets on specific websites.

Mismatched SSL/TLS session state: Browsers cache secure handshakes. If a site changes its security configuration while the browser holds stale state, certificate validation can fail.

VPN, proxy or filtering

MTU size mismatch fragmentation: VPN encryption wraps packets in extra data. If packets become too large for the route and fragmentation fails, large websites can hang while smaller requests appear normal.

Orphaned network adapter hooks: Failed or uninstalled VPN/security tools can leave ghost adapters, proxy rules or routing table entries that send browser traffic into a dead tunnel.

Parental control and content filter false positives: Router, ISP or security filters can silently block shared IP addresses, background scripts or categories, leaving the browser spinning without a clear error.

Device network settings

Stale DHCP lease conflicts: A waking device can reuse an expired local IP address that the router has already assigned elsewhere, causing web access to freeze on that device only.

Hardcoded custom server conflicts: Work profiles, old troubleshooting changes or software installs can leave static DNS or proxy settings pointing at servers that no longer respond.

Aggressive adapter power-saving throttle: Low-power network modes can reduce the performance of a Wi‑Fi card enough that browser requests time out under heavier page loads.

Website or provider routing issue

IPv6 Path MTU Discovery failure: Some modern sites prefer IPv6. If the provider IPv6 gateway or router MTU handling is flawed, IPv6-heavy sites can fail while IPv4 sites still load.

Sub-optimal ISP peering bottlenecks: If your provider has poor capacity toward a hosting network such as a large cloud platform, only websites on that route may time out.

BGP routing failures: Wider internet routing problems can send traffic into a broken path, affecting groups of websites while your home connection itself remains active.

Validate

Steps to Narrow Down the Root Cause of the Issue

Work through these checks in order. Change one thing at a time so the result tells you something useful.

1
Try more than one website and one browser.
This isolates browser script deadlocks and cookie corruption from wider protocol failures. Open an Incognito or Private Browsing window with extensions disabled. If sites load there, the connection is fine and the cause is likely a browser cache or extension issue.
2
Test apps, streaming or email to see whether internet works outside the browser.
This separates DNS translation or port-specific browser failures from a complete outage. If apps keep streaming while the browser spins, your line is active and the likely fault is DNS, HTTPS filtering or browser configuration.
3
Try another device on the same Wi‑Fi.
This isolates a network-wide problem from a single-device fault. If a phone loads pages instantly beside the failing laptop, the broadband line and router are not the main cause; look at device network settings.
4
Turn off VPN/proxy temporarily for testing.
This removes encryption tunnels, proxy wrappers and MTU size changes from the path. Do not just close the VPN window; check that no ghost virtual adapters, proxy settings or routing rules remain enabled.
5
Restart the device and router if multiple devices are affected.
This flushes stale DHCP leases, router NAT tables, RAM and cached DNS state. Use a clean power cycle by unplugging the router and affected device from wall power for 60 seconds before reconnecting.
6
Try mobile data to confirm whether the website itself is down.
This checks whether the target website is unreachable everywhere or only through your home broadband. If the site loads on mobile data but fails at home with errors such as ERR_CONNECTION_TIMED_OUT, suspect provider routing, IPv6 MTU or a path-specific issue.

Fix

Problem Resolution

Apply the fix that matches the cause you validated. If the issue is proven outside your home network, gather evidence before contacting your provider.

Clear browser and disable extensions

Target cause: Browser cache or extension issues, ad-blocker script deadlocks and stale SSL/TLS session state.

Why it works: Clearing site data and disabling extensions removes local execution loops, corrupted cookies and broken secure handshake state.

Critical step: In Chrome or Chromium browsers, test whether QUIC is involved by typing chrome://flags, searching for Experimental QUIC protocol, and setting it to Disabled. This forces a more compatible TCP path for testing.

Reset device network settings

Target cause: Device network conflicts, stale DHCP leases, hardcoded proxy loops and orphaned VPN routes.

Why it works: Rebuilding the local network stack removes invalid routes so traffic can flow directly to the router again.

Critical step: On Windows, open Command Prompt as Administrator and run netsh int ip reset, then ipconfig /flushdns. On Apple devices, test with Private Relay or Limit IP Address Tracking switched off.

Check DNS and filtering

Target cause: DNS failure, overloaded ISP DNS and parental/security filter false positives.

Why it works: Moving to reliable public DNS can bypass provider lookup delays and stabilise website address translation.

Critical step: In your router or device network settings, test public DNS such as Cloudflare 1.1.1.1 and Google 8.8.8.8. Also remove custom proxy, VPN, parental control or security filter rules while testing.

Escalate only if all devices and sites fail

Target cause: Website/provider routing issues, IPv6 Path MTU Discovery failures and wider routing deadlocks.

Why it works: Escalating only after cross-device, cross-browser testing avoids blaming the provider for a single broken app, browser or device.

Critical step: If multiple websites fail only on home broadband but work on mobile data, record exact browser error codes and test with a reputable VPN. If the VPN fixes the issue, you have strong evidence of a provider routing or peering problem.