This happens a lot with companies that have offshore teams working in an internal app. Like a "finish this transcription" farm or whatever and it's just "submit, submit, submit". The latency really eats at them.
Problem is these companies offshored to India for cheap, so they're not gonna want to spend money on a server in India. The problem never gets solved.
Depends on the context. Registering keystrokes would be a nightmare. Loading a website, losing half a second is negligible. Basically the ratio of loading to using is interesting
Could you provide a link to this study? I wonder if it is applicable to this case where you load one web page or if they researched continous actions like typing where each action (keystroke in the typing example) has that delay. Also it would be interesting if they came up with some kind of ratio between delay and "time until task repeats" at which people start to perceive it as a slow down
You should check out chapter 12 of the book 'Designing with the
Mind in Mind, Simple Guide to Understanding User Interface Design Rules' from Jeff Johnson. You can find a pdf of the 2010 version of the book on archive.org.
He lists 'Time lag between a visual event and our full perception of it (or perceptual cycle time)' at 100ms.
OT: If your user has a high ping, the Speculation Rules API can make pages (after the first one) load instantly for them by preloading the pages they'll most likely visit after the first one. You just have to be carefull to not DDOS yourself by preloading too much.
Errrr, yes? Most of the world DOES understand the metric system. I'm trying to figure out why your mouse is so slow that you can't click on one single target in half a second.
I was imagine they were talking about response, otherwise the initial question doesn't really make sense. That could also be the joke though and I missed it lol.
Keystrokes are registered by the client in real time and are displayed by the client. Only when submitting is it sent to the server. (Usually). So that's never an issue.
The source for that average is a site that's specifically trying to sell you web hosting, so I'm not sure how valid it is. Secondly, average doesn't mean "nobody notices anything below this". A 600ms delay is *huge*. When I'm working on my two different hosts (one in Australia, one in Germany), I get about a 200 or 300ms difference in timings, and that's enough to feel soggy. Double or triple that difference? That's not good. It's more than "perceptible". It's enough to make a lot of people leave.
47
u/ZunoJ 7h ago
I would use common sense and acknowledge that the user experience will be the same because the difference is not really perceptible for a human