Test your app on a slow or flaky network
· 9 min read
You build and test your app on fast Wi-Fi, next to your router. Your users don't. They open it on a train, in a lift, at the end of a street with one bar of signal, or on hotel Wi-Fi that is shared with a hundred other people. Some bugs only show up there. The app is fine, until the network is not. This post is a short way to test that before you launch, with tools that cost nothing.
What breaks when the network is slow
I won't quote a statistic about how many people have a bad connection, because I don't have a trustworthy number. You don't need one. Think of the last time your own phone struggled to load a page. The same thing will happen to your users. These are the problems I look for:
- Double submits. The button does nothing for three seconds, so the person taps again. Now there are two orders, two posts or two sign-ups.
- A spinner that never ends. The request fails or hangs, and nothing tells the person. They stare at the spinner and then close the app.
- Timeouts. A request that takes a second on your desk takes thirty on a weak signal. What does your app do at second thirty?
- Lost input. Someone types a long message, taps send, the request fails, and the text is gone.
- Half-loaded screens. The text arrives but the images don't, or the list shows but the buttons need data that never came. The screen looks finished but is not usable.
- Heavy images. A photo that is fine on Wi-Fi can take a very long time on a slow link, and nothing on screen shows that it is coming.
You can see all of these yourself in ten minutes, if you slow your own connection down on purpose.
Slow down a web app: Chrome DevTools
I read Google's Network features reference for Chrome DevTools on 11 November 2026. Open DevTools, go to the Network panel, and use the Throttling drop-down menu. The page says to "select the corresponding preset from the Throttling drop-down menu". It describes how to "emulate fast 4G, slow 4G, or 3G". I won't promise exact preset names, because the page does not list them. Look at the menu in your own version of Chrome.
The same page says that DevTools shows "a warning icon next to the Network panel to remind you that throttling is enabled". That is useful. It is easy to forget that throttling is on and then wonder why everything is slow. To turn it off, choose "No throttling".
Presets are only a start. You can make your own profile. The page says to open the Throttling menu and select "Custom > Add...". The Throttling settings page, which I read on the same day, says you go to Settings, then Throttling, and click "Add profile". A profile has a "Profile Name", download and upload speeds in Kbps, and latency in milliseconds. Make one that is worse than anything you expect, then make one that is just a little slow. The little-slow one shows the bugs people really hit.
Two more things from the same reference:
- Offline. To simulate no connection, "select Offline" from the Network throttling drop-down menu, next to the Disable cache checkbox. DevTools shows a warning icon while offline is on.
- Disable cache. To act like a first-time visitor, "check the Disable cache checkbox". Do this for your first-load test, or your own cached files hide the slow part.
The page also says "In addition to HTTP requests, DevTools throttles WebSocket connections since version 99." So a chat or live feed can be tested too.
Firefox has it too
Mozilla's network throttling page, which I read on 11 November 2026, says "The toolbar includes a Throttling dropdown" in the Network Monitor. The presets it lists are Offline, GPRS, Regular 2G, Good 2G, Regular 3G, Good 3G, Regular 4G/LTE, DSL and Wi-Fi. Your choice "will persist across reloads". Mozilla also warns: "please do not rely on this feature for exact performance measurements." That is the right attitude for all of these tools. They show you what breaks. They are not a lab.
Slow down an Android app: the emulator
The Android Emulator can slow its network. I read two Android developer pages on 11 November 2026. The extended controls page says the emulator "lets you simulate various network conditions". In the Cellular section you pick a network type (GSM, HSCSD, GPRS, EDGE, UMTS, HSPDA, LTE, 5G, or Full) and a signal strength (None, Poor, Moderate, Good or Great). It adds that "Specifying a network protocol is always slower than Full". The page also says some of these options are only available when you run the emulator in a separate window, outside Android Studio.
The command-line page covers the same thing at start-up. The -netspeed option sets upload and download speed, and -netdelay sets latency. For example, emulator @Pixel8_API_34 -netspeed edge. In that page's table, UMTS/3G is 384.0 kbps up and down, and EDGE is 473.6 kbps up and down. For delay, UMTS/3G is a minimum of 35 and a maximum of 200 milliseconds, and GPRS is the same range. You can also give your own numbers. The page notes that these settings apply to Ethernet and Cellular, that -netfast turns throttling off, and that "You can specify startup options when you start the emulator, but not after it has started." So use the extended controls if the emulator is already running.
One more thing I noticed: the same page says the emulator tool is deprecated, and points to an Android CLI command instead. If the flags above do not work on your setup, start from that page.
Slow down an iPhone app: Apple's tools
I read Apple's Tech Talk Adapt to changing network conditions on 11 November 2026. It says: "You can simulate different network conditions with Xcode right in the Devices and Simulators window." It gives an example of picking a network link condition with an LTE profile. For a real phone, it says: "To test your app on an iPhone or iPad, you can use the Network Link Conditioner in Developer Settings." It adds that you can "simulate the same network conditions as in Xcode".
An older, archived Apple guide on testing On Demand Resources describes the same screen. It says "The network link conditioner is available on debug development devices" and that you reach it by "choosing Settings > Developer". From there you can turn it on and off, select a profile, and add or edit profiles. That guide is old, so the menu may look different on your iOS version.
A slow-network test script
Run this on a web app in DevTools, or on a phone with one of the tools above. Use a real phone on real mobile data when you can. Write down what you see at each step.
- First load, slow. Turn on a slow 3G-like profile and tick Disable cache. Open the app from scratch. Does something useful show quickly? Or is it a blank screen for a long time?
- Large images. On the same slow profile, open the screen with your biggest images. Do they have a placeholder, or does the layout jump around when they arrive? Is there a smaller version for phones?
- Slow form, tap twice. Fill in a form and submit it on the slow profile. While it is still loading, tap the button again. Did you get two of whatever it makes? Does the button show it is busy?
- Go offline mid-action. Start an action, such as saving or sending, then switch to Offline before it finishes. What does the screen say? Is it a clear message, or a spinner that never stops?
- Come back online. Turn the network back on without closing the app. Does it recover on its own? Is there a clear button to retry? Does the retry work, or does it fail again?
- Check for lost data. After the failed action, is what you typed still there? Is anything half saved on the server? Open the same record from another device.
- Airplane mode on a phone. Start a request, then switch on airplane mode right away. This cuts the request in the middle, which is harder than a clean offline state. Then switch it off and use the app again.
- Read the error messages. Do the words say what happened and what to do? "Something went wrong" is not enough. "No connection. Your text is saved. Try again" is.
- Weak signal, not no signal. Try a custom profile with high latency and low speed. Real signal is often bad, and it comes and goes, not cleanly off.
Fix the double submit first. It is the one that costs real money and real trust.
Ask your testers to try it on a weak connection
Your testers have real phones, real mobile data and real weak spots. That is worth a lot, but only if you ask for it. Put it in the test task. For more on wording, see how to write a test task. Something like:
"Open the app on mobile data, or with weak signal if you can. Sign up and save one thing. Tell me what happened when it was slow, and if you lost anything."
Then ask for two things back:
- Device and OS version. A slow bug can depend on the phone as well, see testing on phones you don't own.
- Connection type. Wi-Fi, mobile data, or weak signal? "It was slow" means little without this.
The first screen is where slow networks hurt most, so pair this with testing the first 60 seconds of your app.
The slow-network checklist
- Did you test the first load with cache disabled on a slow profile?
- Does something useful show before everything has loaded?
- Do large images have a placeholder and a sensible size?
- Does a button show it is busy and ignore a second tap?
- Do you get one result from a double tap, not two?
- Does going offline mid-action give a clear message, not an endless spinner?
- Does the app recover when the network comes back, and does retry work?
- Is typed input still there after a failed request?
- Did you try airplane mode in the middle of a request on a real phone?
- Does every error message say what happened and what to do next?
- Did you test a mildly slow profile as well as an extreme one?
- Does your test task ask testers to try mobile data or weak signal, and to report device and connection type?
Where TestSwap fits
TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. You can post web, iOS and Android apps, and link to wherever testers can open or install it. Testers use their own phones and their own connections, which is what this test needs.
A review has two public parts, a first impression and a concrete suggestion, and an optional private bug notes box that only you can see. Ask testers to put the slow-network details in the bug notes: the steps, the phone and the connection. You rate the reviews you get, so a tester who writes "the save button froze on mobile data, and I tapped twice and got two entries" is easy to rate well.
Try it
Turn on a slow profile today, tap twice on your most important button, and go offline in the middle of a save. Fix what you find. Then post your app on TestSwap with a test task that asks for mobile data, and review someone else's app first to see how it works. Tell me what's missing or broken (@dizid on X).