Am I crazy if for something like an online purchase, I kind of expect it to take a second or two to process the payment, so I would assume something went wrong if it was 200ms?
> The person who clicked noticed no delay.<p>Just to be the "actually..." guy: People notice 200ms delay. It's just that in cases it doesn't cause any bad feelings."
I learned three thresholds over the years. Well, one of them decades ago and the others recently. Basically:<p>At 50ms, you notice.<p>At 400ms, you care.<p>At 2000ms, without output, you wonder if it crashed. (That was the old one.)
> At 2000ms, without output, you wonder if it crashed. (That was the old one.)<p>That must have been a really, really long time ago indeed, because there are very few websites now that take less than 2000ms to load. The linked site didn’t even come close on my phone (probably 3-4 seconds), and I most certainly didn’t wonder whether it had crashed.
The timing refers to feeling like the device acknowledged your request with some response.<p>Not seeing the final completion of the request.<p>Your phone probably showed something after you clicked the link but before the page rendered: Link highlight change, a progress bar, etc.<p>If your phone had crashed and the browser was non-responsive, you would have recognized it quickly. More quickly than the page load time.
GitHub
[dead]
This is magnificent!<p>Gave me roller-coaster ride across 40 years of gathering knowledge about computers and networks.<p>I'm very jealous of whoever created that. Well done!
While I also enjoyed it very much, some thing are strangely ordered and not how I would expect someone with such knowledge of all the moving parts in a request, would build such a site. So for me it feels like an LLM has build it and the human with the prompt saw it and said "eh, good enough".
Agreed. This reeks LLM writing with no human oversight, or at least a human with no writing experience. The text underneath “The Click” is an immediate giveaway:<p>> Five milliseconds of hardware and browser bookkeeping before a single byte leaves the laptop.<p>I don’t even know how to describe it, but the “[…] before X” sentence style stands out to me.
Wow, input lag is a lot lower than I thought. I thought it was a polling-based flow at some 120 Hz roughly. Good to update these numbers.
Back in the day "what happens when the user types a url in the address bar and press enter" used to be an interview question, and I remember nobody has ever mentioned the hardware and keyboard keys and interrupts. This post does! Pretty awesome detailed view of a request lifecycle.
Wonderful page, congratulations! navigating to the end takes time but the contents and the presentation are great
200ms is insane, 50ms is the goal.<p>But really, great page.<p>Someone new could learn from it the basics of what to check when debugging web.
The US is so big, that 50 ms is physically not possible for everyone.
This is something that not everybody is aware of. When I as a German build something for germans, everyone who needs to wait longer than 100 ms for a request, is rightfully mad. But when I want to serve the same stuff to americans at the same speed, I have to build something completely different and much more complex.
The CSS animation of the encrypted message overwriting the plain is utterly cool.