Usability metrics: 12 key metrics to track

Key Takeaways

• Track task completion and error rate together to spot real friction: A high task completion rate can still hide a usability problem if it takes people far longer than expected to get there.
• SUS, CSAT, and NPS each measure something different: SUS (system usability scale) scores overall usability, CSAT (customer satisfaction score) captures satisfaction with a specific moment, and NPS (net promoter score) predicts loyalty and word-of-mouth growth.
• Segment every metric by user type and device: A task completion rate of 90% for returning users but 40% for newcomers, or 88% on desktop versus 64% on mobile, reveals exactly where to focus fixes.
• Set a baseline before you change anything: Without measuring first, you can't prove whether a redesign actually improved completion rates, error rates, or satisfaction scores.

When you're building a product, confidence alone doesn't tell you if it's actually easy to use. That's where usability metrics come in.

Usability metrics are quantifiable measurements that show how well users can accomplish their goals with your product, website, or app. They answer specific questions: Do people understand what to do? Can they find what they're looking for? Do they get frustrated and leave?

Tracking the right metrics gives you concrete data instead of guesses. As the usability testing tools market continues to expand—growing at 21.3% annually and projected to reach $10.41 billion by 2034—more teams are investing in understanding how users interact with what they build.

This guide walks you through 12 essential usability metrics. Each answers a different question about user experience, painting a clear picture of what's working and what needs attention.

Task completion rate

Task completion rate measures how many users successfully finish what you asked them to do.

If you run a usability test asking 10 people to sign up for your newsletter and only six complete it, your task completion rate is 60%. A high task completion rate (above 80%) typically signals that your interface is intuitive. A low rate (below 70%) suggests friction: unclear instructions, confusing navigation, or technical problems.

This metric is often the first place to look when something feels wrong. Unlike subjective feedback, task completion provides binary clarity. Either someone finished or they didn't. When you implement a redesign, and your task completion rate jumps from 62% to 78%, you have objective proof that your changes worked.

Track this metric separately for different user segments. A task might be easy for experienced users but hard for newcomers. If task completion is 90% for returning users but only 40% for first-time users, your learning curve is too steep.

The insight becomes more valuable when you combine completion rate with time on task. A task with 85% completion but an average time of 12 minutes might still represent a significant problem, even though most people eventually succeed. The struggle matters.

Consider device type as well. Your task completion rate on desktop might be 88%, but on mobile it could be 64%, a massive gap suggesting your mobile interface needs serious attention.

Time on task

Time on task measures how long it takes users to complete a specific action. If your goal is for people to upload a document, and it takes most people two minutes, you've found an efficiency problem.

Faster isn't always better. Sometimes a thoughtful process takes longer. But when time on task is much longer than expected, it often points to specific friction:

• Confusing step sequences that force users to backtrack
• Hidden buttons or options that users can't find easily 
• Unclear labeling that creates uncertainty 
• Too many choices or clicks required

In many contexts, time spent struggling with your interface directly correlates to frustration and abandonment. A checkout process that takes eight minutes instead of three will see higher cart abandonment. Each additional minute represents a drop-off opportunity where users give up and leave.

Compare time on task across different groups. New users often take longer than returning ones, which is normal. But if the gap is huge, your interface might not be learning-friendly. Track both the median and outliers. If most users complete a task in three minutes but a few take 45 minutes, those outliers represent either power users with different needs or people who got seriously stuck.

Document the specific steps where time extends. If users spend 90 seconds on one screen but only 15 seconds on others, that screen deserves investigation. Sometimes, a single confusing element adds minutes of time for every user. Fixing that one element compounds across your entire user base.

Error rate

Error rate tracks how many times users make mistakes while trying to complete a task: wrong button clicks, incorrectly filled fields, or unintended option choices. It's critical because errors extend time on task, increase frustration, and sometimes lead to abandonment.

A high error rate often reveals:

• Unclear instructions or labels
• Small targets that are easy to miss, especially on mobile
• Confusing visual hierarchy
• Similar-looking options that get confused

Track both frequency and severity. A user who accidentally clicks "Delete" and can't undo it experiences catastrophic failure. A user who selects the wrong category and realizes it after two clicks experiences a minor annoyance.

Pay attention to which errors happen most. If 8 out of 10 users click the same wrong button, that's your design problem. When the same error occurs repeatedly across users, it's a strong signal that your design guidance, visual hierarchy, or labeling needs work.

Compare error rates before and after making design changes. Removing one confusing option might cut errors in half. Making buttons larger could reduce accidental clicks on mobile devices significantly. Changing labeling from jargon to plain language could improve accuracy dramatically.

System Usability Scale (SUS) score

The System Usability Scale is a 10-question survey measuring how usable people find a product overall. Users rate statements like "I found this system easy to use" on a scale from "strongly disagree" to "strongly agree."

The SUS produces a score from 0 to 100. Scores above 80 are excellent. Scores between 50 and 80 suggest room for improvement. Below 50 indicates serious usability problems.

What makes SUS useful is consistency and industry recognition. You can compare results directly across products, teams, or time periods. Run SUS surveys after major releases, before and after redesigns, or quarterly. Track how your score changes over time. Even small improvements signal that your changes are making a real difference.

The 10-question format is intentionally short so response rates stay high. Don't modify the questions. The validated questions are what make the score meaningful and comparable. You can compare your SUS score against industry benchmarks and your own historical performance.

When you run SUS surveys, supplement the quantitative scores with open-ended questions about what's working and what isn't. A SUS of 62 tells you there's room for improvement. User comments explaining that "the navigation is confusing" or "buttons look like links" point toward specific fixes.

Customer Satisfaction (CSAT) score

Customer Satisfaction scores measure how happy users are with your product or a specific feature. It's usually one simple question: "How satisfied are you with this experience?" answered on a numeric scale, often 1 (very dissatisfied) to 5 (very satisfied).

The average CSAT across industries is 77%, with scores above 80 considered excellent.

CSAT is quick to measure and gives you a pulse on user sentiment in real time. Deploy it after key interactions—a purchase, customer support chat, using a new feature, or completing onboarding—to capture feedback when experiences are fresh.

Use CSAT to identify which parts of your experience need attention. A low score on one feature compared to others tells you where to focus resources. If your overall product CSAT is 75 but your payment feature CSAT is 42, you've found your biggest problem.

Track CSAT over time and by segment. If CSAT among long-time customers is 82 but CSAT among new users is 58, your onboarding experience needs work. If CSAT drops after a feature launch, that feature created problems.

Combine CSAT with follow-up questions to understand the "why" behind satisfaction scores. Users rating satisfaction as 3 out of 5 should be asked what would make it a 4 or 5. Their responses often point directly toward actionable improvements.

Net Promoter Score (NPS)

Net Promoter Score measures loyalty by asking: "How likely are you to recommend this product to others?" Users answer on a scale of 0 to 10.

Scores 9-10 are "promoters": loyal users who actively recommend you. Scores 7-8 are "passives": satisfied but not loyal. Scores 0-6 are "detractors": unhappy users. Your NPS is calculated by subtracting the percentage of detractors from the percentage of promoters, ranging from -100 to 100.

A positive NPS is good. An NPS above 50 is excellent and indicates a strong competitive advantage.

Ask detractors what would make them more likely to recommend you; their frustrations point to improvement opportunities. Ask promoters what they love most; double down on those strengths. NPS correlates strongly with business growth and predicts whether users will stay, spend more, and grow your user base through word-of-mouth.

Segment your NPS by user characteristics. Long-time users might have an NPS of 65 while new users have an NPS of 15. Different user personas might show dramatically different loyalty levels. Understanding these segments reveals whether specific improvements move the needle on loyalty for particular groups.

Bounce rate

Bounce rate is the percentage of users who leave your product, page, or feature without taking the desired action. If 100 people land on your pricing page and 35 leave without action, your bounce rate is 35%.

High bounce rates suggest:

• The page doesn't match expectations based on how users arrived
• Messaging or visual design feels off-target
• The call to action is unclear or buried
• The page loads slowly

Bounce rate varies by page type, so interpretation requires nuance. A high bounce rate on a landing page (40%+) is concerning. A high bounce rate on an educational article might be normal. People read, learn, and leave.

Compare bounce rates across sources: organic search, paid ads, email, direct traffic, and social media. If one source has an unusually high bounce rate compared to others, investigate. It could reveal a messaging mismatch or technical problem. Segment bounce rates by device type as well.

Look at bounce rate in combination with dwell time. A high bounce rate with long dwell time suggests people are reading but not converting. A high bounce rate with short dwell time suggests immediate rejection, meaning the page doesn't meet expectations.

Conversion rate

Conversion rate measures the percentage of users who complete the desired action: signing up, making a purchase, downloading, submitting a form, or upgrading. If 100 users visit your signup page and eight complete the signup, your conversion rate is eight percent.

Small improvements compound quickly. A jump from two to three percent on a high-traffic page means 50% more conversions with the same traffic, translating directly to more customers and revenue.

Track conversion rates at each step of your funnel, not just the final outcome. If people consistently abandon at a specific stage, that's your bottleneck. Identifying the exact leakage point lets you invest resources where they matter most.

Test variations systematically. Change one variable at a time—button color, form length, copy, layout—and measure whether conversion rate improves. Even tiny changes sometimes have surprisingly large effects.

Compare conversion rates for different user segments and entry points. New users might convert at half the rate of returning users. Understanding these patterns helps you identify where friction exists.

User satisfaction with specific features

Beyond overall satisfaction, measure how satisfied users are with individual features. This tells you which parts work well and which frustrate people. General satisfaction scores can mask problems in specific areas. Your overall CSAT might be 80 while your search function generates consistent frustration.

Ask: "How satisfied are you with the search function?" immediately after someone uses it. Timing matters, and asking later produces less accurate responses.

Feature-level satisfaction data guides your roadmap. If 60% of users feel unsatisfied with search but 90% love filtering, you know where to invest. Create a feature satisfaction matrix showing which features your users depend on most and how satisfied they are with each. A feature that everyone uses but nobody loves represents a high-impact improvement opportunity.

Feature-level satisfaction data also helps you understand whether problems are system-wide or localized. If every feature has low satisfaction scores, your problem is fundamental. If only specific features have low satisfaction, your problems are more surgical and fixable.

Perceived ease of use

Perceived ease of use is how simple users think your product is, separate from whether it actually is. You measure it with questions like "This system was easy to use" or "I felt in control while using this product."

People's perception shapes their behavior powerfully. If users think something is hard, they'll avoid it, even if it would save them time. If they think something is easy, they're more likely to try it and recommend it.

Measure both actual performance (time on task, error rate, task completion) and perceived ease of use. If they don't match, dig into why. Maybe users need better guidance, clearer labeling, or visual cues that make the design feel simpler. Track perception changes as users gain experience to see whether the learning curve is manageable.

Click-through rate (CTR)

Click-through rate measures the percentage of users who see something and actually click on it. If 500 users see a "Learn More" button and 50 click it, your CTR is 10%.

A low CTR suggests:

• The button isn't visually prominent enough
• The label doesn't match user expectations
• Placement is hard to see or is outside the natural reading flow
• Users aren't motivated to click

Track CTR separately by section or design variation. If one button gets clicked 15% of the time and an identical button elsewhere gets clicked 3%, something about context or placement matters.

CTR is useful for testing variations rapidly. Change button color, label, or position and measure whether CTR improves. Tests consistently show that more specific, action-oriented button labels ("Learn how our filters work" instead of "Learn More") drive higher CTR.

Compare CTR across devices and browsers. A button that performs well on desktop might underperform on mobile because the touch target is too small or the label gets truncated.

Abandonment rate

Abandonment rate tracks what percentage of users start a process but don't finish. In e-commerce, people add items to carts but never check out. In onboarding, people start signup but quit halfway. High abandonment represents lost opportunity.

High abandonment at any step tells you there's friction. If 70% abandon during checkout, your payment process has problems: too many fields, unclear errors, unwanted payment methods, or security concerns.

Identify where abandonment happens most. Each step should have progressively lower abandonment simply because some users naturally drop off. When one step shows significant drop-off compared to others, that's your redesign target.

Combine abandonment rate with user feedback to understand why people quit. Create a visual map of your funnel showing where users drop off most dramatically. A 20% drop from step one to step two is concerning. A five percent drop from step eight to nine is normal. These visualizations make it immediately obvious where your biggest problems exist.

Analyze what drives abandonment by adding exit surveys. Ask users who abandon: "What made you decide to leave?" Their responses often reveal problems your analytics alone wouldn't surface.

Accessibility compliance score

Accessibility compliance measures how well your product meets standards for users with different abilities. This includes people using screen readers, keyboards only, high-contrast modes, magnification, or other assistive tools.

This is both a moral obligation and a business consideration. It expands who can use your product and reflects changing legal expectations. Many regions now require websites and apps to meet Web Content Accessibility Guidelines (WCAG) standards.

Track compliance against WCAG 2.1 Level AA standards. Audit your product regularly using both automated tools and manual testing with real assistive technology users. Automated tools catch maybe 30% of issues; human testing reveals the rest.

Score your compliance across categories: color contrast ratios, keyboard navigation, alt text quality and presence, form labels and instructions, and focus management. Accessibility improvements often benefit everyone. Captions help people in loud environments, keyboard navigation helps power users, and clear labeling helps people scan quickly.

Test with real users who rely on assistive technologies. What passes automated checks might still fail real-world usage.

Tracking usability metrics pays off

The usability testing tools market is growing because companies realize that guessing about user experience is expensive. One case study found that a usability investment of $68,000 generated $6.8 million in benefit within the first year on a system used by over 100,000 people, signaling a 100x return.

These 12 metrics give you a framework for understanding what's working and what isn't. You don't need to measure all of them at once. Start with the ones most relevant to your current priorities: task completion and error rate if redesigning a workflow, CSAT and NPS if tracking sentiment, bounce rate and CTR if optimizing marketing pages.

Set baselines first. Measure today so you know whether future changes actually improve things. Then, measure again after the changes and compare. Without baselines, you can't prove improvement.

The goal is understanding your users well enough to make thoughtful decisions, not chasing perfect scores on every metric. Usability metrics turn observation into action, transforming user experience from gut feel into data-driven discipline. Your competitors are measuring. Your users will appreciate the results. Start measuring today.