How to Simulate a Slow Internet Connection in Chrome on Windows

Your website loads quickly on your connection, but you’re hoping it still works for visitors with slower internet. Chrome DevTools can simulate reduced speeds, added latency, and offline access without changing your Windows network settings.

Fix #1: Test the page with a Chrome throttling preset

Chrome includes presets for quick page-load checks. Slow 4G is a sensible starting point, while 3G exposes heavier pages more clearly.

1. Open the page you want to test in Google Chrome.

2. Press Ctrl + Shift + I to open DevTools. You can also select Customize and control Google Chrome > More tools > Developer tools.

3. Select Customize and control DevTools if you want to change its position, then choose a dock location.

4. Select the Network panel. If it isn’t visible, select the >> overflow button and choose Network.

5. Open the throttling dropdown, which normally displays No throttling.

6. Select Fast 4G, Slow 4G, 3G, or Offline.

7. Press Ctrl + R while DevTools remains open to reload the page.

The Network panel should fill with requests for images, scripts, fonts, and other resources. Check the Time and Waterfall columns to see what delayed the page.

Throttling applies to the tested browser context rather than your whole Windows connection. Other apps and tabs shouldn’t behave like they’re using a slow Wi-Fi router.

Fix #2: Create a custom network throttling profile

A custom profile lets you test a specific download rate, upload rate, and latency. That’s useful when Chrome’s presets don’t resemble your visitors’ connections.

1. Open DevTools and select Settings.

2. Select Throttling.

3. Find Network throttling profiles, then select Add profile.

4. Enter a descriptive profile name.

5. Enter the required download speed, upload speed, and latency values.

6. Add any optional packet-related values available in your Chrome version.

7. Select Add or close Settings after saving the profile.

8. Return to the Network panel and select your profile from the throttling dropdown.

9. Reload the page with Ctrl + R.

Your custom profile should remain selected while the page reloads. So far, so good if the site completes its main content before slower third-party requests finish.

Fix #3: Throttle one request in Chrome 145 or later

Current Chrome releases can throttle one script, image, or API request without slowing every resource. This helps isolate a troublesome dependency.

1. Open DevTools and select Network.

2. Reload the page so its requests appear.

3. Right-click the request you want to test.

4. Select Throttle request.

5. Configure the request in the Request conditions drawer.

6. Reload the page.

The selected request should now respond under the assigned condition. Other requests should continue working as expected unless they depend on that resource.

If Throttle request doesn’t appear, update Chrome and reopen DevTools. Individual request throttling requires Chrome 145 or later.

Fix #4: Test more realistic network problems

Chrome DevTools is useful for browser-only checks, but its throttling doesn’t fully reproduce packet loss, jitter, radio interference, or every connection-level failure. Use a different method when those details affect the bug.

1. Choose an HTTP(S) proxy such as Charles Proxy when you need traffic inspection and request-level throttling.

2. Choose mitmproxy when you need an open-source proxy with scriptable request controls.

3. Use Linux tc with netem when you need kernel-level delay, jitter, packet loss, reordering, or bandwidth limits.

4. Run the same page test under the selected condition and compare it with Chrome’s results.

A proxy or packet-level emulator should reveal failures that a DevTools preset doesn’t reproduce. I’d skip this step unless browser throttling leaves a specific field issue unexplained.

When throttling doesn’t match real-world results

Test on a physical device and connection if timing still looks unrealistic. Device performance, cached files, extensions, a crowded wireless adapter, and remote server behavior can all change the result independently of bandwidth. Consider using a USB Wi-Fi Adapter or a Cat6 Ethernet Cable for a more stable connection.

Conclusion

Fix #1, using Slow 4G or 3G, is the solid choice for a quick website check and usually exposes oversized resources. If the problem involves dropped packets or unstable latency, use a proxy or packet-level emulator before recommending a site change.