UI/UX checklist for Persian RTL websites

A Persian site is not a flipped LTR layout. Design RTL, readable type, finger-sized buttons, and a short form on purpose. Most Iranian users arrive on a phone; a pretty desktop that fails on mobile does not sell. The KGSM UI/UX checklist on kgsm.ir locks these before color and animation. Build with web design, then speed with SEO. If the form must hit a panel, include web programming from day one. Send a scope sample via contact.

This guide — UI/UX checklist for Persian RTL websites — is written from KGSM delivery work: scoped first versions, staged releases, and support after handoff.

Audience, risk, and how KGSM works

A business owner or product lead building a Persian RTL site who does not want a mirrored LTR translation

Bad mobile UI means abandoned forms, an invisible phone number, and a user who goes back to Instagram.

KGSM closes RTL visuals in web design around type, forms, and touch; SEO is checked separately but in the same phase.

Design RTL and type as the product

If you only set dir=rtl on an English theme, icons, numeral spacing, and the hamburger usually break. Limit Persian fonts to two or three weights; loading every IRANSans or Vazir file ruins LCP and fails on cheap phones. Keep numerals consistent: Persian or Latin, not mixed in price and date. Put Shamsi dates where users expect them — invoices, appointments, news — not in a hidden field. Check right alignment and line length on mobile so a paragraph does not become a skinny column. KGSM locks this in web design before the color palette. Directional icons such as a «next» arrow must flip with the language. If you also ship English, make the language switch easy to find and stable so users are not lost between two layouts.

Limit font weights to two or three files. An English theme was only rtl-flipped and the mobile menu stuck under the logo; calls dropped for a week.

Forms and touch: fewer, larger, clearer

An eight-field required contact form will not be finished in a taxi. Name, phone, and one note are enough; keep email optional. Buttons need a finger-sized target, not a twelve-pixel footer link. Make the phone number tappable and do not hide it in the mobile header. Write errors in Persian beside the field, not in an English alert. Light rate limits and captcha cut spam without exhausting a real customer. KGSM wires the form to a panel or a named inbox so messages do not vanish in a chat group. If appointments or quotes come later, extend that form in web programming instead of building three parallel forms. Test one-handed on a real device; a desktop emulator lies. Put the label above the input so it does not collide with the Persian keyboard.

Eight required fields on an ad landing pushed form submit below one percent. Cut the contact form to three core fields; keep the rest optional.

Trust, contact, and the Iranian user path

Iranian users look for trust before they type: eNamad in a sensible place, a city or address, and a real sample. A giant eNamad in the hero steals focus; footer and contact page are enough. Shorten the path service → sample → contact. A ten-item mobile menu delays the decision; keep five primaries and the rest in a submenu. A floating chat that covers the call button is a loss. Write response hours so you do not invent false waiting. Keep the KGSM brand and kgsm.ir identical in header and footer so similar names do not mix. If Instagram ads hit the site, the landing page must repeat the same promise, not a crowded home. To lock look and trust, send three competitor URLs and one real copy sample through contact so design is not a guess.

Keep a tappable phone number in the mobile header. A floating chat covered the call button and an older user could not dial.

Readability, contrast, and visual speed

Grey text on a dark background disappears in sunlight. Check contrast by eye on a cheap phone, not only with a tool score of one hundred. Scroll animation that delays content is both a UX and an SEO problem. Compress the hero and drop auto sliders unless you have a clear reason; slide jumps create CLS. Background video on Iranian mobile should be off by default. After the look is frozen, SEO measures speed and titles separately so a pretty design does not break indexing. Do not force dark mode if it wrecks brand contrast. Keep keyboard focus on forms; do not assume a mouse. KGSM hands off UI with a mobile, form, and font checklist, not an open design file without a live build.

Four font weights pushed the first page to six seconds on 4G. Place eNamad in the footer and contact page, not in the hero.

Flip directional arrows and icons for RTL. A Gregorian date on a Shamsi invoice sent the customer to support.

Forced dark mode made the price invisible on a dark background. Check text contrast on a cheap phone in daylight.

Drop auto sliders unless they carry one message. An English theme was only rtl-flipped and the mobile menu stuck under the logo; calls dropped for a week.

Eight required fields on an ad landing pushed form submit below one percent. Keep the language switch stable and easy to find.

Implementation checklist

• Limit font weights to two or three files.
• Cut the contact form to three core fields; keep the rest optional.
• Keep a tappable phone number in the mobile header.
• Place eNamad in the footer and contact page, not in the hero.
• Flip directional arrows and icons for RTL.
• Check text contrast on a cheap phone in daylight.
• Drop auto sliders unless they carry one message.
• Keep the language switch stable and easy to find.

Field scenario 1

An English theme was only rtl-flipped and the mobile menu stuck under the logo; calls dropped for a week.

Limit font weights to two or three files.

Field scenario 2

Eight required fields on an ad landing pushed form submit below one percent.

Cut the contact form to three core fields; keep the rest optional.

Field scenario 3

A floating chat covered the call button and an older user could not dial.

Keep a tappable phone number in the mobile header.

Field scenario 4

Four font weights pushed the first page to six seconds on 4G.

Place eNamad in the footer and contact page, not in the hero.

Field scenario 5

A Gregorian date on a Shamsi invoice sent the customer to support.

Flip directional arrows and icons for RTL.

Field scenario 6

Forced dark mode made the price invisible on a dark background.

Check text contrast on a cheap phone in daylight.

Related KGSM pages

Continue with KGSM services: سئو و بهینه‌سازی, طراحی سایت. Related reading: طراحی سایت فروشگاهی با Laravel — نکات مهم قبل از شروع, چه زمانی باید سایت را از نو طراحی کرد؟. For a scoped estimate, use the contact form.

When you apply this on a live team, write it as an operating rule, not a slide: Limit font weights to two or three files. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Cut the contact form to three core fields; keep the rest optional. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Keep a tappable phone number in the mobile header. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Place eNamad in the footer and contact page, not in the hero. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Flip directional arrows and icons for RTL. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Check text contrast on a cheap phone in daylight. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Drop auto sliders unless they carry one message. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Keep the language switch stable and easy to find. Then assign an owner and a review date so the rule survives the first busy week.