Why a Clear Home Button Matters on a Microsite

A microsite is a small, single-purpose website: a landing page built around one offer, one download, or one short piece of information. Because the content is deliberately lean, the navigation carries far more weight than it would on a full site. Visitors usually arrive from a search result, a message thread, a printed poster, or a QR code, and they often hold exactly one question. The links they can see settle whether they stay or drift away.

Among the smallest elements on a page like that sits the control that returns a visitor to the start. On a desktop monitor it looks like an afterthought — a house glyph, a word, a logo tucked into a corner. On a phone, gripped one-handed on a crowded peak-hour train into Melbourne's CBD, the same control decides whether someone finds what they came for or closes the tab.

What follows examines how navigation behaves on small screens, what a home control actually tells a visitor, how to design one so it cannot be missed, how it sits alongside Australian privacy and advertising expectations, and how to check whether it is doing any work at all. The argument stays narrow throughout: one control, one clear label, one obvious destination.

How navigation behaves on small screens

Most Australian traffic to a lean landing page now arrives on a handset, and a large share of it is browsed in short bursts: on the platform at Circular Quay, during an arvo coffee break, or on a patchy connection in regional Queensland. Scrolling is fast, forgiving, and almost entirely vertical, which puts the top of the screen in the worst possible position for a one-thumb grip. Controls placed high on the page are the hardest to reach without regripping the device.

On a microsite, a visitor may never scroll more than a screen or two, because there is not much further to go. A header that scrolls out of view takes any home control with it, and it disappears at the precise moment a confused visitor needs it. The practical options are a header that stays pinned, a control anchored near the bottom of the display where the thumb already rests, or the same control repeated in a footer block that visitors reach after a full read.

Care is needed, because phone browsers already own visual language that competes for the house symbol. The browser's own home shortcut, the favicon beside the address bar, and the "add to home screen" prompt all wear similar clothing. When a microsite adds its own house glyph without a word attached, visitors can reasonably wonder whether they are leaving the site, bookmarking it, or returning to their previous screen.

What the home control signals to visitors

A home control works less as a shortcut than as an orientation marker. Search engines routinely land people on a section anchor, a deep-linked paragraph, or the bottom of a page, so a visitor can begin without ever seeing the opening screen. Returning to the start restores the mental model: this is the page you searched for, and this is where its contents begin.

It also carries a light signal of accountability. A page that names its own starting point feels more like a documented, maintained destination than a disposable splash screen, and that impression matters when the topic is betting or gambling content, where visitors have learned to distrust sites that hide where they are pointing. A visitor who taps the control expects a return to the site's homepage rather than a grid of unrelated campaigns, a booking flow, or an entirely different domain.

The third job is separation. A home control is not a back button, and it is not an exit. Those distinctions need space: keep the in-page anchor links apart from the return-to-start link, and keep the browser's back gesture untouched. Overloading one label with several meanings weakens all of them.

Design choices that make the control obvious

Words still win here. A pictogram requires a moment of interpretation, while the word "Home" or "Main page" can be read at a glance by someone glancing up from a noisy carriage. Pairing a small icon with a written label costs a few pixels and removes almost all of the guesswork, particularly for visitors whose first language is not English.

Spacing and size decide whether the intention survives contact with a fingertip. Australian accessibility practice follows WCAG 2.2 AA guidance closely, so a contrast ratio of at least 4.5:1 between the label and its background is a sensible floor, and a tap area of roughly 44 by 44 CSS pixels avoids the near-miss that plagues a bouncing train. Keep clear space between the home control and any neighbouring link, and keep it visually distinct from the primary call to action so it does not look like the main event.

On betting and casino pages there is one extra trap: "home" and "house" are near neighbours in that vocabulary, and a heading such as "House Games" sitting one scroll away can make an icon-only control read as a shortcut into that category. Reserve the house glyph for the return-to-start control alone, and give the category its own wording.

Accessibility also extends beyond sight. The link needs an accessible name so screen readers announce it as a link with a meaningful label, it needs a visible focus ring for keyboard users, and it needs a sensible position in the focus order. A header that is visually hidden from assistive technology but visually obvious to sighted users is a common and expensive failure.

Speed, accessibility and Australian legal expectations

Navigation that arrives late is navigation that fails. Every kilobyte of script delays the moment a visitor can act, and that delay lands hardest on prepaid mobile data and on regional fixed connections where NBN availability and speeds still vary widely. Compress images, defer what can be deferred, and check that the control renders before the analytics bundle finishes loading, because a link that appears after the visitor has already scrolled away has missed its purpose.

Data handling has its own local frame. The Privacy Act 1988 and the Australian Privacy Principles set the baseline for how personal information and online identifiers are collected, and Australian Communications and Media Authority guidance expects clear notice and genuine consent around cookies and analytics. That makes navigation and disclosure part of the same design problem: a visitor who follows the privacy policy page from the header should land on plain language about what is logged, for how long, and how to have it removed.

Advertising rules add a second layer for betting-related content. The Australian New Zealand-style advertising code, applied alongside state regulators such as Liquor and Gaming NSW and the Victorian Gambling and Lotteries Commission, shapes what claims can be made and where responsible gambling messaging must sit. The Australian Communications and Media Authority and Scamwatch have also issued repeated warnings about fraudulent download pages and look-alike domains, which makes a site that clearly states what it is, and where its links lead, quietly reassuring.

Putting the control to work

Whether the home control earns its place is measurable. Track taps on it through consented analytics, then compare scroll depth, time on page, and completion rates for visitors who use it against those who never touch it. A control with a high click rate and no change in outcomes is decoration; one that correlates with longer sessions is doing real work.

Three common approaches side by side:

Approach Visibility on a phone Clarity for a first-time visitor Typical tap target Common snag
House icon alone in the header Vanishes once the header scrolls Low, reads as a logo or browser shortcut 24–32 px Confused with the favicon or an install prompt
Icon with a written "Home" label Clear while the header is pinned High, the word removes the guesswork 44 px and above Clutters a header that already carries a call to action
Text link in a footer navigation block Found only after scrolling to the end Moderate, arrives after the point of need Wide but shallow link area Too late for a visitor who has already lost the thread
Fixed bottom bar with a home tab Always within thumb reach High once the pattern is recognised Full width, 56 px tall Covers content and needs careful spacing on small screens

A practical checklist for microsite owners

One change worth making this week

The quickest way to see whether the control works is to stop theorising and open the page on a mid-range handset with mobile data, then scroll to the second screen and tap the home link from there. The test is unforgiving and simple: does it land on the opening screen within a second, does the label read clearly at arm's length, and does nothing else on the page look like a return link? Write down what happens, adjust the label or placement if the answer is no, and repeat the same tap on a train, in bright sun, and on a regional connection before the week is out.