In terms of testing I'm assuming you're not planning on observing users and asking "how hard would you like to hurt this proxy for frustration?" What you can realistically test is how it copes under realistic loads and how accurate the predictions are. does it buffer presses whilst loading and also move items around on the display so people press before it's finished and accidentally press the wrong thing? Does it annoyingly eat input soon after you've started to input it so you have to type/scan it again? Amazon says that one second of load lag time would cost them 1.6 billion in sales. 7 loss in conversions which means less money for you. 11 fewer page views which means less people will know about your brand. If you're replacing something that took 3 minutes then it's pretty fast. Just a one-second delay in loading time results in: 16 decrease in customer satisfaction which keeps your audience from coming back. Who are the users and what other systems have they used previously? If it was all writing in a book before then waiting 2 minutes for images is going to be positively slow. How good is the feedback to the user? (does it look like it's broken or have a nice progress bar during the waiting? knowing it's nearly there can help ease the pain, even if the loading times are always consistent). unpredictable is usually the single most annoying thing about waiting)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |