System response time standards

Summary for Response time in man-computer conversational transactions
By Robert B. Miller · 1968 miller1968:

Topic Timing (sec)
Response to control activation 0.1 to 0.2
Response to “System, are you listening?” 3
Response to “System, can you do work for me?” 2 (simple) 5 (complex)
Response to “System, do you understand me?” 2 to 4
Response to identification 0.4 to 0.5 (feedback) 0.2 (confirmation)
Response to “Here I am; what work should I do next?” 10 to 15
Response to a simple inquiry of listed information 2
Response to a simple inquiry of status 7 to 10
Response to a complex inquiry in tabular form 4
Response to a request for the next page 1
Response to “Now, run my problem.” 15
Response to the delay following a keyboard entry versus 3 (keyboard) 2 (light pen)
a light-pen entry of category for inquiry
Graphic response from light pen 0.1
Response to complex inquiry in graphic form 2 to 10

Topic	Timing (sec)
Response to control activation	0.1 to 0.2
Response to “System, are you listening?”	3
Response to “System, can you do work for me?”	2 (simple) 5 (complex)
Response to “System, do you understand me?”	2 to 4
Response to identification	0.4 to 0.5 (feedback) 0.2 (confirmation)
Response to “Here I am; what work should I do next?”	10 to 15
Response to a simple inquiry of listed information	2
Response to a simple inquiry of status	7 to 10
Response to a complex inquiry in tabular form	4
Response to a request for the next page	1
Response to “Now, run my problem.”	15
Response to the delay following a keyboard entry versus	3 (keyboard) 2 (light pen)
a light-pen entry of category for inquiry
Graphic response from light pen	0.1
Response to complex inquiry in graphic form	2 to 10

Summary for MIL-STD-1472F: Department of Defense Design Criteria Standard - Human Engineering · 1999mil-std-1472f:

Action Definition Timing (sec)
Key response Key depression until positive response (e.g., click) 0.1
Key print Key depression until the appearance of a character 0.2
Page turn End of request until the first few lines are visible 1.0
Page scan End of request until the text begins to scroll 0.5
XY entry From selection of field until visual verification 0.2
Function From selection of command until response 2.0
Pointing From input of point to display point 0.2
Sketching From input of point to display of line 0.2
Local update Change to image using local database (e.g., new menu list from display buffer) 0.5
Host update Change where data is at the host in readily accessible form (e.g., scale change of an existing image) 2.0
File update Image update requires an access to a host file 10.0
Inquiry (simple) From command until display of a commonly used message 2.0
Inquiry (complex) Response message requires seldomly used calculations in graphic form 10.0
Error feedback From entry of input until an error message appears 2.0

Action	Definition	Timing (sec)
Key response	Key depression until positive response (e.g., click)	0.1
Key print	Key depression until the appearance of a character	0.2
Page turn	End of request until the first few lines are visible	1.0
Page scan	End of request until the text begins to scroll	0.5
XY entry	From selection of field until visual verification	0.2
Function	From selection of command until response	2.0
Pointing	From input of point to display point	0.2
Sketching	From input of point to display of line	0.2
Local update	Change to image using local database (e.g., new menu list from display buffer)	0.5
Host update	Change where data is at the host in readily accessible form (e.g., scale change of an existing image)	2.0
File update	Image update requires an access to a host file	10.0
Inquiry (simple)	From command until display of a commonly used message	2.0
Inquiry (complex)	Response message requires seldomly used calculations in graphic form	10.0
Error feedback	From entry of input until an error message appears	2.0

Summary for Guidelines for designing user interface software (ESD-TR-86-278)
By Sidney L Smith, Jane N Mosier · 1986esd-tr-86-278:

Section Topic/Action Timing (sec) Guidance
1.0/4 Fast response 0.2 Maximum time for delays in displayed feedback for normal operation
1.1/5 Fast acknowledgment of entry 0.2 Maximum time to acknowledge the entry of a designated position
1.1/7 Responsive cursor control 0.5 Maximum time for moving the cursor from one position to another
2.7.1/6 Fast response to display request 0.5 to 1.0 System response to a simple request for data display
3.0/28 Appropriate computer response time 0.5 to 1.0 2.0 System response to a control entry System response to simple entries
3.0/19 Control availability 0.2 Maximum time for control delays or lockouts
4.3/11 Appropriate response time for error messages 2.0 to 4.0 Display error message

Section	Topic/Action	Timing (sec)	Guidance
1.0/4	Fast response	0.2	Maximum time for delays in displayed feedback for normal operation
1.1/5	Fast acknowledgment of entry	0.2	Maximum time to acknowledge the entry of a designated position
1.1/7	Responsive cursor control	0.5	Maximum time for moving the cursor from one position to another
2.7.1/6	Fast response to display request	0.5 to 1.0	System response to a simple request for data display
3.0/28	Appropriate computer response time	0.5 to 1.0 2.0	System response to a control entry System response to simple entries
3.0/19	Control availability	0.2	Maximum time for control delays or lockouts
4.3/11	Appropriate response time for error messages	2.0 to 4.0	Display error message

Summary for Department of Defense Technical Architecture Framework for Information Management. Volume 1. Overview. Version 3.0
By Defense information systems agency reston va · 1996tafim1996:

Section Topic/Action Timing (sec) Guidance
6.6.2 Work-in-progress window 5 sec For simple requests that can be processed under this time, provide simple visual feedback via a brief message. If the request response exceeds this time, the application should provide a window to indicate work in progress.
8.3.1.14 Control 5 to 200 ms System response time.
8.3.1.15 Feedback 15 sec If the user waits more than this time, provide a periodic indication of normal operation.

Section	Topic/Action	Timing (sec)	Guidance
6.6.2	Work-in-progress window	5 sec	For simple requests that can be processed under this time, provide simple visual feedback via a brief message. If the request response exceeds this time, the application should provide a window to indicate work in progress.
8.3.1.14	Control	5 to 200 ms	System response time.
8.3.1.15	Feedback	15 sec	If the user waits more than this time, provide a periodic indication of normal operation.

Feedback becomes especially important in case the system has long response times for certain operations. The basic advice regarding response times has been about the same for many years ( Response time in man-computer conversational transactions
By Robert B. Miller · 1968 miller1968; Card et al. 1991):
0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
1.0 second is about the limit for the user’s flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.
10 seconds is about the limit for keeping the user’s attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.