new | show | ask | jobs Github

zahlman 7 hours ago

I learned three thresholds over the years. Well, one of them decades ago and the others recently. Basically:

At 50ms, you notice.

At 400ms, you care.

At 2000ms, without output, you wonder if it crashed. (That was the old one.)

▲

p-e-w 7 hours ago | parent [-]

> At 2000ms, without output, you wonder if it crashed. (That was the old one.)

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.

▲

Aurornis 6 hours ago | parent | next [-]

The timing refers to feeling like the device acknowledged your request with some response.

Not seeing the final completion of the request.

Your phone probably showed something after you clicked the link but before the page rendered: Link highlight change, a progress bar, etc.

If your phone had crashed and the browser was non-responsive, you would have recognized it quickly. More quickly than the page load time.

▲

thenthenthen 5 hours ago | parent | prev | next [-]

I dunno man, i am In China.. everything outside of it takes at least 2000-5000 ms to even start responding on a good day

	▲	inigyou 4 hours ago \| parent [-]
		That is your government trying to block you

▲

Crunchified 6 hours ago | parent | prev | next [-]

I'm finding more and more web sites that won't load at all until I request them a second time.

	▲	dylan604 4 hours ago \| parent [-]
		maybe the site's debouncing logic on the buttons isn't working well

▲

bloppe 7 hours ago | parent | prev | next [-]

GitHub

▲

hobonation 6 hours ago | parent | prev [-]

[dead]