Hebrew landing page design: 10 decisions that determine whether a visitor leaves their details

Landing page design is not a question of taste. Every decision on the page, from the size of the headline to the position of the button, either moves the visitor closer to leaving their details or pushes them away. A great many guides and templates were built for English and for a desktop screen, and on a Hebrew page opening on a phone they break in exactly the places that matter. In this article we have gathered 10 design decisions for a landing page in Hebrew: hierarchy, the first screen on a phone, right-to-left direction, the form, contrast, images and speed. At the end you will find what to put in the brief for your designer, and what to insist on receiving when the work is done.

Landing page design starts with the text, not the colours

Decision 1: the text is written before the design. A designer handed "make something nice, the text will follow" fills the screen with dummy lines of uniform length. Then a headline arrives that runs to two lines instead of one, and the first screen breaks. So: headline, benefits, frequently asked questions and button text first, and only then design. What goes into each section is set out in our complete guide to building a landing page.

Decision 2: one important thing per screen. Visual hierarchy means that at every screen height there is a single element standing out more than the rest: a headline, an image or a button. If three large, bright things share a screen, the eye does not know where to go. A simple test: look at each screen for one second, cover it, and try to say what you saw first. If the answer is not what you intended, the hierarchy is not working.

The first screen on a phone: what has to fit without scrolling

Decision 3: four things before the first scroll. A headline that says what you get, one line explaining who it is for, an action button, and a small trust cue — a genuine review count, or a familiar logo. A large image that pushes the button below the fold is a common mistake. Design this screen for the phone first, and check it on a real handset, not only in a desktop preview.

Decision 4: the button goes where the thumb is. On a phone, the comfortable tapping area is the lower part of the screen. So it is worth considering a fixed action bar at the bottom with one primary button — and, if WhatsApp is your enquiry channel, that too. According to web.dev, the recommended minimum tap target size is around 48 pixels, with roughly 8 pixels of spacing between tap targets. A smaller button leads to mis-taps, mostly on adjacent links.

Hebrew right-to-left: 3 decisions translated templates get wrong

Decision 5: the flow runs right to left, down to the last icon. A Hebrew reader's eye starts in the top-right corner. Headlines, lists and forms are aligned to the right. Arrows that mean "next" point left, and galleries and sliders advance leftwards. In a template translated from English, at least one of those is usually still the wrong way round.

Decision 6: a real Hebrew typeface, and numbers that do not flip. Choose a font that was designed for Hebrew, with Latin letters that sit well alongside it, because product names in English will appear inside your sentences. Limit yourself to two weights, regular and bold. For body text on a phone we recommend at least 16 pixels, with generous line spacing. On top of that, check every phone number, price range and date inside a Hebrew sentence. A mix of Hebrew, digits and English is exactly where a sequence ends up displayed in the wrong order.

Decision 7: fields typed in English stay left-to-right. The label is aligned right, but an email or phone field is typed left to right. Otherwise the cursor jumps and the visitor thinks they have made a mistake. And in a phone field, accept a number typed with a hyphen and without one, instead of showing a format error.

Form, contrast and accessibility

Decision 8: a form that looks short, and is short. A name and a phone number, with a visible label above each field rather than only grey text inside the field that disappears as soon as you start typing. A phone field opens a numeric keypad. An error message appears next to the relevant field, in plain language. And plan the screen that comes after the submission as well: what to put on it is set out in the thank-you page.

Decision 9: contrast that meets the standard, not just "looks fine". According to MDN's explanation of the WCAG contrast criterion, the contrast ratio between text and background should be at least 4.5:1, and at least 3:1 for large text. Large text is defined there as at least 18pt, or 14pt bold. Light grey text on white, and white on a light image, frequently fail this. What Israeli law requires of websites, and what an accessibility adaptation includes, is explained in our website accessibility guide.

Images, video and speed

Decision 10: every visual element earns its place. A real photograph of the team, the work or the product is usually better than a stock shot. A video behind the first screen looks impressive, but it weighs on loading on a phone, so a short clip that only starts on a tap is the better option. AI-generated images suit illustration; they suit "happy customers" far less. When they do work is set out in our article on AI images and videos in marketing.

Every decision like that is ultimately measured in speed. According to web.dev, good Core Web Vitals values are an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1, measured at the 75th percentile of visits. In practice, for a designer that means: one compressed main image, two font weights, and space reserved in advance for every image so that the text does not jump while the page loads. How to check those numbers is explained in our website speed guide.

The designer brief: what to hand over and what to get back

What to give the designer:

1. The goal, and the one action of the page.
2. The audience, and where they arrive from: a Google search, a social network or WhatsApp.
3. The complete text, including the frequently asked questions and the button text.
4. A logo, brand colours and fonts, if you have them.
5. Real photographs, or a list of what needs to be shot.

What to get back at the end: a design for phone and for desktop, the form states (error and success), the design of the thank-you page, and the source files with full rights. Before you approve anything, open the design on your own phone, at real size, rather than only as a file on a large screen.

What does it cost? According to Midrag, the price of designing a landing page runs ₪1,000–3,500, depending on the complexity of the work. Note that this is a price for the design, not for a complete page with writing, build and measurement.

What Simple Web does about it

Simple Web is an AI-first marketing agency from Bnei Brak, certified Meta partners and Google advertising experts, working with 200+ businesses and holding 35 five-star Google reviews. We build landing pages with AI, on the principle of one message, one action and a short form — usually a name and a phone number. The design is done mobile-first, the pixels and conversion tracking are connected, and after launch you can add a heatmap and A/B tests to see where visitors stop. A landing page is usually ready within 5–7 working days, and the price comes as a quote based on scope.

Summary

Landing page design in Hebrew is a sequence of small decisions: text before design, one thing standing out per screen, a first screen that works on a phone, and the right direction of flow down to the last icon. After those come a form with visible labels, contrast that meets the standard, and speed that is measured rather than guessed. Give your designer a complete brief, and ask to receive the form states and the thank-you page as well. Want us to go over the design of your page with you? Book a free diagnostic call.

Sources

• web.dev: Accessible tap targets: a minimum tap target of around 48 pixels and roughly 8 pixels of spacing
• MDN: Color contrast: the 4.5:1 and 3:1 contrast ratios and the definition of large text
• web.dev: Web Vitals: the thresholds for LCP, INP and CLS, and measurement at the 75th percentile
• Midrag: landing page design: the price range for landing page design