A lot of people judge an internet connection by one number: Mbps. The higher it is, the better the connection must be. Except that in day-to-day use, raw speed is only part of what makes something feel fast.
Latency is basically the time it takes for data to travel from one place to another and come back. You can have a very fast connection with plenty of bandwidth, but if every request takes too long to respond, the experience still feels sluggish. It’s especially noticeable with remote desktops, gaming, voice calls, real-time applications and anything that constantly exchanges small amounts of data.
I find it interesting because it’s another example of how specifications can be technically correct while still telling only half the story. A 1 Gbps connection sounds impressive, but if the systems behind it are badly designed, geographically distant or constantly waiting on other services, throwing more bandwidth at the problem won’t magically fix it.
This is one of those things that changed how I look at performance in general. Faster hardware and bigger connections are useful, obviously, but good technology is often less about how much you can push through a system and more about how quickly the system reacts when somebody actually asks it to do something.
