The Doherty Threshold is one of the most practical UX principles for improving engagement: if your interface responds within roughly 400 milliseconds, users stay in flow.
In this guide, you’ll learn what the Doherty Threshold is, why it matters for UX and SEO, and exactly how to apply it in product design.
What is the Doherty Threshold?
The Doherty Threshold (named after researcher John Doherty) states that systems should respond to user input within about 400ms to keep users engaged.
If your app or website feels slower than that, users start feeling friction. And friction usually means lower satisfaction, lower conversion, and higher bounce rates.
Why the Doherty Threshold matters for UX and SEO
Speed affects behavior. Behavior affects SEO.
When users experience delays, they are more likely to:
- leave before completing a task,
- visit fewer pages,
- and return less often.
When your interface responds quickly, users interact more, stay longer, and complete more actions. These engagement patterns support stronger organic performance over time.
How to apply the Doherty Threshold in UX design
1. Provide immediate visual feedback
Some operations will always take longer than 400ms. Your job is to make sure the interface acknowledges the action immediately.
Examples:
- change a button state instantly after click,
- show "Saving..." microcopy right away,
- trigger inline confirmation when possible.
This improves perceived performance, even when actual processing takes longer.
2. Use loading states intentionally
Loading UI reduces uncertainty.
Use:
- skeleton screens for content-heavy pages,
- progress indicators for long-running actions,
- optimistic UI updates for low-risk interactions.
If people can see progress, they are far less likely to abandon.
3. Preload likely next actions
If you can predict the next click, preload required assets or data.
For example, streaming platforms preload a short segment so playback feels instant. The same idea works for dashboards, checkout flows, and content navigation.
4. Remove performance bottlenecks
Perceived speed helps, but real speed still wins.
Prioritize:
- image and media optimization,
- code splitting and script reduction,
- caching and async/background processing,
- minimizing third-party scripts.
Practical examples of the Doherty Threshold
You already see this pattern in products like Instagram, Facebook, and modern SaaS tools:
- likes update immediately,
- comments appear with instant feedback,
- notifications and counters refresh quickly.
These interactions feel simple, but they are carefully designed to stay under (or feel under) the 400ms threshold.
Common mistakes when applying the 400ms rule
- Showing no feedback until the server responds.
- Using spinners everywhere instead of context-aware loading states.
- Prioritizing visual polish over interaction speed.
- Ignoring mobile conditions and slow networks.
FAQ about the Doherty Threshold
Is the Doherty Threshold always exactly 400ms?
Think of 400ms as a practical target, not a hard law. In many contexts, faster is better, but staying around this range helps preserve flow for most interactions.
What is the difference between actual and perceived performance?
Actual performance is measured system speed. Perceived performance is how fast it feels to users. Good UX design improves both.
Is the Doherty Threshold still relevant today?
Yes. User expectations are higher than ever, especially on mobile. Fast feedback is now baseline UX quality.
Related UX principles
If you work with speed and interaction quality, you may also like:
Key takeaway
The Doherty Threshold is not just about milliseconds. It’s about momentum.
If users get immediate response, they stay in flow. If they wait without feedback, they drop off.
Design for fast feedback first. Then optimize everything behind it.