Average response time hides what users actually experience: an average of one second can mean every request took one second, or half took almost nothing and half took two. Apdex, the Application Performance Index, fixes this by sorting requests into satisfied, tolerating, and frustrated buckets against a threshold you choose, then scoring them as satisfied plus half of tolerating, divided by the total. The result is one number between zero and one that tracks user perception instead of server averages. This tool computes Apdex from your counts and labels the result, so you can set a performance target the whole team understands, compare releases on user experience rather than averages, and spot the slow-request tail that averages conceal.
Quick Answer: Enter 80 satisfied, 10 tolerating, 10 frustrated and the tool returns Apdex 0.850 (Good).
Free Online Tool
Apdex Score Calculator
Compute an Apdex score from satisfied, tolerating, and frustrated request counts — one number for user-perceived performance.
Apdex = (satisfied + tolerating / 2) / total. Scores above 0.94 are generally considered excellent.
How to Use the Apdex Score Calculator
- Enter your input in the tool above — for example, 80 satisfied, 10 tolerating, 10 frustrated.
- Choose any options the tool offers, such as the conversion direction or the settings that fit your case.
- Click the main button to run the tool and read the result it displays.
- Check the result against what you expected, then adjust the input and run it again if needed.
- Copy the output into your own document, code, or configuration wherever you need it.
Worked Example
Try it with 80 satisfied, 10 tolerating, 10 frustrated: the tool returns Apdex 0.850 (Good). That example is a good first test whenever you use the tool, because it confirms you entered the input in the expected format before you trust it with your real values. This tool is built for setting performance targets and comparing releases on user experience, and the worked example shows the shape of a correct result so you can recognize a wrong one at a glance.
Key Features
- Runs entirely in your browser — nothing you type is uploaded anywhere.
- Built for setting performance targets and comparing releases on user experience, with the result shown immediately and in full.
- No account, no sign-up, and no software to install.
- Clear error messages when an input is incomplete or in the wrong format.
- Free to use as often as you like, for study, work, or checking homework.
Best Practices and Tips
- Start with the worked example in the guide, then substitute your own values.
- Double-check units and formats before trusting a result — most tool errors are input errors.
- Keep a note of the exact inputs that produced a result you rely on, so you can reproduce it.
- For anything important, cross-check with a second method or a known test value.
- Bookmark the tool if you use it regularly, so the same workflow is always one click away.
Common Mistakes to Avoid
- Choosing a threshold that flatters the score instead of reflecting user patience.
- Reporting Apdex without the threshold, which makes scores from different systems incomparable.
- Copying a result without checking it against a known example first.
- Assuming the tool knows your context — it only sees the values you enter.
When This Tool Helps — and When It Doesn’t
This tool helps most when you need a fast, checkable answer for setting performance targets and comparing releases on user experience and you can verify the result against a known example. It does not replace professional judgment: for decisions with real consequences, treat the output as one input among several, verify it independently, and remember that the tool can only work with exactly what you enter. Used that way — quick check, verified result, human decision — it saves time without creating false confidence.
Frequently Asked Questions
What threshold should I use for the buckets?
It depends on the interaction: a common starting point is 0.5 seconds for satisfied in web applications, with tolerating up to four times that. The threshold must reflect what your users tolerate, not what makes the score look good.
What do the rating bands mean?
Above 0.94 is generally excellent, 0.85 to 0.94 good, 0.70 to 0.85 fair, 0.50 to 0.70 poor, and below 0.50 unacceptable. These are conventions, not laws — track your own trend over time.
Why is Apdex better than average response time?
Because users experience individual requests, not averages. Apdex counts how many requests actually felt fast, so a small number of terrible requests cannot hide inside a respectable average.