200 Milliseconds

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.

Just to be the "actually..." guy: People notice 200ms delay. It's just that in cases it doesn't cause any bad feelings."

This is magnificent!

Gave me roller-coaster ride across 40 years of gathering knowledge about computers and networks.

I'm very jealous of whoever created that. Well done!

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.

But really, great page.

Someone new could learn from it the basics of what to check when debugging web.

The CSS animation of the encrypted message overwriting the plain is utterly cool.