In short
- Definition: The time between a user or system request and the system’s response.
- Goal: Keep interactions fast enough to feel immediate and keep users productive.
- Example S.M.A.R.T. requirement: 95th percentile API response under 300 ms and 99th percentile under 1 second at normal load.
1. Definition
As a non-functional requirement, response time describes the time between a request, by a user or another system, and the system’s response [1], [2], [3].
Users do not experience your average. They experience their own slow request.Key takeaway
For people, research summarized by Nielsen Norman Group gives three classic limits: about 0.1 second feels instantaneous, about 1 second keeps the user’s flow of thought, and about 10 seconds is the limit for keeping attention on the task.
Response time should always be stated with a percentile (for example the 95th or 99th), a load level and a measuring point: in the browser, at the API gateway or inside the service.
2. Goal
The goal is interactions fast enough to feel immediate and to keep users productive.
Slow responses frustrate users, reduce conversions and, between systems, cause timeouts and cascading failures.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| API latency | Milliseconds at the 95th percentile | < 300 ms at normal load | APM or gateway metrics |
| API tail latency | Milliseconds at the 99th percentile | < 1 s | APM or gateway metrics |
| User-perceived response | Seconds for key actions | < 1 s | Real-user monitoring |
| Long operations | Feedback provided | Progress indicator if > 10 s | UX review |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- API: “At normal load, the 95th percentile of API responses shall be under 300 ms and the 99th percentile under 1 second, measured at the API gateway.”
- Interactive UI: “Search results shall appear within 1 second for 95% of queries.”
- Long tasks: “Any operation expected to take more than 10 seconds shall show a progress indicator and allow the user to cancel.”
5. Questions to Ask Stakeholders
- Which actions must feel instant, and which can take longer?
- At what load must response times be met [4]?
- Where should response time be measured?
- Which percentile reflects an acceptable experience?
- What timeouts do calling systems use?
- What should the user see during long operations?
6. Common Pitfalls
- Measuring only on the server. Network and browser time matter to users. Use real-user monitoring.
- Using the average. It hides the slow tail. Use percentiles.
- Ignoring dependencies. A slow downstream call sets your response time.
7. Related NFRs
- Performance — response time is the most visible part of performance.
- Throughput — high throughput with slow responses still frustrates users.
- Capacity — response times hold only up to a certain load.
- Usability — fast feedback improves the user experience.
8. FAQ
Classic human-factors limits for feeling instant, keeping flow of thought and keeping attention, as summarized by Nielsen Norman Group.
The response time of the slowest requests, usually the 99th percentile or above.
Yes. Latency SLOs are common, such as 99% of requests under a given threshold over 30 days.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [6] |
| APM | Application performance monitoring | Tools that measure an application’s speed and errors in production. | [7] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [3] |
| SLO | Service level objective | Internal, measurable target for a service, such as “99.9% of requests succeed over 30 days”. | [9] |
| UI | User interface | The screens, buttons and controls through which a person uses a system. | [10] |
| UX | User experience | Everything a person experiences when using a product: ease, emotions, and the whole journey. | [11] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Latency | Delay between a request and the start of the response. | [12] |
| Percentile | Value below which a given share of measurements falls; “95th percentile under 300 ms” means 95% of requests are faster than 300 ms. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
| Throughput | Amount of work a system completes per unit of time, such as requests per second. | [15] |
10. Sources and Further Reading
- [1] “Measure performance with the RAIL model.” web.dev. https://web.dev/articles/rail (accessed Nov. 18, 2026).
- [2] “Response time (technology).” Wikipedia. https://en.wikipedia.org/wiki/Response_time_(technology) (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “Response Times: The 3 Important Limits.” Nielsen Norman Group. https://www.nngroup.com/articles/response-times-3-important-limits/ (accessed Nov. 18, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [7] “Application performance management.” Wikipedia. https://en.wikipedia.org/wiki/Application_performance_management (accessed Nov. 19, 2026).
- [8] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [9] “Service-level objective.” Wikipedia. https://en.wikipedia.org/wiki/Service-level_objective (accessed Nov. 19, 2026).
- [10] “User interface.” Wikipedia. https://en.wikipedia.org/wiki/User_interface (accessed Nov. 19, 2026).
- [11] “User experience.” Wikipedia. https://en.wikipedia.org/wiki/User_experience (accessed Nov. 19, 2026).
- [12] “Latency (engineering).” Wikipedia. https://en.wikipedia.org/wiki/Latency_(engineering) (accessed Nov. 19, 2026).
- [13] “Percentile.” Wikipedia. https://en.wikipedia.org/wiki/Percentile (accessed Nov. 19, 2026).
- [14] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [15] “Network throughput.” Wikipedia. https://en.wikipedia.org/wiki/Network_throughput (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @wwarby; inline photo by @andriklangfield, both on Unsplash.




