Three dominant themes in the discussion
1. Perceived latency thresholds
Users repeatedly reference the “magic numbers” that define when a delay becomes noticeable.
“At 50ms, you notice. At 400ms, you care. At 2000ms, without output, you wonder if it crashed.” — zahlman
“That must have been a really, really long time ago … I most certainly didn’t wonder whether it had crashed.” — p-e-w
These thresholds shape expectations: a few‑hundred‑millisecond lag feels fine, while a couple‑second pause often raises suspicion that the site has frozen.
2. Real‑world performance frustrations
Many commenters share practical experiences of sites behaving unexpectedly or requiring repeated interaction.
“I’m finding more and more web sites that won’t load at all until I request them a second time.” — crunchified
The consensus is that modern pages often exceed users’ tolerance for latency, leading to confusion, perceived crashes, or the need to retry.
3. Skepticism about the article’s authorship & style
A recurring suspicion is that the piece reads like AI‑generated prose, prompting critiques of its tone and structure.
“The text underneath “The Click” is an immediate giveaway:
Five milliseconds of hardware and browser bookkeeping before a single byte leaves the laptop.” — mimischi
“If this were rewritten in second person … it would make it a heck of a lot more readable.” — half‑the‑time (paraphrased from the thread)
The community’s reaction underscores doubts about human editorial oversight, with several remarks labeling the writing style as “LLM‑like” or “mic‑drop”‑heavy.