UX/UI: Everything You Need to Know

When a visitor leaves your website without taking the action you wanted, it affects your business more than you think. The visitor did not buy, did not call, and did not fill out your form. That is the first loss. The second loss is quieter. A bad experience sticks with the visitor, and it shapes what they think of your company. They remember the name, and they skip it the next time they see it. A bad user experience can hurt your company’s reputation, and a hurt reputation is harder to fix than a confusing page.

A visitor finds your website in a search result and taps or clicks the link. The page loads. The visitor stays for a few seconds, looks around, and cannot find what they came for. The headline does not say it. The menu does not show it. The page looks busy, and nothing tells the visitor where to go next. The visitor leaves. That visitor was a customer you will never meet. You paid for the click, or you earned the ranking, and the visit still ended with nothing. They went back to the search results, and the next business on the list got the sale. That is what this post is about. UX and UI decide whether a visitor stays long enough to take the action you wanted, and this guide explains both in plain words.

What UX and UI Mean, and Why You Need Both

UX and UI sound like one job, and most people treat them that way. They are two different jobs, and a website needs both of them done well.

UX (user experience) is how a person feels while using your website. It answers one question: can the visitor get the job done without confusion? UI (user interface) is what the visitor sees and touches while doing that job: the buttons, the menus, the layout, and the type.

Think of a store. UX is the floor plan, the path from the door to the shelf to the register. UI is the signs, the price tags, and the lighting. A clear floor plan with unreadable signs loses customers, and beautiful signs with a confusing layout lose them too.

Now the follow-up question should be: which one matters more? Neither one, because a visitor meets both at the same time. A page that looks good and confuses people fails, and a page that is clear and looks careless fails too.

How People Move Through a Page

The first thing to know about visitors is that they scan. They do not read every word on a page. They move through it the way a person moves through a room, looking for the thing they came for and skipping the rest.

Nielsen Norman Group defines visual hierarchy as the organization of design elements so the eye is guided to consume each element in order of intended importance. In other words, hierarchy is the order in which a visitor notices things, and you set that order with size, weight, contrast, position, and spacing.

Eye-tracking research from Nielsen Norman Group shows that on text-heavy pages, readers scan in an F shape: two horizontal sweeps near the top, then a vertical drift down the left edge. The F-pattern is a fallback, and it shows up when a page gives the eye nothing better to land on. Clear headings, bold key terms, and short sections push readers into layer-cake scanning, where the eye lands on headings and subheadings. The Nielsen Norman Group article on the F-shaped reading pattern has the original findings.

In a 2018 eye-tracking study, the Nielsen Norman Group found that visitors spent about 57 percent of their viewing time above the fold, which is the part of the page visible without scrolling. More than anything else, that number tells you where the decision happens: at the top of the page.

Four habits keep the eye moving in the right direction:

  • The most important thing first: the answer, the price, or the next step sits near the top.
  • One headline, one job: the headline says what the page is for, in the visitor’s words.
  • One main action: each page has one thing you want the visitor to do next, and that action is the most visible button on the page.
  • Short sections: paragraphs stay short, headings say something real, and lists break up long passages.

I wrote about this from the language side in my post on how people navigate an interface like a sentence.

What Makes Navigation Work on Any Website

Navigation is the menu, and it is also the structure behind the menu. Nielsen Norman Group recommends settling the structure before designing the menu. The structure is how your pages group together. The menu is how a visitor sees those groups.

Labels carry the navigation. A label should use the visitor’s words, and it should start with the most meaningful word. “Pricing” beats “Learn More About Our Services” because the visitor came for the price.

On a desktop screen, the main paths should stay visible. Nielsen Norman Group found that hiding navigation behind a menu icon drops discoverability sharply, because a visitor cannot click a path they cannot see. A menu icon has its place on a small screen, and even there the top tasks should stay within one tap.

Three habits keep navigation working:

  • Few top choices: keep the top-level links few, and group related pages under them.
  • Labels in plain words: a label names the destination.
  • One path back: every page shows the visitor where they are and provides a clear way back to the home page.

What Makes a Page Feel Fast and Easy on a Phone

Most of your visitors arrive on a phone, and a phone forgives nothing. The screen is small, the connection is often slow, and the visitor is often doing something else. A page that feels fast and easy on a phone feels fast and easy everywhere.

Google measures that feeling with three numbers called Core Web Vitals, and it publishes a good line for each one in its web.dev documentation.

  • LCP (Largest Contentful Paint): the time until the main content appears on screen. Good is 2.5 seconds or less.
  • INP (Interaction to Next Paint): the time from a tap, click, or key press until the page shows its response. Good is 200 milliseconds or less. INP replaced First Input Delay in March 2024.
  • CLS (Cumulative Layout Shift): how much the page jumps while it loads. Good is 0.1 or less, and a page passes only when three out of four real visits meet all three lines.

A finger is wider than a mouse pointer, and it hides the thing it taps. Google’s Material Design sets the minimum touch target at 48 by 48 density-independent pixels (dp), and Apple’s guidelines set it at 44 by 44 points. The accessibility standard WCAG 2.2 sets a floor of 24 by 24 CSS pixels. Build to 48, and you satisfy all three at once.

Reach matters as much as size. A thumb sweeps an arc from the bottom corner, so the bottom of the screen is easy and the top corners are a stretch. Put the main action where the thumb already rests. Speed is a design decision too, and every late-loading banner costs visitors.

What the Ten Usability Rules Catch Before Your Visitors Do

Jakob Nielsen published ten usability heuristics with Rolf Molich in 1990, and the Nielsen Norman Group refined them in 1994. A heuristic is a rule of thumb, and these have stayed in use because they describe how people think. The full list with examples lives on the Nielsen Norman Group site. Here is the short version, in plain words.

  1. Visibility of system status: the page tells the visitor what is happening through loading signs and confirmations.
  2. Match between the system and the real world: the page speaks the visitor’s language.
  3. User control and freedom: the visitor can undo, cancel, and go back.
  4. Consistency and standards: the same button does the same thing on every page.
  5. Error prevention: the best error message is the one that never appears, so the page stops mistakes with clear constraints and confirmation first.
  6. Recognition rather than recall: the visitor never has to remember what they saw on the last page.
  7. Flexibility and efficiency of use: frequent visitors get shortcuts, and beginners get a clear path.
  8. Aesthetic and minimalist design: every extra element competes with the thing that matters.
  9. Help users recognize, diagnose, and recover from errors: when something goes wrong, the message says what happened and how to fix it.
  10. Help and documentation: when the page needs explaining, the help sits where the visitor is stuck.

Run this list against your own site.

How Accessibility Fits In, and Why It Helps Everyone

Accessibility means a website works for people with disabilities, and it also means a website works better for everyone else. The international standard is the Web Content Accessibility Guidelines (WCAG), from the World Wide Web Consortium (W3C). The current version is WCAG 2.2, published in October 2023, and most organizations aim for Level AA.

WCAG organizes its rules under four principles, remembered by the letters POUR:

  • Perceivable: the visitor can take in the information, whatever their senses. Images that carry meaning get text that describes them.
  • Operable: the visitor can use every part of the site with a keyboard alone.
  • Understandable: the visitor can follow the content and the interface. Labels are clear, and error messages say what went wrong and how to fix it.
  • Robust: the site works with the tools people use, including screen readers, so it uses real semantic markup.

WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text, and 3 to 1 for large text, and a free contrast tool checks it in seconds. It is the fastest accessibility fix on most business sites.

The same fixes help every visitor. Captions help in a noisy room. Clear labels help a hurried visitor. Large tap targets help a thumb on a moving bus.

What This Means for You

A visitor decides in seconds whether your site is worth their time, and the decision rests on two things: whether they can do the job they came for, and whether the page makes it easy. UX is the job. UI is the surface. Start with the visitor’s job, give the page one clear headline and one clear action, keep the main paths visible, make the page fast and the targets big, and write every label in plain words. That is the whole guide in one paragraph, and it is also the checklist to run against your own site this week. About Jeff’s Notes explains what this blog is for.

Leave a Reply

Your email address will not be published. Required fields are marked *