In short
- Definition: How fast and efficiently a system responds and processes work, including speed, throughput, response time and battery life.
- Goal: Give users a fast experience and handle the expected workload smoothly.
- Example S.M.A.R.T. requirement: 95% of page loads under 2 seconds at 1,000 concurrent users, measured in a load test.
1. Definition
As a non-functional requirement, performance describes how fast and efficiently a system responds and processes work: response time, throughput, resource use and, on devices, battery life [1], [2].
Averages hide the slow requests your users remember. Use percentiles.Key takeaway
In ISO/IEC 25010:2023, this is performance efficiency, with sub-characteristics time behavior, resource utilization and capacity. For websites, Google’s Core Web Vitals give user-centered targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 ms or less, and Cumulative Layout Shift of 0.1 or less [3], [4].
Performance must always be stated at a given load, on given hardware or network, and with a percentile, not an average.
2. Goal
The goal is a fast experience for users and smooth handling of the expected workload.
Slow systems lose users and revenue, frustrate employees and often need costly hardware to compensate.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Page or screen response time | Seconds at the 95th percentile | < 2 s at expected load | Load test and real-user monitoring |
| Largest Contentful Paint (web) | Seconds at the 75th percentile | ≤ 2.5 s | Field data (e.g., Chrome UX Report) |
| Interaction to Next Paint (web) | Milliseconds at the 75th percentile | ≤ 200 ms | Field data |
| Throughput | Transactions per second | As required by the business | Load test |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Web application: “95% of page loads shall complete in under 2 seconds with 1,000 concurrent users, measured in a load test before each major release.”
- Public website: “At the 75th percentile of real visits, LCP shall be 2.5 seconds or less and INP 200 ms or less on both mobile and desktop.”
- Batch: “The month-end closing job shall finish within 2 hours for the expected data volume.”
5. Questions to Ask Stakeholders
- Which user actions must be fast, and how fast?
- What is the expected load at peak?
- On which devices and networks do users work?
- Which percentile represents an acceptable experience?
- How will performance be tested before release and monitored after?
- What happens if performance degrades: alert, scale, degrade features?
6. Common Pitfalls
- Using averages. A good average can hide many slow requests. Use the 95th or 99th percentile.
- Testing too late. Architecture problems found in the last week cannot be fixed cheaply.
- Testing on unrealistic environments. Small test databases and fast networks give misleading results.
7. Related NFRs
- Response Time — the most visible performance metric for users.
- Throughput — how much work is processed per unit of time.
- Capacity — the load at which performance targets still hold.
- Efficiency — resources used to achieve performance.
- Scalability — keeping performance as load grows.
8. FAQ
A set of Google metrics for web user experience: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
They show what most users actually experience, including slower cases, unlike averages.
No. Performance is speed at a given load; scalability is keeping that speed as load grows.
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. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| INP | Interaction to Next Paint | Core Web Vital: how quickly a page responds visually after a click, tap or key press. | [4] |
| LCP | Largest Contentful Paint | Core Web Vital: time until the largest visible element of a page is displayed. | [4] |
| 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. | [2] |
| UX | User experience | Everything a person experiences when using a product: ease, emotions, and the whole journey. | [9] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Batch processing | Processing large groups of records together, often at night, rather than one at a time. | [10] |
| Concurrent users | Users active on the system at the same moment. | [11] |
| Database | Organized store of data that software can query and update. | [12] |
| Load test | Test that simulates the expected number of users or requests to check how the system behaves. | [13] |
| Percentile | Value below which a given share of measurements falls; “95th percentile under 300 ms” means 95% of requests are faster than 300 ms. | [14] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [15] |
| Throughput | Amount of work a system completes per unit of time, such as requests per second. | [16] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [17] |
10. Sources and Further Reading
- [1] “Software performance testing.” Wikipedia. https://en.wikipedia.org/wiki/Software_performance_testing (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “Web Vitals.” web.dev. https://web.dev/articles/vitals (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “User experience.” Wikipedia. https://en.wikipedia.org/wiki/User_experience (accessed Nov. 19, 2026).
- [10] “Batch processing.” Wikipedia. https://en.wikipedia.org/wiki/Batch_processing (accessed Nov. 19, 2026).
- [11] “Concurrent computing.” Wikipedia. https://en.wikipedia.org/wiki/Concurrent_computing (accessed Nov. 19, 2026).
- [12] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [13] “Load testing.” Wikipedia. https://en.wikipedia.org/wiki/Load_testing (accessed Nov. 19, 2026).
- [14] “Percentile.” Wikipedia. https://en.wikipedia.org/wiki/Percentile (accessed Nov. 19, 2026).
- [15] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [16] “Network throughput.” Wikipedia. https://en.wikipedia.org/wiki/Network_throughput (accessed Nov. 19, 2026).
- [17] “Database transaction.” Wikipedia. https://en.wikipedia.org/wiki/Database_transaction (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @coryrogers; inline photo by @tyler_clemmensen, both on Unsplash.




