Nielsen's 10 Usability Heuristics: A Website Guide

A visitor who can't tell what happened after clicking a button, can't find a way back or gets an "Error" message with no explanation won't write to you to complain. They will simply close the tab and go to a competitor. Most of these problems don't need expensive research to uncover: checking your interface against ten simple rules is often enough.

Those rules were put together by interface researchers Jakob Nielsen and Rolf Molich in 1990, based on hands-on experience from many projects. In 1994 Nielsen refined them into the version known today as "Nielsen's 10 usability heuristics". More than three decades later, in a world of mobile apps, e-commerce and AI interfaces, they are still the standard starting point for any usability review.

In this guide we explain:

• what a heuristic is and why it is useful for business owners, not just designers;
• what each of the ten principles means, with examples from well-known websites and apps;
• how to run a heuristic evaluation of your own website, step by step;
• which common mistakes are worth fixing first;
• what to keep in mind on multilingual and international websites.

What Nielsen's heuristics are and why they still matter

A heuristic is a rule of thumb: not a binding law or a precise formula, but a general principle that helps you make a good decision quickly. Nielsen's heuristics don't tell you what colour a button should be or where the menu belongs. They describe how a good interface behaves towards the person using it.

You can break them, and some successful products do so deliberately. But every violation adds cognitive load for the user: one more thing to remember, guess or double-check. On a company website that can cost you an enquiry that never gets sent. In an online shop, it costs you an abandoned cart.

Why have the principles lasted so long? Because they don't depend on technology. They are based on how people think, remember and make mistakes, and that has barely changed since 1990. The same rules apply to a Webflow website, a banking app, a car park payment machine and an AI chatbot.

There is a practical advantage too: a heuristic evaluation is cheap and fast. You don't need to recruit participants or book a usability lab. One or two experts walk through the interface against the list of principles and catch a large share of the obvious problems, before you ever test with real users. It doesn't replace user research, but it filters out the clear mistakes so that research can focus on the questions that really matter.

Principles 1–3: visibility, familiar language and control

The first three principles deal with a basic question: does the user understand what is going on, does the interface speak their language, and can they get out of a situation they didn't want to be in?

1. Visibility of system status

The system should always show users what is happening, within a reasonable time and in a clear way. Ordered food delivery in an app? The "Order received" screen, followed by real-time tracking of the kitchen and the courier, is exactly this principle in action. You know everything is fine and you don't need to call to check.

On websites, this principle breaks most often in forms. The user clicks "Submit" and nothing happens: no loading animation, no confirmation, and sometimes the form simply clears itself. The result is a double click, a duplicate enquiry or a user who gives up. A few simple things worth checking:

• a submit button that shows a loading state and stays disabled until a response arrives;
• a clear thank-you message after the form is sent, explaining what happens next and when you will get back to them;
• a visual highlight for the active page in the navigation menu;
• a cart counter that updates as soon as an item is added;
• a progress bar in any form or checkout that has several steps.

2. Match between the system and the real world

The interface should speak the user's language, not the language of developers or of an internal department. A magnifying glass stands for search, a cart for buying, a bin for deleting. These are metaphors from the physical world that everyone understands without explanation.

The same goes for copy. "Error 0x80070005" means nothing to a customer, and "SKU" means nothing to most shoppers. It also helps to order information the way users think about it: on a clinic's website, people look for "how do I book an appointment" and "how much does it cost" first, and only later for the history of the practice.

Designers used to apply this principle through skeuomorphism: a calendar that looked like a paper calendar and a calculator that looked like a real one. That style has all but disappeared, but the idea remains: explain something new through something the user already knows.

3. User control and freedom

People make mistakes. They click the wrong link, delete an item by accident or start a process they didn't mean to. A good interface offers a clearly marked "emergency exit": a cancel button, a way to go back and an Undo action.

Good examples are easy to find. Gmail lets you undo sending an email for a few seconds. Telegram lets you restore a deleted chat for a few seconds after you delete it. On an iPhone you can revert an edited photo to the original even after saving. The opposite is familiar from delivery apps: one careless swipe removes a product from the cart, and there is no one-tap way to bring it back.

On a website this means: pop-ups that are easy to close (including with the Esc key), a cart where you can change quantities and restore a removed item, and a long form that doesn't wipe your answers when you go back a step.

Principles 4–5: consistency and error prevention

4. Consistency and standards

The same action should look and work the same way everywhere in the system. If the primary button is purple on the homepage, it should be purple on the contact page as well. If the logo in the header takes you to the homepage on one page, it should do so on every page.

The principle has two sides. Internal consistency means keeping the same rules within your own product. External consistency means respecting conventions users have already learned on other websites: links look like links, a hamburger icon opens a menu, and destructive actions, such as deleting an account or signing out of all devices, are shown in red almost everywhere.

A common problem is buttons that are all equally "important". When two buttons with the same visual weight sit side by side and their labels are similar, the user stops and starts reading every word. A clear hierarchy, with one primary button and quieter secondary ones, solves this. You can read more about it in our guide to website button design.

The tool that keeps things consistent over time is a design system or UI kit: an agreed set of colours, typography, buttons and form fields. In Webflow this takes the form of shared classes and components; in Figma, a component library.

5. Error prevention

A good error message is better than a bad one, but it is better still if the error never happens. A good interface prevents problems before they occur: it asks for confirmation before an irreversible action, blocks invalid input and offers sensible defaults.

Practical examples for a website:

• in a phone field, show a numeric keypad on mobile (using type="tel" or inputmode="numeric"), and in an email field, a keyboard with the @ sign;
• for dates, use a date picker rather than a free-text field, and block dates in the past;
• keep the "Submit" button inactive until the required fields are filled in;
• before deleting something, cancelling a subscription or making a payment, show a confirmation screen with a summary of the action;
• offer autocomplete in address fields so users don't misspell a street name.

How serious a mistake is depends on the context. An email accidentally sent to your whole mailing list is embarrassing, but the interface of a medical device or a payment system cannot afford that kind of slip. The higher the cost of an error, the stronger the safeguards need to be.

Principles 6–7: recognition rather than recall, flexibility and efficiency

6. Recognition rather than recall

People's short-term memory is limited. A good interface doesn't make users carry information from one page to the next; it shows that information exactly where it is needed. Recognising an option in a list is far easier than pulling it out of memory.

Imagine an online shop that doesn't show the delivery date on the product page, or a banking app that doesn't show your balance before you confirm a transfer. The user has to open another screen, remember a number and come back. Large retailers such as Amazon show an estimated delivery date on the product page and in the cart, which saves an unnecessary question at the moment of decision.

On websites this comes down to a few simple habits: breadcrumbs that show where you are, a "recently viewed" list, form fields that remember what was typed earlier, search with suggestions, and field labels that don't disappear as soon as you start typing. A placeholder used instead of a label is a classic violation: once you have typed something, it is no longer clear what the field was asking for.

7. Flexibility and efficiency of use

A new user and an experienced user need different things. The newcomer needs a clear, step-by-step path; the regular wants to get to the goal as quickly as possible. A good interface serves both: the standard route is open to everyone, with shortcuts alongside for people who know the system.

The classic example is keyboard shortcuts. You can copy via the menu, but anyone who does it dozens of times a day uses Ctrl+C. On websites and in apps it looks like this: ready-made quick replies in a support chat, a "Reorder" button in order history, sign-in with Google or Apple instead of a long registration form, saved delivery and payment details for the next purchase, and filters that stay applied when you return to a product list.

It's important not to lock users into a single path. A website that demands full registration before anyone can even see prices, or that doesn't allow guest checkout, loses some of the customers who just wanted to try. Let people continue as a guest, and offer to create an account only after the purchase.

Principles 8–10: minimalism, error recovery and help

8. Aesthetic and minimalist design

Every extra piece of information on the screen competes for attention with the information that really matters. Banners, unnecessary icons, five call-to-action buttons and three pop-ups at once don't make a website richer. They make it harder for users to understand what they are supposed to do next.

Minimalism here doesn't mean "white and empty". It means every element has to earn its place. A product with few features isn't a bad product: a timer app with four buttons is usually better than a tool that tries to do everything. A customer dashboard crammed with promotions, a loyalty club, points, loan offers and recommendations on one screen is what happens when every department in a company wants space on the page.

To test this principle on your own website, ask of every block on the page: what would happen if we removed it? If the answer is "nothing", you can probably remove it. The Gestalt principles of proximity, similarity and white space help organise what remains; we cover them in our guide to Gestalt principles in web design.

9. Help users recognise, diagnose and recover from errors

When an error does happen, the message should use plain language, explain exactly what went wrong and suggest a fix. "Error" at the top of a form, after the page has jumped back up and wiped everything the user typed, is the exact opposite.

A good example: when you try to share a file via AirDrop with Bluetooth switched off, the iPhone doesn't just say "Action failed"; it offers to turn Bluetooth on. That is the structure of a good message: what happened, why, and what to do about it.

Rules for error messages in forms:

• show the error next to the problem field, not only at the top of the page;
• explain the requirement: "Please enter your phone number with the country code", not "Invalid input";
• never delete what the user has already typed;
• use colour plus an icon or text, so users who can't distinguish colours still understand;
• don't blame the user and don't show technical codes.

A 404 page is a special case of the same principle: instead of a dead end, it should help the user find their way again.

10. Help and documentation

Even the clearest interface will have moments when the user needs extra help. Ideally the system is understandable without explanations, but when an explanation is needed, it should be easy to find, short, focused on the task and written in human language.

On websites this can be an FAQ page, a short tooltip next to a confusing field, a WhatsApp button or a support chat available from every page, or a searchable help centre. What doesn't work is instructions that don't answer the real question. If an AI image generator refuses a request and only says "This request violates our policies", without explaining which policies or what to change, the user is left guessing. Good help tells people what to do now.

How to run a heuristic evaluation of your website, step by step

A heuristic evaluation can be done in a day or two, and it produces a practical list of fixes. This is the process we recommend.

Step 1: Define the key tasks

Don't review "the whole website" in general terms. Pick three to five tasks that matter most to the business: submitting a contact form, booking an appointment, buying a product, finding a price or finding your address. The evaluation follows each of these journeys from start to finish.

Step 2: Choose your evaluators

A single evaluator will miss some of the problems. Nielsen recommended three to five evaluators working independently, because each one notices different things. In a small business, you can pair a designer or UX specialist with someone on the team who wasn't involved in building the website.

Step 3: Walk through each journey against the ten principles

Each evaluator goes through the tasks alone, on desktop and on mobile, and records every problem: where it is, which principle it violates and what exactly happens. It helps to attach a screenshot to each finding. A simple table in Google Sheets or Notion is perfectly enough.

Step 4: Rate the severity of each problem

Once all evaluators have finished, merge the lists and rate each problem. Nielsen proposed a scale from 0 to 4, from "not really a usability problem" to "usability catastrophe that must be fixed before launch". The rating takes three things into account: how many users run into the problem, how hard it is to overcome and whether it keeps coming back.

Step 5: Prioritise and fix

Start with severe problems in the most important journeys, especially the ones that are easy to fix. A submit button with no loading state or an unclear error message in a form is usually an hour's work with a direct effect on the number of enquiries. After the fixes, check the outcome in your metrics: form conversion rate, cart abandonment and time to complete a task in Google Analytics 4.

Common mistakes when applying the heuristics

The heuristics are simple to state, but easy to misuse. These are the mistakes we see most often:

• Treating them as a visual design checklist. The principles describe how an interface behaves, not its style. A website can look beautiful and still break half of them.
• Testing on desktop only. On most websites today, the majority of visitors arrive on a phone. A button that is too small, a menu that closes by accident or the wrong keyboard for a field are problems that only show up on mobile.
• Replacing user research with a heuristic evaluation. The evaluation finds known problems, but it won't tell you whether your message is clear or your price is convincing. It complements testing with real users and the data from your analytics.
• Reviewing a website you built yourself. Whoever built the interface already knows how it works and doesn't see the obstacles. A fresh pair of eyes is better.
• Trying to fix everything at once. Without a severity rating, the team wastes time on small details while the main form still doesn't work properly.
• Confusing minimalism with hiding things. Hiding important information, such as the price or delivery terms, to make a page look clean violates principle 6. Worse, it edges towards dark patterns, which are designed to mislead users.

Nielsen's heuristics on multilingual and international websites

The principles are universal, but applying them on a website that serves several countries or languages brings a few nuances worth knowing.

Language switching. Consistency and user control include language. The language switcher should sit in the same place on every page, show each language in its own name ("Português", not "Portuguese"), and keep the user on the equivalent page rather than sending them back to the homepage. A visitor who lands on the wrong language version and can't find the way out is a textbook violation of principle 3.

Local formats in forms. Error prevention starts with knowing what people will actually type. Phone numbers come in different lengths and with or without a country code, so a field that only accepts one national format creates pointless errors. Most of Europe writes dates as day/month/year, and many countries use a comma as the decimal separator. Fields that accept these variations, or a country selector that sets the format automatically, stop errors before they happen.

Right-to-left languages. If your website includes an Arabic or another right-to-left version, consistency includes direction. "Next" arrows, carousels and progress indicators should be mirrored, while phone numbers and product codes must still read correctly inside right-to-left text.

Messaging apps as a help channel. In many markets customers would rather ask a quick question in WhatsApp or another messenger than fill in a form. A visible messaging button is a direct application of principle 10, and of principle 7 as well, because it shortens the path to an answer.

Accessibility. In the EU, the European Accessibility Act has applied since June 2025 to many digital products and services, including online shops and other e-commerce, and the related European standard EN 301 549 builds on WCAG. Many of Nielsen's principles, such as clear error messages, consistency and visible field labels, overlap with accessibility requirements. Whether and how the rules apply to your business is a question for a legal professional; this is not legal advice. We cover the practical side in our guide to website accessibility.

How RJL Studio improves your website's usability

At RJL Studio we review your website against the ten principles and against real data from your analytics, rate the problems by severity and fix first what directly affects enquiries and sales: forms, call-to-action buttons, mobile navigation and error messages. When needed, we also redesign entire journeys, from wireframes to a consistent design system in Figma and Webflow.

Want to know what is stopping your customers from getting in touch? Read about our UX/UI design services and Webflow website development, or contact us and we will get back to you.

Frequently asked questions

What is the difference between a heuristic evaluation and usability testing with users?

In a heuristic evaluation, experts review the interface against a list of principles and find known problems. In usability testing, real users try to complete tasks while the team watches where they get stuck. A heuristic evaluation is faster and cheaper, while testing with users reveals problems that experts don't anticipate. Combining the two gives you the full picture.

Can I run a heuristic evaluation myself, without a UX designer?

You can start on your own: go through the most important tasks on your website on a phone and ask the ten questions from this guide about every screen. That will catch the obvious problems. A UX specialist will find more, rate the severity correctly and suggest fixes that don't break other parts of the website.

Are Nielsen's heuristics still relevant in 2026?

Yes. The principles are based on how people think and remember, not on any particular technology. They apply equally to websites, apps, voice interfaces and AI chatbots. What changes are the examples and the tools used to put them into practice.

How long does a heuristic evaluation of a business website take?

For a company website or a landing page, a day or two is usually enough, including a report with screenshots and severity ratings. An online shop or a system with many user journeys takes longer, depending on how many tasks are reviewed.

Which principle should I start with?

On most business websites, the quickest wins are in forms: visibility of system status (what happens after clicking "Submit"), error prevention (the right fields and keyboards) and clear error messages. These three fixes have a direct effect on the number of enquiries you receive.