Fix Slow Establishing Secure Connection in Chrome

This guide fixes the frustrating delay where Chrome hangs on “Establishing secure connection” before loading a website. The steps below clear outdated security settings, adjust DNS and network protocols, and disable conflicting extensions, which together resolve the majority of slow-connection issues in Chrome.

What You’ll Need

• Access to Chrome’s settings and flags (no admin rights required for most steps)
• Your router’s login details if you need to adjust DNS settings at the network level (optional)
• About 15 minutes of time

Step-by-Step

1. Clear Chrome’s SSL state. Go to Chrome menu (three dots) > Settings > Privacy and security > Security. Scroll down to Advanced and click Manage certificates. In the window that opens, go to the Trusted Root Certification Authorities tab, select any certificates that look expired or unfamiliar, and click Remove. Be careful not to remove standard ones (like DigiCert or GlobalSign). This resets Chrome’s cached certificate validation.
2. Flush the DNS cache. Open Command Prompt (Windows) or Terminal (Mac/Linux). Type ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (Mac) and press Enter. Restart Chrome.
3. Enable or disable QUIC protocol. In Chrome’s address bar, type chrome://flags and press Enter. Search for Experimental QUIC protocol. If it’s enabled, set it to Disabled; if disabled, set it to Enabled. Then click Relaunch. This forces Chrome to use a different network stack for HTTPS.
4. Change your DNS provider. Go to your network adapter settings (Control Panel > Network and Sharing Center > Change adapter settings on Windows; System Preferences > Network on Mac). Change the DNS to a public resolver like 8.8.8.8 and 8.8.4.4 (Google) or 1.1.1.1 and 1.0.0.1 (Cloudflare). This avoids slow ISP DNS servers.
5. Disable problematic extensions. Type chrome://extensions in the address bar. Toggle off all extensions, then restart Chrome. If the problem disappears, turn them back on one by one to find the culprit. Pay special attention to VPN, ad-blocker, and security extensions.
6. Reset Chrome’s network settings. In Chrome, go to Settings > Advanced > Reset and clean up > Restore settings to their original defaults. This resets startup page, new tab page, search engine, and pinned tabs, but does not delete bookmarks or passwords.
7. Check for malware. Run a full system scan with your antivirus or Windows Defender. Some malware modifies proxy settings or injects scripts that slow down HTTPS handshakes.
8. Update Chrome and your OS. Go to Chrome menu > Help > About Google Chrome to check for updates. Also install pending Windows or macOS updates, as they often include TLS stack fixes.
9. Adjust your router’s MTU (optional). Log into your router’s admin page (usually 192.168.1.1 or 192.168.0.1). Look for WAN or Internet settings and lower the MTU from 1500 to 1492 or 1400. This helps if the problem is due to fragmented packets.

Common Mistakes

• Removing all certificates – deleting valid root certificates can break HTTPS entirely. Only remove ones that look obviously wrong or expired.
• Changing DNS at the wrong level – if you only change DNS in Chrome’s settings (which Chrome doesn’t have a built-in DNS setting), it won’t work. You must change it in the operating system or router.
• Disabling all extensions permanently – this may fix the issue but you lose functionality. Identify the specific extension instead.
• Skipping the reset step – many users try everything else and miss the simple reset, which often clears corrupted cached data.

Tips

• Use Chrome’s built-in Clean up computer tool (Settings > Advanced > Reset and clean up > Clean up computer) to find harmful software that might interfere with connections.
• If you use a VPN, try disconnecting it entirely. Some VPNs cause handshake delays due to extra encryption layers.
• Test the same website in an incognito window (Ctrl+Shift+N). If it loads fast there, the issue is likely extension-related, not network-related.
• Check if the problem only happens on specific websites. If so, the website’s server might be slow, not Chrome.

Troubleshooting

If the problem persists after all steps, try the following:

• Use a different browser. If Firefox or Edge loads the same site instantly, the issue is Chrome-specific, so consider a full uninstall/reinstall of Chrome (back up your profile first).
• Check your system’s date and time. An incorrect clock can cause certificate validation to fail or hang. Ensure automatic time sync is on.
• Temporarily disable your firewall or antivirus. Some security suites perform HTTPS scanning that adds delay. If the problem goes away, configure the software to exclude Chrome or disable HTTPS inspection.
• Test on another network. Connect your device to a mobile hotspot. If the problem disappears, the issue is your router or ISP. Restart your router and modem.
• Run Chrome with a clean profile. Close Chrome, then open it with the --user-data-dir=C:\temp\chrome-test flag (Windows) or --user-data-dir=/tmp/chrome-test (Mac/Linux). If that works, your main profile is corrupted.

Frequently Asked Questions

Why does Chrome say “Establishing secure connection” for so long?

This message appears during the TLS handshake, where Chrome and the server exchange encryption keys. A slow handshake can be caused by DNS delays, a congested network, or Chrome’s own cached certificate data being outdated.

Will clearing SSL state log me out of websites?

No, clearing SSL state only removes cached certificate information. It does not affect cookies or session data, so you’ll stay logged in.

Is it safe to disable QUIC?

Yes, QUIC is a performance feature that speeds up connections on modern networks. Disabling it is safe and forces Chrome to use the older TCP-based HTTPS, which is more reliable on some networks.

Why does the problem happen only on some websites?

Certain websites have slower servers or use older TLS configurations. If the issue is site-specific, it’s likely not Chrome’s fault. Try the same site in another browser to confirm.

How often should I flush DNS?

Only when you encounter connection issues. Flushing DNS clears your local cache, which can speed up resolution if the cache is corrupted, but doing it too often slows down browsing because your computer has to re-resolve every domain.

Will a VPN fix this problem?

Usually not. A VPN adds another layer of encryption and routing, which can actually make the handshake slower. Only use a VPN if you suspect your ISP is throttling your connection.

Related

• Asus Laptop Sound Not Working: Fixes That Work
• iPhone Photos Album Widget: Setup Guide
• How to Export or Backup a Color Profile in Windows 11