Confirm the Problem Is Browser-Specific
Before changing any settings, run the same speed test in each browser you have installed: Chrome, Firefox, Safari, and Edge. If results are consistent across all of them, the browser is not the cause and you should use the general slow internet or slow on certain websites guide instead. If one browser is measurably slower or one site loads poorly only in that browser, you have a browser-specific issue.
The most reliable isolation step is to open the slow browser in incognito or private mode and load the same page. Private mode starts without your extensions, most cookies, and active service workers. If private mode is fast, the culprit is something in your regular browser state.
Browser-Specific Causes
| Pattern | Likely Cause | Fix |
|---|---|---|
| Private window is fast | Extension, cookie, service worker | Disable extensions, clear site data |
| Only one profile is slow | Damaged browser profile | Create a fresh profile and compare |
| All sites slow in one browser | Proxy, DNS, security setting | Check browser network settings |
| Videos stutter in one browser | Hardware acceleration or codec path | Toggle hardware acceleration |
| One site broken after login | Cookies or cached app state | Clear that site's data only |
Fix 1: Disable Extensions in Batches
Extensions are the most common cause of browser-only slowdowns. Ad blockers, privacy tools, coupon finders, password managers, security extensions, VPN extensions, and developer tools all inject code or intercept network requests. Some proxy every request through their own servers before forwarding it, adding meaningful latency to every page load.
Disable all extensions at once, restart the browser, and test. If things improve, re-enable them one at a time until you find the offender. In Chrome, open chrome://extensions. In Firefox, open about:addons. In Edge, open edge://extensions. Browser-level VPN or proxy extensions deserve extra scrutiny because they affect every request.
Fix 2: Check Browser Proxy and DNS Settings
Each browser can be configured with its own proxy server and its own DNS resolver, completely independent of your OS network settings. That means one browser can take an entirely different network path than the rest of your computer.
In Chrome, go to Settings → System → Open your computer's proxy settings, or check if any extension has set a proxy. In Firefox, go to Settings → Network Settings and look for any manually configured proxy or SOCKS server. Edge inherits Windows proxy settings by default but extensions can override this.
DNS-over-HTTPS is another common cause. Each browser has its own secure DNS setting that may point to a different resolver than your OS uses. A slow or misconfigured DoH provider can make one browser's DNS lookups take hundreds of milliseconds while other browsers resolve the same domain instantly. In Chrome, check Settings → Privacy and security → Security → Use secure DNS. In Firefox, check Settings → Privacy & Security → DNS over HTTPS.
Fix 3: Chrome-Specific Fixes
Chrome has several internal pages useful for diagnosing slow browsing. Navigate to chrome://net-internals/#dns and use the Clear host cache button to flush Chrome's DNS cache independently of the OS. This is useful when you have changed DNS resolvers but Chrome is still using cached old results.
Chrome also uses the QUIC protocol by default for connections to Google services and other supporting sites. On some networks, QUIC traffic is deprioritized or blocked, causing those connections to be slower than standard HTTPS. You can disable QUIC at chrome://flags/#enable-quic and test whether the affected sites improve. Hardware acceleration conflicts with certain GPU drivers can cause video and WebGL to stall; toggle it at Settings → System → Use hardware acceleration when available, then restart Chrome.
Fix 4: Firefox-Specific Fixes
Firefox exposes fine-grained network settings through about:config. Search for network.http.max-persistent-connections-per-server to see how many simultaneous connections Firefox opens to a single server. The default is usually 6. Increasing it can help on sites that serve many assets, but it rarely causes slowdowns on its own.
The DNS-over-HTTPS setting in Firefox defaults to Cloudflare's 1.1.1.1 in some configurations. If your ISP or corporate network has a faster resolver or if Cloudflare's path is poor from your location, switching to a different DoH provider or disabling DoH entirely can improve lookup times. Go to Settings → Privacy & Security → DNS over HTTPS and select your preferred provider or turn it off.
Firefox also stores a network cache and an image cache separately from cookies. Clearing the cache at about:preferences#privacy does not clear cookies, and clearing cookies does not clear cached assets. Use the More info link on the Clear Data dialog to understand exactly what each option removes.
Fix 5: Cache vs Cookie Clearing
Many guides say to clear the cache, but cache and cookies are different things with different effects. The browser cache stores copies of CSS, JavaScript, images, and fonts so they load faster on repeat visits. A corrupted cache entry can cause a page to break or behave strangely for one specific site. Clearing the cache for only that site, rather than your entire history, is always the better first step.
Cookies store authentication tokens and session state. Clearing cookies logs you out of websites. If a site is slow after login but fast before it, the issue is more likely a corrupted cookie or cached service worker than a general cache problem. In Chrome and Edge, right-click any page, open Inspect, go to Application → Storage, and click Clear site data for the affected origin only.
Fix 6: Try a Fresh Browser Profile
A fresh profile starts completely clean: no extensions, no old settings, no accumulated cache, no proxy configuration carried over from months of browser use. If browsing is fast in a fresh profile and slow in your regular one, the problem is in your profile state, not your internet connection or the browser itself.
Fix 7: Toggle Hardware Acceleration
If the browser is fast for normal text pages but slow or stuttering for video, maps, animations, or WebGL-heavy sites, hardware acceleration may be conflicting with your GPU driver. This often surfaces after a driver update or OS upgrade. Toggle hardware acceleration off, restart the browser, and test the affected pages. If those pages improve, the fix is usually updating your GPU driver to a stable release.
Frequently Asked Questions
Why is only Chrome, Safari, Edge, or Firefox slow?
If other browsers are fast, the slow browser likely has an extension, cache, profile, proxy, DNS, hardware acceleration, or site-data problem. Running the speed test in each browser is the fastest way to confirm the issue is browser-specific.
Should I clear all browser data?
Start smaller. Test private mode, disable extensions, and clear data for the affected site first. Clearing everything can sign you out of accounts and may not be necessary if the problem is limited to one extension or one site's cached data.
Can browser DNS settings make sites slow?
Yes. Some browsers use DNS-over-HTTPS or secure DNS settings that differ from your system DNS. If the DoH provider is slow or routes you to a distant CDN node, browsing can feel noticeably sluggish in that browser while others remain fast.