Monday, November 11, 2019

web app - Loading Times / Breaking points


We all know that a user is not going to wait forever for a website to load. Given there are certain factors and circumstances that can apply to this, is there a breakdown of users stages/breaking points that apply to length of time for when loading a website?


I believer there is the general rule of thumb for the amount of time a user will wait in a content stage, but I was curious to know if anybody could elaborate a little more in the phycology of loading times.



Answer



There is a breakdown:


.1 seconds if you don't want a user to notice a delay, 1 second will give a noticeable delay, but will not affect users experience too much and no feedback will be needed, 10 seconds is the maximum amount of time a user wants to wait without a diaglog explaining what the server is doing and how long they should wait, longer than that and they will loose interest.


According to this article the reason behind it is related to short-term memory not exceeding 15 seconds, so slower than that the user begins to forget what they were doing.


Also, according to this article customer satisfaction decresses by 16% for every second they have to wait.



You can speed up a site by reducing image quality, removing flash, or make it more AJAX based.


Visual Break down: enter image description here


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...