Saudi-built solutions

Your website from SAR 39 a month · cancel anytime · upgrade anytimePrice calculatorCurrency

🎧 A world-class website from SAR 39Listen: why clients choose Webnaa
0:00 / 1:28

UX and UI design for websites: how to plan a site people can actually use

A website can look polished and still lose customers, because looking good and being easy to use are two different jobs. UX and UI design split those jobs: UX decides what visitors need and how they move through the site, while UI decides what each screen looks like and how every button, menu and form behaves. This guide shows how to plan both for a business website in Saudi Arabia, from research on a small budget and user journeys to wireframes, testing with five people, accessibility and what to measure after launch.

Web Design17 min readUpdated October 2026

Blank sticky notes laid out in rows beside a keyboard and a marker, ready to map a website's pages
Good websites are planned on paper before anyone opens a design tool. Photo: Kelly Sikkema on Unsplash

In short:

  • UX is the whole experience of finding, understanding and acting on your site; UI is the visible layer of layout, type, colour and controls. A site needs both.
  • You can do useful research for almost nothing: talk to a handful of customers and read your WhatsApp history before anyone draws a screen.
  • Plan structure with wireframes, then watch five real people try your key tasks. Small rounds of testing find most serious problems.
  • Accessibility, speed and clear calls to action are part of the experience, not extras, and they can be measured after launch.
In this guide
  1. UX vs UI
  2. Research and user journeys
  3. Wireframes and prototypes
  4. Testing with five users
  5. UI components and design systems
  6. Accessibility
  7. Measuring after launch
  8. Common mistakes
  9. UX and UI at Webnaa
  10. FAQ
  11. Summary

UX vs UI design: two jobs inside one website

UX stands for user experience. Nielsen Norman Group defines it as every part of a person's interaction with a company, its services and its products. On a website, that covers whether visitors find the page they need, understand what you offer, trust you enough to get in touch and manage to do it without friction. UX work happens mostly before anything is drawn: research, deciding which pages exist, what goes on each one and in what order.

UI stands for user interface: the screens themselves. It is the layout grid, the typefaces and sizes, the colours, icons, buttons, menus, form fields and the small states that tell you something happened, such as a button changing when you tap it or a message confirming a form was sent. UI is what people usually mean when they say a site "looks good".

The two depend on each other, but one cannot rescue the other. NN/g makes the point with a film review site whose search interface is flawless but whose database only lists major studio films: the visitor looking for a small independent film still has a bad experience. Translate that to a Saudi clinic: a beautiful booking form is useless if the site never says which insurance the clinic accepts, because that is the question patients came with.

UX designUI design
Main questionCan people do what they came to do?Is each screen clear, consistent and pleasant to use?
Typical outputsResearch notes, user journeys, sitemap, wireframes, test findingsVisual designs, colour and type rules, component library, interaction states
MethodsInterviews, task analysis, card sorting, usability testing, analyticsLayout grids, visual hierarchy, contrast checks, prototyping micro-interactions
Fails whenThe site answers questions nobody asks and hides the ones they doButtons look like text, labels are vague, the page feels cluttered
Example fixMoving prices and service areas onto the service pageMaking the WhatsApp button one clear colour and the same on every page

Think of a shop. UX is the floor plan: where the entrance is and how far the cashier is from the door. UI is the signage, lighting and price tags. A beautiful sign over a confusing floor plan still loses customers.

In most small web design projects one designer handles both, and that is fine as long as both questions get asked. If you want the wider picture of where UX and UI sit alongside content, build and SEO, start with our guide to what web design includes.

From research to user journeys

UX research on a small budget

Research sounds expensive, but for a business website most of the evidence already sits inside your company. Collect it before you brief anyone; it is the cheapest part of any web design project and the one that saves the most rework:

  • Your WhatsApp and phone history. Scroll back through the last month of enquiries and write down every question. The ones that repeat are the content your website is missing.
  • Front-line staff. Ask whoever answers the phone or greets clients for the ten questions they hear most and the three moments when customers get confused or give up.
  • Five short customer conversations. Ask recent customers how they found you, what they compared, what almost stopped them and what device they used. Fifteen minutes each is enough.
  • Reviews and questions on Google. Your Google Business Profile shows what people praise, complain about and ask before visiting. Our guide to Google Business Profile in Saudi Arabia explains where to find them.
  • Search Console, if you already have a site. The queries report shows the words people type before landing on your pages, in Arabic and English.

Summarise the findings on one page: who your main visitors are, what they need to decide, what worries them, which language they prefer and which device they use. A short list of real needs beats invented personas with names and hobbies.

Pick the top tasks

Choose the three to five tasks the website must make easy. For most Saudi businesses they are: understand what you offer, check that you serve their city, get a sense of price or process, see proof that you are reliable, and contact you on WhatsApp or by phone. Every page and button should serve at least one of these tasks.

Mapping a user journey: a worked example

A user journey follows one visitor from the moment a need appears to the moment they act. Take a home maintenance company in Jeddah. It is August, an air conditioner has stopped, and the homeowner searches on a phone:

StepWhat the visitor needsWhat the page should showWhat usually breaks
SearchA result that matches the problemA dedicated AC repair page with a clear titleOnly a generic "Services" page exists
LandConfirmation in seconds that this is the right companyHeadline naming the service and the city, plus a visible WhatsApp buttonA slider of stock photos with no text
CheckAreas covered, how soon a technician can come, rough costA short list of districts, typical response time, how the visit fee works"Contact us for details" on everything
TrustEvidence the company is realCommercial registration details, photos of real jobs, reviewsNo address, no reviews, copied photos
ActA fast way to bookWhatsApp with a pre-filled message, a tap-to-call numberA long form that asks for email first

Now compare a procurement officer at a factory in Dammam choosing an industrial supplier. They sit at a desktop, compare vendors over a week and need certifications, product specifications and a quote form that accepts attachments. A different journey needs different pages and a different main button. Two or three journeys like these tell the designer more than any mood board.

Write the journeys into your brief. Our website brief template has space for goals, audiences and the actions you want visitors to take.

Wireframes and prototypes: structure before colour

A wireframe is a simple drawing of a page made of boxes and lines: here the headline, here a photo, here three service cards, here the contact button. It deliberately has no colours, fonts or real images, so everyone discusses what matters at this stage: what appears on the page and in what order. A wireframe can be a pencil sketch on paper or a grey layout in a design tool such as Figma.

A good homepage wireframe settles these decisions before any visual design starts:

  1. What the first screen says, in one sentence, about who you are and what you do.
  2. Which single action is primary (often WhatsApp or a quote request) and which is secondary.
  3. The order of sections below: services, proof, process, areas, frequently asked questions, contact.
  4. What the menu contains, with labels your customers would use rather than internal department names.
  5. How the page stacks on a phone, since most of your visitors will probably see the mobile version first.
  6. Where trust signals sit: registration details, reviews, client sectors, guarantees you actually offer.
Hand-drawn website wireframes on paper showing boxes for the header, images, text and buttons
A wireframe uses plain boxes and lines so the conversation stays on structure and priority. Changing a sketch takes minutes; changing a finished design takes days. Photo: Hal Gatewood on Unsplash

Sketch the phone layout first and the desktop second. A narrow screen forces you to rank content, and a ranking that works on a phone usually works on a laptop. We explain the reasoning in design for mobile first.

Use real words, not placeholder text

Dummy text hides the hardest problems: a real headline may be twice as long as the box allows. Put rough versions of the actual copy into the wireframe. If you need help with the words, see website copy that persuades.

Wireframe Arabic and English separately

A bilingual site is not one layout with translated text. Arabic pages run right to left, so the menu, reading order and "next" arrows are mirrored, and the same message often takes a different length in each language, which changes line breaks and button widths. Draw at least the homepage and one inner page in both directions. Our bilingual website design guide covers the details.

When a prototype is worth it

A prototype is a clickable version of the design: tap the menu and it opens, tap a service and the next screen appears, though nothing is built yet. For a five-page company site, linked wireframes are usually enough. For a multi-step flow, such as booking, a quote calculator or course registration, a prototype pays for itself because you can test the flow before any code exists.

Usability testing with five users

Usability testing means watching real people try real tasks on your design while you stay quiet and take notes. It is the most useful step in UX and UI design and the one most often skipped, because owners assume it needs a lab.

It does not. In a well-known article, Jakob Nielsen of Nielsen Norman Group showed that a test with five participants uncovers about 85% of the usability problems, because each new person mostly repeats what the earlier ones ran into. His advice is to spend the budget on several small rounds rather than one big one: test with five, fix what you found, then test the new version with another five. If you have clearly different audiences, for example homeowners and property managers, he suggests three or four people from each group.

Watching five customers struggle with your site teaches you more than a month of internal meetings about it.

Here is how to run a simple round yourself, without a lab or special software:

Choose three tasks

Take them straight from your top tasks: find out whether you serve their district, find the price range, send an enquiry.

Recruit the right people

Real or likely customers, not your staff or designer. Recent clients, people in your waiting area or contacts who match your audience all work.

Write tasks as situations

Describe a need, not a button. Use the visitor's words, not the labels on your menu, or you will only test whether people can match words.

Watch, do not help

Ask people to think aloud. Note where they hesitate, scroll back, tap the wrong thing or say "I would just call". Resist explaining the design.

Fix, then test again

List problems that affected two or more people, fix the worst first, and run another short round on the revised version.

The wording of a task matters more than most people expect. "Click on Services and find AC maintenance" tells the participant where to go, so you learn nothing. "Your air conditioner is leaking water and you live in Al Rawdah. Find out whether this company can send someone this week" mirrors a real situation and reveals whether your structure works.

A video call with screen sharing works well for phone testing: the participant opens the preview link on their own device and shares the screen. Test each language version with people who read that language, and offer a small thank-you, such as a coffee voucher, for twenty minutes of their time.

Know the limits. Five people will not tell you which of two headlines brings more enquiries; that needs live traffic. What they reveal is behaviour: where people get lost, what they misread and what they cannot find.

UI components and design systems

Once the structure works, UI design turns wireframes into screens. Most business websites use the same handful of components, each with a few rules that decide whether it helps or frustrates.

Navigation

Five to seven top-level items with plain labels. The current page is highlighted, the logo returns home, and on phones the menu opens with one tap and closes just as easily.

Buttons

One primary style for the main action and one quieter style for secondary actions. Labels say what happens: "Message us on WhatsApp", not "Submit" or "Click here".

Forms

Only the fields you need, labels above fields, and a phone field that accepts both 05 and +966 formats. Error messages explain how to fix the problem, next to the field.

Cards and lists

Services, projects and client sectors shown as cards of equal weight, each with a short title, one line of detail and a link. The whole card should be tappable, not only a tiny "more" link.

Feedback and states

Every control shows hover, focus and pressed states. After a form is sent, a clear confirmation says what happens next and when you will reply.

Text and headings

A clear size hierarchy so people can scan: headings that state the point, short paragraphs and comfortable line length. Arabic text usually needs a slightly larger size and more line height than English.

The first screen on a phone is where these rules meet: headline, menu and primary action in a few centimetres of glass.

Top of the Webnaa English home page on a phone, with the header, hero headline and call-to-action buttons
On a phone the first screen carries the whole interface: a short headline, a menu that folds away and one primary button styled to stand out from the secondary one. Check your own site on a phone the same way.

A design system, even for a small site

A design system is the set of rules and reusable parts that keep every page consistent. Large companies maintain whole libraries; a small business site needs only a compact version, written down in one document or kept in the design file:

  • Colour tokens: a primary colour for actions, a text colour, a background, one accent and colours for success and error messages, each with its exact code.
  • Type scale: fixed sizes for headings, body text and small print, chosen once for Arabic and once for English.
  • Spacing: a small set of spacing steps used everywhere, so sections breathe the same way on every page.
  • Components: the button, card, form field, alert and section styles described above, each with its states.
  • Content rules: how you write button labels, dates, prices and phone numbers, and whether you use Western or Arabic-Indic digits.

The benefit appears months later, when a new page added in WordPress reuses existing blocks instead of inventing a new button colour. For choosing the colours and fonts themselves, read our guide to colour and typography in web design.

Accessibility belongs in both UX and UI

Accessibility means people can use your site whatever their eyesight, hearing, motor control or device. Most of it is decided during design, not at the end, and it helps everyone: good contrast helps anyone reading a phone in bright sunlight.

The reference standard is the W3C's Web Content Accessibility Guidelines, currently WCAG 2.2. Level AA is the usual target for business sites, and a few of its criteria shape UI decisions directly:

  • Text contrast: at least 4.5:1 between normal text and its background, and 3:1 for large text, which W3C describes as roughly 24 px regular or 18.5 px bold. Light grey text on white usually fails.
  • Target size: clickable targets of at least 24 by 24 CSS pixels, or enough space around smaller ones, with exceptions such as links inside a sentence. Tiny social icons squeezed together are a common failure.
  • Not colour alone: a red border is not enough to mark a form error; add a message and an icon.
  • Keyboard and focus: every menu, button and form field can be reached with the keyboard, and the focused element is clearly visible.

On the UX side, accessibility looks like plain language, headings in a logical order, descriptive link text, alternative text for informative images, forms that do not time out and instructions that do not depend on "the button on the right", which is on the left in the Arabic version. For Arabic pages, check that the page declares its language and direction correctly so screen readers pronounce the text properly, and that icons pointing forward are mirrored.

Our website accessibility checklist turns WCAG 2.2 into practical checks you can run on a business site in an afternoon.

Measuring UX after launch

Launch is when real data starts. The aim is to find out whether visitors complete the top tasks you chose and where they drop out; "more traffic" alone tells you little about the experience.

What to measureWhere to find itWhat it tells youTypical action
WhatsApp, call and form clicksEvents in your analytics toolWhether visitors take the main action, and from which pagesMove or reword the button on pages that get visits but no clicks
Search queries and click-throughGoogle Search ConsoleWhich needs bring people in and whether titles match themRewrite titles, add a page for a repeated need
Exit pagesAnalytics page reportsWhere people leave before actingCheck that page for missing information or a weak next step
Loading and responsivenessCore Web Vitals report, PageSpeed InsightsWhether the site feels fast on real phonesCompress images, remove heavy scripts and sliders
Questions customers still askWhatsApp, phone, front deskInformation the site still fails to giveAdd it to the relevant page or the FAQ

Speed is part of the experience, and Google publishes clear targets for it. On web.dev, a page passes the Core Web Vitals when the largest content element appears within 2.5 seconds (LCP), the page responds to taps and clicks within 200 milliseconds (INP) and the layout shifts by no more than 0.1 (CLS), measured at the 75th percentile of real visits on mobile and desktop separately. A slow, jumpy page is a UX problem however good it looks; we explain the business side in website speed drives sales.

Numbers show where something goes wrong; they rarely show why. Keep asking new customers whether anything on the site was hard to find, and repeat a quick five-person test on key pages every few months. A monthly half-hour review with one change each time beats a large redesign every few years. See after your website launches for a fuller routine.

Common UX and UI mistakes on business websites

These web design mistakes appear again and again on Saudi company websites, and most are cheap to fix once you notice them:

  1. Approving the design on a desktop screen. Owners review on a large monitor while customers see a phone. Review every page on a phone first.
  2. A hero slider instead of a message. Rotating banners move before people finish reading. One clear headline and one action work better.
  3. Menu labels in company language. "Solutions", "Divisions" and "Our world" mean little to visitors. Name services the way customers search for them.
  4. Hiding the basics. No service areas, no working hours, no indication of price or process. Each missing answer becomes a WhatsApp message, or a lost visitor.
  5. Forms that ask too much. Mandatory email and company size before a simple callback request. Ask for a name and phone number; gather the rest in conversation.
  6. Too many buttons competing. Five brightly coloured buttons on one screen means none of them stands out. Choose one primary action per page.
  7. Treating Arabic as a translation. Text pasted into a left-to-right layout, punctuation in the wrong place and Latin fonts used for Arabic make the site feel foreign to its main audience.
  8. Important content in PDFs or images. Price lists and company profiles locked in files are hard to read on phones and invisible to search. Put the key points on the page.

For more problems that quietly cost enquiries, read mistakes that cost customers, and for the signals that make visitors comfortable contacting you, trust signals that convert.

How Webnaa approaches UX and UI on a business website

Webnaa is a website design service in Saudi Arabia, based in Riyadh, that builds professional websites for businesses on a subscription. Many of the UX basics in this guide are built into the way the service works:

  • We write the content for you, in Arabic, English or both, so the pages answer the questions your customers ask instead of waiting for text that never arrives.
  • Every site is fast and mobile-friendly, with a WhatsApp button, a direct call number, an inquiry form and a map location for the "act" step of most journeys.
  • You review the design on a preview link before launch, and we test it on phone and computer. The preview is a good moment to run the five-person test from this guide yourself.
  • After launch you can act on what you measure: reword a button, add a missing answer, update a price. On a WordPress website you make these changes yourself from the dashboard.

Prices start from SAR 39 a month, and every website is priced by type, pages and languages; for example, a 5-page bilingual WordPress website with a dashboard to edit the site yourself is SAR 324 a month. Every website includes content written for you, hosting and SSL (and a domain in your name on every custom-domain website), with no setup fee and no long contract, and prices are paid in advance, every 6 months or for a full year with 10% off.

The preview link takes 24 hours at most once we have all the information and content we need from you, and if you do not like the design during the design stage, a money-back guarantee applies, per the refund policy. See what is included on our website design service page and price your site in our price calculator. If you already have a site that looks fine but does not bring enquiries, our website redesign service starts from the same questions about tasks and journeys.

Price calculator

Choose what you need, see your exact price

The price updates with every choice. No surprises, no hidden fees.

The calculator is off. Press the power button to start

1Domain

Where will your website live: on a Webnaa address, or on a domain in your business name?

The SAR plan is one page in one language, paid yearly. Need more pages, a second language or paying every 6 months?
2Website type

Who edits your website after launch? On static we edit it for you; on WordPress you edit it yourself from a dashboard.

3LanguagesPriced by how many languages, not which

How many languages will your visitors read?

Language
Second language
Home, About, Services, Contact…

How many pages does your business need? If you are not sure, five pages suit most businesses.

5Payment

A subscription paid every 6 months or yearly that keeps your website with us, or buy the website in one payment and own it.

Optional extrasDon’t need them? Skip them; your price is ready.
Monthly article planOptional · up to words per article, with its image, publishing and SEO basics
Need more than articles a month? Request a quote
Your logoHave one, or we design it
Business emailOptional · addresses on your domain, like info@yourname.com

Whoever you work with, these questions show quickly whether a provider thinks about UX or only about visuals:

  • What do you need to know about my customers before you design anything?
  • Will I see the structure of the pages before the visual design?
  • How do you check the design on phones and in both languages?
  • Which accessibility checks do you run before launch?
  • After launch, how do I find out whether visitors are contacting me, and who makes the changes?

For the wider selection process, read how to choose a web design company.

A website planned around your customers

Tested on phone and computer, reviewed on a preview link before launch. Prices from SAR 39 a month, with content written for you on every website.

FAQ

What is the difference between UX and UI design?

UX design is about the whole experience: what visitors need, which pages exist and how people move through them to reach a goal. UI design is about the screens: layout, typography, colour, buttons, forms and how they respond. UX decides what a page must do; UI decides how it looks and feels while doing it.

Does a small business website need a separate UX designer?

Usually not. One designer can cover both, provided the process includes research into customer questions, a page structure agreed before visuals, and checks on real phones.

How many users do you need for usability testing?

For finding problems, five per round is the classic guidance from Nielsen Norman Group, which found that five participants reveal about 85% of usability issues. Run several small rounds with fixes in between, and use three or four people per group if your audiences differ clearly.

What tools are used for UX and UI design?

Paper for early wireframes, a tool such as Figma for layouts and prototypes, a contrast checker, and analytics plus Google Search Console after launch. The order matters more than the tools.

Is UX design the same as web design?

No. Web design is the broader job of planning, designing and building a website, and it includes UX, UI, content, development and search basics. UX is one part of it, focused on whether the site works for the people using it.

Summary

Good UX and UI design starts with your customers, not with colours. Collect the questions they already ask, pick the few tasks the site must make easy, map the journeys, and agree the page structure in wireframes. Then design clear, consistent components, meet the WCAG 2.2 basics for contrast and target size, and watch five real people use the result before launch. After launch, measure whether visitors take the main action, keep the site fast, and improve one thing at a time. That routine is the difference between web design people admire and a website they actually use.

Sources: Nielsen Norman Group: the definition of user experience, Nielsen Norman Group: why you only need to test with 5 users, W3C: Understanding WCAG 2.2 contrast (minimum), W3C: Understanding WCAG 2.2 target size (minimum), web.dev: Web Vitals. Webnaa: how we work, pricing.

Send a note

Coming from the page: Article: UX and UI design for websites: how to plan a site people can actually use

One moment…