Giters

mlibrary / search

A single-page web application that consolidates the library’s multiple discovery interfaces into one.

Home Page:https://search.lib.umich.edu/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Response times should be 1 second or less, otherwise use a loading indicator.

jonearley opened this issue · comments

commented

For the most seamless user experience, response times from user interaction to response should be 1 second or less. If this is not feasible, we must identify those 1-10 second wait times and add a loading indicator to mitigate losing the user's attention and keep them on track. If the wait time is over 10 seconds, we are at high risk users will abandon the site.

  • @varnum Plans the time and resources of the team to make this happen.
  • Identify ways to accurately measure and analyze application performance to find areas of improvement.
  • @bertrama Evaluate and make response time improvements targeting 1 second or less. If 1 second is not possible, then please identify these slow requests so that we add an appropriate loading indicator.
  • @jonearley Evaluate and make response time improvements to the front end.
  • @jonearley Work with design and UX to add loading indicators to areas where we can't meet our 1 second target.
  • @bnhowell UX consultation and usability testing of loading indicators.
  • @Treevore Provides loading indicator designs.

Success Criteria
Responses times are 1 second or less. If longer and can no longer be improved, then add a loading indicator in the UI. The loading indicator has been tested with users and is effective.

Evidence
Website Response Times
https://www.nngroup.com/articles/website-response-times/

  • 0.1 seconds gives the feeling of instantaneous response — that is, the outcome feels like it was caused by the user, not the computer. This level of responsiveness is essential to support the feeling of direct manipulation (direct manipulation is one of the key GUI techniques to increase user engagement and control.
  • 1 second keeps the user's flow of thought seamless. Users can sense a delay, and thus know the computer is generating the outcome, but they still feel in control of the overall experience and that they're moving freely rather than waiting on the computer. This degree of responsiveness is needed for good navigation.
  • 10 seconds keeps the user's attention. From 1–10 seconds, users definitely feel at the mercy of the computer and wish it was faster, but they can handle it. After 10 seconds, they start thinking about other things, making it harder to get their brains back on track once the computer finally does respond.
commented

Moved to SEARCH-3 in jira.