Yes. Two seconds is usually regarded as the rection time threshold where an ineractive system starts to turn into a batch system. It is long enough for the user

Yes. Two seconds is usually regarded as the rection time threshold where an ineractive system starts to turn into a batch system. It is long enough for the user to start to forget what he expects from the system or to think about swiching to another activity while the current one loads. That is also the reason why database transaction benchmarks are always defined by number of transactions per second at a response time of slightly under two seconds, that is the threshold where they can still claim that the benchmark measures something about a system that is actually usable in practice. So cutting response times by a second from say two seconds to one second changes the percieved delays from barely tolereble to barely noticable, which is unually beneficial for interactive apps.