What makes a good WiFi landing page
The WiFi login is the first screen of your venue a guest sees on their own phone, often with one bar of patience and a coffee going cold. A good one gets them online in seconds, asks an honest question, and leaves them somewhere useful.
It has to work before the guest is online
This is the part most designs forget. When a phone joins the guest network, it is not on the internet yet. The controller holds it in a waiting state and lets it reach only the hosts on a short allow list, often called the walled garden or pre authentication list. The login page has to load, in full, from those hosts alone.
A background video served from a media host, a web font from a font service, a chat widget, an analytics tag: each one asks for a host the phone cannot reach yet. The page waits, renders half styled, or never finishes. The guest sees a spinner and walks to the counter to ask for the password.
What to keep off the page
- Video backgrounds and large photos. A logo and one modest image are plenty.
- Anything loaded from a third party host before authorisation: fonts, scripts, embeds, pixels.
- Pop ups and banners that cover the button on a small screen.
VoqadoWiFi keeps its walled garden to two entries, www.voqadowifi.com and voqadowifi.com. Logos and background images are served through the same origin, and brand fonts load without blocking, so the page falls back to the phone’s own font if they are not reachable. The full list and the reasons are on the walled garden domains page.
One clear action
The guest came to get online. The page should have one obvious thing to press, and it should say what happens: “Connect to WiFi” beats “Submit” and beats “Continue”. Secondary links, such as the WiFi terms and the privacy notice, belong in small text near the checkbox, not as rival buttons.
Think of the barista with a queue of eight. Every guest who cannot work out the login becomes a question at the till. A page with one button is a page staff never have to explain.
Few fields, each with a reason
Every field costs sign ins. Before adding one, name the message that will use it.
| Field | Keep it when | Leave it off when |
|---|---|---|
| Always: it is the guest list | Never | |
| First name | You will greet guests by name | Emails will be generic anyway |
| Phone | You have a real use for it | You only want it just in case |
| Birthday (month and day) | A birthday message is planned | Nobody will send one |
| Marketing consent | Always, separate and unticked | Never bundle it with the terms |
The VoqadoWiFi login asks for an email address and a first name, with last name, phone and birthday as optional extras, and every label can be renamed per venue. There is no social login: guests sign in with an email address, so the page never depends on a social network being reachable.
Consent wording guests can trust
Two boxes, two decisions. The WiFi terms box is the condition for getting online. The marketing box is optional, starts unticked, and says in plain words what the guest will get and from whom. Compare “Email me offers and news from Harbour Café” with “I agree to receive communications from partners”. The first is a choice a guest can make in a second. The second is a reason to leave.
If you will send a one off message about the visit, such as a review request, say so near the button. The VoqadoWiFi login shows a short service notice for exactly that. The rules behind all this are summarised in guest WiFi and privacy rules.
Readable by everyone
Contrast
Light grey text on a photo looks elegant on a monitor and disappears on a phone in the afternoon sun on a terrace. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text (success criterion 1.4.3). Put text on a solid card, not straight on the image.
Tap targets
The enhanced WCAG criterion asks for pointer targets of at least 44 by 44 CSS pixels (2.5.5). Make the checkboxes and their labels one tappable area, and the main button wide and tall. The VoqadoWiFi connect button is at least 58 pixels high.
Labels, not just placeholders
A field needs a label that stays visible while the guest types (3.3.2). Placeholder text vanishes on the first keystroke, and with it the reminder of what the field was. Mark optional fields as optional. The VoqadoWiFi login uses visible labels and shows “(optional)” beside the fields a guest can skip.
Language
Write the button, the labels and the consent line in the language most of your guests read. In Willemstad or Philipsburg that may mean English for a hotel lobby and Dutch or Papiamentu for a neighbourhood bakery. Renaming labels per venue makes that a setting, not a redesign.
What happens after connecting
Once the guest is online, the page has a second chance to be useful. Send them to something that serves the visit they are in the middle of: the menu at a cafe, the spa booking page in a hotel, tonight’s line up at a lounge. In VoqadoWiFi a venue sets that link in the Portal Builder, and it appears on the connected screen.
Returning guests should not meet the same form. Within the auto login period, 30 days by default, a recognised device is let back on without it, and a returning guest sees a welcome back card instead. That card never records consent again, so the original choice stays the one on file.
What to avoid
- Forced social follows. Making a guest like a page or follow an account to get online turns a courtesy into a toll, and the follow is worth little.
- Pre ticked boxes. They do not create valid consent under the GDPR and they sour the first impression.
- Ads. Advertising on the login slows the page, usually needs extra hosts in the walled garden, and puts someone else’s brand on your door.
- Long legal text on the page itself. Link the terms and privacy notice; do not paste them in.
- Surveys before access. Ask about the visit after it, not before the guest has even sat down.
Want to see these choices on real layouts? The splash page examples are rendered from the VoqadoWiFi builder, and the demo lets you build one for your own venue.
Questions
Why does my WiFi login load slowly or look broken?
How many fields should a WiFi login ask for?
Should the marketing checkbox be ticked by default?
What should guests see after they connect?
Do regulars have to fill in the form every time?
Keep reading
Product behaviour described here is the platform default; most settings can be changed per location.
Build a light, honest WiFi login free
One location and 500 guest logins a month on the Starter plan, no card. Works with the Omada or UniFi network you already have.