UI/UX design in plain terms: UX is about whether a person reaches the purchase without effort, UI is about how it looks and whether it is obvious where to click. Both affect sales from a website, but in different ways: poor UX logic buries the order button below the third screen and adds twelve fields to the form, while weak UI paints that button gray on a gray background so even those who get there do not see it. Below we explain the difference with examples, show how usability eats conversion, and give a 10-point checklist for a quick audit any owner can run in an hour.

UX (user experience) is the path from landing on the site to the desired action, and how logical that path is. UI (user interface) is the interface itself: buttons, fields, colors, typefaces, spacing, hover states. The UX designer decides what to show and in which order; the UI designer decides exactly how to draw it. In small teams this is one person, in large products two separate roles.
| Criterion | UX | UI |
|---|---|---|
| Responsible for | Logic, flows, steps to action | Look, states, visual hierarchy |
| Key question | Is it clear what to do next | Is it clear where to tap |
| Deliverables | CJM, wireframes, prototypes | Moodboard, design system, mockups |
| Tools | Figma, Hotjar/Clarity, GA, interviews | Figma, Adobe, contrast checkers |
| Metrics | Conversion, bounces, time to action | Misclicks, readability |
The practical takeaway: if people do not buy, look for the problem in UX first. If they buy but complain that the site "looks cheap", the problem is UI. Most often at Query we see a mix: the logic works overall, but there are a few UX holes at key steps plus visual noise that hides them.
Three examples that come up in every second audit.
A 12-field form. A consultation request asks for first name, last name, middle name, phone, email, city, company, job title, budget, convenient time, how you heard about us, and a comment. Half of that the manager will ask on the call anyway. Every extra field filters out a share of people, and on mobile the effect is stronger. A working first-contact form: name, phone or messenger, and if needed one question about the task.
CTA below the fold. The homepage has a beautiful banner, then benefits, then testimonials, and only after that an "Order" button. A desktop user may still scroll down; a mobile user leaves earlier. The action button belongs on the first screen, in the header, and should repeat after every content block.
A slow mobile version. The site takes 6 seconds to open, catalog items have no "add to cart" button without opening the product page, filters expand to full screen and close on the third attempt. In our observation, mobile traffic has long dominated in most niches, so every second and every extra tap costs more there than on desktop.
Simpler but no less painful things: no catalog search, prices shown only after registration, the form does not show which field has an error, the "Back" button leads to the homepage instead of the previous step.

Once the logic is verified, the UI designer turns the prototype into mockups. The key deliverable here is the design system: a set of colors, type styles, buttons, fields, cards and rules for using them. It makes the site coherent and makes every next page cheaper, because the developer assembles it from ready components instead of drawing from scratch. How this work looks at an agency is described on our website design page.
Accessibility is not only about people with visual impairments: high-contrast text is readable on a phone in the sun, large tap targets help on public transport, field labels help everyone. The minimum WCAG contrast for regular text is 4.5:1, for large text 3:1, and any contrast checker will verify it. The gray-on-white text fashionable in recent years often fails that bar.
Visual hierarchy: a screen should have one primary action, and it should be the most prominent thing on it. Two identical "Buy" and "Learn more" buttons side by side split attention in half. Element states (hover, pressed, disabled, error) are drawn in the design system, otherwise the developer invents them.
Go through the list on a phone, not on your work computer. Every "no" is a potential point where customers are lost.
If you count three or more "no" answers, a full UI/UX design audit with session recordings and a prioritized list of fixes is worth it. We covered the basic usability rules separately in our article on website usability.
