Why typography matters before customers read a word
Before a visitor reads your headline, they have already formed an opinion about your business. They have noticed whether the text looks cramped or comfortable, whether the headings sit evenly, whether the paragraph text feels easy on the eye. That judgement happens in seconds, and it happens on a phone screen held at arm’s length in an MRT carriage or a hawker centre queue.
That is why I treat typography as part of usability, not decoration. As a web designer, I spend more time on font sizes, spacing and contrast than on which fashionable typeface to use — because those choices decide whether someone keeps reading or gives up.
Typography is not about finding a fancy font. It is about making the site feel clear, professional and easy to use. Good typography is invisible: nobody praises it, but people trust the business behind it. Bad typography is very visible, usually in the form of text that is too small, too pale or too tightly packed.
For most Singapore small businesses, the majority of visitors arrive on a mobile phone. So poor readability is not a minor aesthetic issue — it is a direct cost to enquiries, bookings and sales. If someone has to pinch and zoom to read your address or your price list, they will often leave rather than work for it.
Start with readability: font size, line length, and line height
Three settings do most of the work: how big the text is, how long each line runs, and how much breathing room sits between lines.
Font size
Use a base body font size of at least 16px (1rem) on mobile. I would rather see 17px or 18px for a site aimed at a broad audience. That applies to body copy, and also to the parts people forget:
- Form labels and placeholder text
- Captions under images
- Footer links and small print
- Opening hours and address blocks
Placeholder text in particular is often styled so faintly and so small that it is nearly unreadable. If someone cannot see the field label, they will guess — and guessing produces wrong enquiries.
Line height
Aim for a body line height of roughly 1.5 to 1.7 times the font size. Tight line spacing makes paragraphs look like a wall of text; very loose spacing makes them feel disconnected. Somewhere in that middle range is comfortable on both mobile and desktop.
Line length
On desktop, keep paragraphs to around 45 to 75 characters per line. Wider than that and the eye struggles to find the start of the next line. Narrower than that, especially on mobile where narrow is unavoidable, make sure your font size is generous enough to compensate.
The test is simple: if a reader has to zoom or squint, the design has already failed, no matter how attractive the layout looks in a screenshot.
Choosing fonts for a Singapore SME website
Broadly, you have three options.
System fonts are already on the visitor’s device — for example the default sans-serif stacks on Android, iOS, Windows and macOS. They cost nothing to download, so they are the fastest option, and they look native to each device. The trade-off is that your brand typeface looks slightly different across platforms.
Google Fonts (and similar hosted libraries) are free and easy to add. They give you more personality than system fonts, but every weight and style you select becomes another file the browser must fetch.
Custom webfonts give you full control and a distinctive brand look. They usually come with a licence fee and require careful handling for performance.
Whichever you choose, keep the number of typefaces small. One family in three weights is usually plenty; two families — one for headings, one for body — is the practical maximum for most small-business sites.
There is a local consideration that many guides ignore: if your site includes Chinese, Tamil or Malay content, check that the chosen font family actually supports those scripts properly. A beautiful Latin typeface may fall back to a mismatched system font for Chinese characters, which looks inconsistent and can render at the wrong size. For a multilingual Singapore audience, that check is worth doing early.
Whatever you do, avoid decorative or novelty fonts for body copy. Save them for a logo or a single short headline if you must use them at all. For a deeper look at the decision, my post on choosing the right font covers pairing options and readability considerations in more detail.
Loading fonts without slowing the site
Font files are real files, and they add page weight. A family with five weights, each in two formats, plus an italic variant, can easily become several hundred kilobytes that every visitor must download before the page looks the way you designed it.
Practical steps:
- Use WOFF2 format. It is well supported and noticeably smaller than older formats.
- Load only the weights you actually use. If your design uses regular and bold, do not load light, medium, semibold and black “just in case”.
- Use
font-display: swap. This tells the browser to show a fallback font immediately and swap in your custom font when it arrives, so text is readable straight away rather than invisible. - Preconnect to the font provider if you are loading from a third-party host, so the connection is set up earlier.
- Subset where possible, so you are not shipping characters your site never uses.
Be careful about building pages that depend on many custom fonts across different sections. Each one is another request, and on a weak mobile connection in a lift or a basement carpark, the delays add up. If speed is already a concern, these tips for optimising website loading speed go further into the practical fixes.
Pairing fonts and creating hierarchy
Hierarchy means the reader can tell, at a glance, what is a heading, what is a subheading, what is body text, and what is a button. You do not need many fonts to achieve this — you need consistent sizes, weights and spacing.
A simple structure that works for most SME sites:
- One typeface for headings (or the same family in a heavier weight)
- One typeface for body text
- Three or four heading sizes defined once and reused across every page
- One button text style, used consistently
Size, weight and spacing do the work. A heading at 32px bold with generous space above it is clearly a heading without any decoration. Adding a third and fourth typeface usually makes a page look busier rather than clearer.
Inconsistency is the more common problem I see: a heading styled one way on the home page, another way on the services page, and a third way inside a blog post, usually because different sections were built at different times. Fixing this is often a matter of tidying existing styles rather than redesigning anything.
If you are weighing up whether to use a widely available typeface or invest in something custom, this comparison of common fonts and custom fonts is a useful starting point.
Accessibility and colour contrast
Typography accessibility is not only about font choice. Contrast matters just as much. Text that is technically present but pale grey on white is unreadable for many visitors, and worse for anyone with reduced vision or using a phone in bright sunlight.
Aim to meet WCAG AA contrast levels for normal text. In practice, that means avoiding light grey body text on white, and being careful with brand colours — a colour that looks striking in a logo may be far too light for paragraph text. If a brand colour fails contrast, use it for accents and backgrounds rather than for type.
Also avoid very thin or light font weights for body copy. Hairline weights look elegant in a design mockup and disappear on a real phone screen. Regular or medium weights are safer.
Finally, test on real devices, ideally outdoors. Singapore’s daylight is unforgiving, and a screen that looks fine indoors can be washed out at a bus stop. My post on colour contrast covers the checks in more detail.
Typography across devices and templates
A font size that reads comfortably on a 27-inch desktop monitor can be painfully small on a phone. This is why fixed pixel sizes set once for desktop cause problems.
Use a responsive type scale built on rem or em units, so text scales with the visitor’s own browser settings. If someone has increased their default font size because of poor eyesight, your site should respect that rather than override it.
Two things to avoid: disabling pinch-zoom, and judging type purely from a desktop browser preview. Zoom is an accessibility lifeline — never remove it. And a design that has only been reviewed in a resized desktop window has not really been tested.
Check headings, forms, menus and buttons on an actual Android phone and an actual iPhone. Check the smallest common screen width you expect. Check in both portrait and landscape. It takes fifteen minutes and catches most problems.
Common typography mistakes to avoid
- Too many typefaces, or too many weights of one typeface
- Very long lines on desktop, or cramped, tightly packed lines on mobile
- Low-contrast text, especially grey on white and brand colours used for body copy
- Justified text, which creates awkward gaps and rivers of white space on the web
- All-caps body copy, which is harder to read than sentence case
- Different heading styles on different pages, usually from ad-hoc editing
- Text baked into images, which cannot be resized by the reader or read by search engines
Quick pre-launch typography checklist
- Base font size is at least 16px on mobile
- Line spacing and line length feel comfortable to read
- Font loading causes no visible layout shift or blank text
- Text contrast passes an accessibility check
- Headings and body text use consistent styles across pages
- The site has been tested on both Android and iOS devices
- Form labels, captions and footer text are all readable without zooming
Get the typography right before launch
Typography is a practical business issue. It affects whether people trust your site, whether they can read it on the phone in their hand, and how quickly the page appears. None of that is cosmetic — it shows up in whether someone enquires or leaves.
If you are unsure how your current site measures up, I am happy to take a look and give you a straight answer on what is worth fixing. You can get in touch with a link to your site and a note on what is bothering you, and I will come back with practical suggestions rather than a sales pitch.