I had an iPhone XR, a hand-me-down from my daughter, as usual. My mailbox holds a lot of email. Checking my email was quick over Wi-Fi at home, but painfully slow over mobile data when I was out.

To me, it was obvious: the mobile network was to blame.

New provider, same wait

I was planning to switch providers anyway: my old mobile plan didn’t include nearly enough data and wasn’t fast enough. So I switched, expecting my email to load faster too. The result: no improvement. Websites loaded and videos played reasonably well on mobile data.

Then the XR broke. I got an iPhone 12, again from my daughter. The same SIM card, the same plan, the same large mailbox – and suddenly checking my email was lightning-fast on mobile data too.

I still don’t know exactly what was wrong with the old phone. But the problem was with the device – its hardware, software or settings.

Your connection starts with your device

We often blame our provider for a slow internet connection. When we check our email, we don’t see what happens before the messages appear.

An internet connection is actually a chain: from the app through your device, then over Wi-Fi or the mobile network and on through the wider network to the server. Each request travels along this path, and the response returns along the same path.

The weakest link sets the pace. A faster connection won’t help much if the app or device can’t keep up; good reception won’t help if the server is slow to respond. So “slow internet” describes the result, not where the problem lies.

The Wi-Fi or mobile signal bars show just one link: how well your device receives the signal from the router or mobile base station it’s connected to. They don’t tell you whether data moves quickly beyond that point, whether many users are sharing the same connection or whether the server at the other end responds quickly.

“Fast” can mean two things

There are two questions behind the word “fast”: How much data arrives each second? And how long does it take to get a response to a request?

Once a video is playing, it mainly needs a large, steady stream of data. The player loads some data ahead of time to ride out brief interruptions. A speed test also transfers larger amounts of data; its download figure shows how much arrives each second.

Syncing a large mailbox is a different kind of task. Among other things, the app checks which messages are new, which have already been read and what’s changed in the folders. That can mean many small follow-up requests, with the next step starting only after the previous request has been answered.

These pauses add up. If a hundred consecutive requests each take a tenth of a second longer, that’s ten extra seconds in total. The individual responses may be tiny.

That’s why a speed test can report a good download speed while your email crawls. It usually also shows a ping value: how long a small test request takes to travel to its test server and back. When many requests follow one after another, this waiting time often matters more than download speed, but the speed test doesn’t measure the actual process of fetching your email.

The swap test: one link at a time

One link at a time, starting with the cheapest. Start with devices and connections you already have. Compare how long the slow task itself takes, running the tests in quick succession. If you change the device, network and service at the same time, you won’t know afterwards what made the difference.

Check the settings first. If new emails arrive late or not at all when you’re on mobile data, it’s worth checking the settings on your iPhone or Android phone: whether the phone is set to reduce data use, whether the email app is allowed to use mobile data, and whether it fetches new messages automatically, at set intervals or only when you check manually. I don’t know whether settings like these played a part in my case.

Same account, different device. Check your email on a PC or tablet you already have, ideally on the same network as your phone. If it’s fast there, that points to a problem with the original device or its app.

Same device, different network. Try the same email check on your phone over Wi-Fi and over mobile data, ideally in the same place – for example, at home with Wi-Fi briefly switched off. But this comparison doesn’t cleanly separate the network from the device: your phone uses different components for Wi-Fi and mobile data. That’s exactly the test that led me astray.

Same device, different service. Keep the device and network unchanged and compare checking email with loading several websites, for example. If only email is slow, it makes more sense to look at the mailbox, app or server. If everything is slow, the connection they share deserves a closer look.

Try a wired connection at home. Connect a computer directly to the router with a network cable rather than using Wi-Fi, and repeat the same task. The internet connection stays the same; you’re only removing the Wi-Fi link. If it’s noticeably faster with the cable, start by investigating your home Wi-Fi.

Switching providers made sense because I needed more data, but it didn’t help with email. The revealing comparison – the same SIM card in a different device – happened by chance when I got the hand-me-down iPhone 12.

If nothing you change helps, look at what you haven’t changed.

Which link turned out to be the bottleneck for you – and how did you find it?

Comments

1
Guillermo García Luq
Yesterday
Interesante reflexión.
Like Like like 1 Reply
2
Jan
Yesterday
In my view, following the step "One link at a time, starting with the cheapest," one should try a different email client.
Nowadays, software developers often pay little attention to code optimization, application logic, or how the software interacts with its embedded database. Over time, "junk" accumulates in the database, causing a severe slowdown in read, write, and update operations. Whenever the program attempts an operation, it must wait for a response from the database; naturally, the time required increases in proportion to the "age" of the database and the number of emails stored within it.
Furthermore, the specific algorithm the program uses to query the database is crucial—does it attempt to read the entire database, or just a portion of it?

In short, this is a broad topic for discussion among those interested.

Thanks to the author for the "Friday blogs"—they are quite engaging.
Like Like like 3 Reply
0
Joseph C. Pianta
Yesterday
Forced Obsolescence!
Like Like Reply
0
corser69
Yesterday
Et si le téléphone est un androïd ?
Il suffit parfois de passer par le mode avion pour rafraîchir la connexion !
Like Like like 1 Reply
1
D Duncan
Yesterday
Could try the nuclear option, delete the files ! I periodically clear my Bin, Inbox and Sent folders, probably not an option for some, but works for me, but then I'm a cynical 76 year old.Anything important goes into separate folder.
Like Like like 3 Reply
2
David Gee
Yesterday
Oddly prescient, given today's Microsoft outage…
Like Like like 3 Reply
0
TroySchulz
Yesterday
Maybe it's just because you are using an iPhone. I've had significantly better luck with Android platform - most especially Samsung Galaxy S-series phones or even Google Pixel. I would never go back to Apple again. It's too limiting and too painful.
Like Like like 3 Reply

Add comment

Submit