University Website UX: Stop Losing Applicants to Poor Design

The UX drain your admissions team cannot see

91% of visitors to an Australian university website leave without ever making an enquiry (Source: Skolbot funnel analysis, 30 institutions, 2025–2026 cohort). That figure is not a content problem, a brand problem, or a budget problem. It is, in the vast majority of cases, a user experience problem. Broken forms on mobile, open day registration spread across five screens, fee pages buried three clicks deep, enquiry buttons that scroll off screen — these are the silent conversion killers that no Google Analytics dashboard flags automatically.

The stakes are measurable. Prospective students visit an average of 4.7 pages before asking their first question, with program pages visited in 92% of journeys, fee pages in 78%, and admissions pages in 71% (Source: Skolbot analytics, 15,000 prospect journeys, 2025–2026). Each of those pages is an opportunity to retain or lose a prospect. And because 67% of that browsing happens outside business hours, peaking on Sunday evenings between 8pm and 9pm AEST (Source: Skolbot interaction logs, 200,000 sessions, Oct 2025 – Feb 2026), there is no admissions officer available to cover the gap.

This article gives you an actionable checklist — mobile UX, enquiry forms, open day registration — to identify and fix the UX issues that are quietly costing your institution applications. For the broader conversion context, see our analysis of university website conversion rate benchmarks.

Section 1: Mobile UX checklist

More than 70% of Gen Z prospects first encounter a university website on a smartphone. ATAR results, UAC preference periods, and scholarship deadlines are all researched on mobile — often late at night with patchy connectivity. If your site is not genuinely mobile-first, you are not losing a few enquiries: you are losing the majority of your prospective cohort.

The Australian Web Accessibility Standard (aligned with WCAG 2.1 AA) applies to all Australian Government websites and is strongly expected of institutions operating under TEQSA registration. Accessibility and mobile UX are not separate issues — a site that fails WCAG 2.1 AA on touch targets and colour contrast also fails the average smartphone user.

Run Google PageSpeed Insights on your program pages and your homepage. A mobile score below 70 will cost you both organic ranking and user retention.

Mobile UX checklist — tick each item:

• Core Web Vitals pass on mobile: Largest Contentful Paint < 2.5 s, First Input Delay < 100 ms, Cumulative Layout Shift < 0.1. Test on PageSpeed Insights for each high-traffic page.
• Touch targets meet WCAG 2.1 AA minimum: All buttons, links, and form fields are at least 44×44px. Program enquiry buttons are especially critical — if they are too small, Year 12 students tapping quickly will miss them.
• No horizontal scroll on any program or fees page: Test at 360px viewport width, which covers the most common Android screen sizes in Australia.
• Navigation menu is thumb-reachable: Primary navigation and the main CTA (enquire, apply, register for open day) sit within the bottom 60% of the screen on mobile — the thumb zone.
• PDF prospectuses and course guides have a mobile-optimised HTML equivalent: PDFs are inaccessible on mobile and excluded from Google indexing. Every PDF course guide should have a corresponding HTML page.
• HECS-HELP and fee information is not locked behind a login or a form: Fee transparency is a decisive factor for domestic prospects. If a student cannot see their Commonwealth Supported Place contribution band without submitting an enquiry form, they will go to the Good Universities Guide or a competitor's site.
• Font size is at least 16px for body text: Anything smaller forces users to pinch-to-zoom, which is a strong signal of imminent abandonment.
• Images use next-gen formats (WebP, AVIF) and are lazy-loaded: Campus photography is essential for conversion, but unoptimised hero images are among the top causes of poor LCP scores.

For a full deep-dive on mobile enrolment journeys, see our dedicated guide to mobile-first enrolment UX.

Section 2: Enquiry form checklist

The enquiry form is the primary conversion mechanism on most university websites. It is also one of the most commonly neglected. Common failure modes in the Australian context include: requiring UAC applicant numbers before a student even knows their ATAR, presenting 15 mandatory fields for a simple "send me a course guide" action, and timing out without saving progress on mobile.

Under the Privacy Act 1988 and the Australian Privacy Principles (APPs), every enquiry form collecting personal information must display a collection notice at or before the point of collection (APP 5). This notice must state: who is collecting, what is being collected, the primary purpose, whether disclosure to third parties is likely, and how to access the institution's privacy policy. This is not optional. The OAIC can investigate complaints about inadequate privacy notices without a data breach having occurred.

Enquiry form checklist — tick each item:

• Field count is < 5 for a first-touch enquiry: Name, email, program of interest, and one optional field (e.g., study start date) is sufficient for a top-of-funnel enquiry. Every additional mandatory field reduces submission rates.
• APP 5 collection notice is visible at the point of submission: Not in the footer, not accessible only via a linked policy page — a brief, plain-English notice immediately above or below the submit button.
• The form is a single HTML form, not a multi-step process with unsaved state: On mobile, if the user navigates away mid-form and loses their input, they will not return.
• Autocomplete attributes are set correctly: autocomplete="given-name", autocomplete="email", etc. This is a WCAG 2.1 AA requirement (Success Criterion 1.3.5) and dramatically improves completion rates on mobile.
• Error messages are inline and specific: "This field is required" next to the email field is better than a generic banner at the top of the page. Prospects abandoning a form due to unclear errors are a direct, measurable loss.
• The submit button is clearly labelled and not disabled by default: Avoid "Submit" as button text — "Send my enquiry" or "Get course information" are more legible and reduce hesitation.
• Confirmation is immediate and sets expectations: After submission, the confirmation page or message should state when the prospect will receive a response. Industry best practice is within 24 hours; Skolbot mystery shopping data across 80 institutions found an average of 47 hours for email and 72 hours for form enquiries.
• HECS-HELP and FEE-HELP eligibility is referenced in the program enquiry flow: Domestic prospects want to know upfront whether a program is Commonwealth-supported. Including this information in the form confirmation reduces the most common follow-up question.
• Forms work without JavaScript for accessibility: Progressive enhancement ensures the form submits even in degraded connectivity — relevant for regional and rural students on slower networks.

A note on data minimisation: the APPs require that personal information is reasonably necessary for the stated purpose (APP 3). Asking for a student's date of birth, phone number, and school name at the enquiry stage is difficult to justify under APP 3, unless the program has specific entry-age requirements.

Section 3: Open day sign-up UX

Open days remain the single highest-converting touchpoint in the Australian enrolment journey. A prospect who attends an open day is substantially more likely to submit a UAC or VTAC preference, and more likely to accept an offer. The challenge is that the registration experience on most university websites actively discourages sign-up.

Typical failure modes: the open day registration form requires an institutional login, is only accessible from the events page (not from program pages where the prospect's interest is highest), presents dates in a non-standard format, or sends no reminder. Across Skolbot tracking of 4,200 open day registrations across 12 institutions, the no-show rate without any reminder was 52%.

Open day sign-up UX checklist — tick each item:

• Open day registration is accessible from every program page, not only from the events or "visit us" page: A student reading about a Bachelor of Commerce should be able to register for the business faculty open day without leaving that page.
• Registration requires no more than 3 fields: Name, email, and preferred date. Asking for ATAR estimate, year group, or postcode at registration stage reduces conversions and can be gathered post-event.
• The registration form works natively on mobile without redirecting to a third-party platform: Redirect to Eventbrite or an external booking system introduces loading time, an unfamiliar interface, and additional form fields. Every additional step in the registration flow reduces completion.
• Dates and times are presented in local AEST/AEDT time with unambiguous formatting: "Saturday 26 July, 10am–2pm AEST" — not "07/26/26 10:00".
• A calendar invite (.ics file) is sent immediately after registration: This single step meaningfully reduces no-shows by anchoring the event in the prospect's calendar.
• At least two reminders are automated: One 7 days before, one 24 hours before the event. Including the campus address and parking/transport information in the reminder reduces last-minute drop-off.
• A waitlist flow exists for sold-out sessions: Prospects who see "this session is full" without a waitlist option simply do not attend — they do not self-migrate to another date.
• Change of preference period is referenced for Year 12 prospects: For school leavers navigating UAC, VTAC, QTAC, SATAC, or TISC, the open day invite should explicitly note that attending does not commit them to a preference — a barrier that deters cautious Year 12 students from registering.

For a Gen Z-specific perspective on what drives open day attendance decisions, see our article on Gen Z expectations from a university website.

Section 4: The pages that need to convert — and often don't

UX is not only about forms. The pages a prospect visits before ever reaching a form are where conversion is won or lost. As noted, program pages appear in 92% of journeys, fee pages in 78%, and admissions pages in 71%. For a detailed breakdown of page-level conversion, see our companion article on university website pages that convert.

Key issues to check on these pages:

• WAM and ATAR cut-off transparency: Prospects researching a postgraduate program want to see the indicative Weighted Average Mark (WAM) requirement on the program page, not buried in the admissions guide. Prospects researching undergraduate entry want the ATAR cut-off (or ATAR range), not a generic "competitive entry" descriptor.
• Fee pages are not a maze: One page per program type (Commonwealth Supported, full-fee domestic, international) with a clear fee calculator or fee table. If a student needs to call or email to find out what they will pay, most will not bother.
• Admissions page explains the year's cycle clearly: For undergraduate applicants, the UAC/VTAC/QTAC/SATAC/TISC process should be summarised with dates — not merely linked out to the relevant admissions centre's site.

Section 5: Priority fix matrix

Use this table to triage your institution's UX backlog. Impact is rated by estimated effect on enquiry rate; effort reflects typical implementation time for a higher education marketing and web team.

FAQ

Does my university website need to comply with WCAG 2.1 AA?

WCAG 2.1 AA is the standard referenced by the Australian Web Accessibility National Transition Strategy and is expected of institutions receiving Commonwealth funding. Under the Disability Discrimination Act 1992, universities have an obligation not to discriminate on the basis of disability — which extends to inaccessible digital services. TEQSA's Higher Education Standards Framework emphasises student access and participation. A university website that fails WCAG 2.1 AA on colour contrast or keyboard navigation carries both legal exposure and practical exclusion risk.

How many fields should an enquiry form have?

For a first-touch enquiry (e.g., "send me a course guide" or "contact me about this program"), 3–5 fields is the evidence-backed ceiling. Name, email, and program of interest are the minimum viable set. Every additional mandatory field reduces form completion. If your team needs more information (postcode, year of study, citizenship status), collect it in the follow-up interaction — not the initial form.

Why is the open day no-show rate so high, and what actually fixes it?

The no-show rate for university open days without reminders is around 52% (Source: Skolbot tracking, 4,200 registrations, 12 institutions). The most impactful single fix is an automated reminder 24 hours before the event, including the venue address and practical information (parking, public transport). Adding a calendar invite (.ics) at registration and a 7-day reminder reduces no-show rates significantly. The addition of a personalised SMS reminder, where prospects have provided consent, reduces no-shows further.

What are my Privacy Act obligations on a university enquiry form?

Under APP 5 of the Australian Privacy Principles, your institution must notify individuals at or before the time of collection of: the identity and contact details of the collector, the purpose of collection, whether collection is required by law, and how to access your privacy policy. This notice must be on or immediately adjacent to the form — not solely in a linked privacy policy. The OAIC provides guidance and can investigate complaints about inadequate collection notices without a breach having occurred.

An AI chatbot reduced bounce rate from 68% to 41% — is that realistic for an Australian university?

Yes. The bounce rate reduction from 68% to 41% (-39.7%) was measured in an A/B test across 22 Australian and comparable institutions, September–December 2025 (Source: Skolbot A/B test). Average session duration rose from 1 min 45 s to 4 min 12 s in the same test. The mechanism is straightforward: a prospective student who cannot find the answer to their question via the page navigation will ordinarily leave. An AI chatbot trained on the institution's program and fee data surfaces that answer immediately — at 10pm on a Sunday when no admissions officer is available. 67% of prospect activity occurs outside business hours (Source: Skolbot, 200,000 sessions, Oct 2025 – Feb 2026). The chatbot covers that gap.

Your university website is the first campus visit most prospective students will ever take. If the forms break on mobile, if the open day registration takes seven steps, if the fee information requires an enquiry — they will leave before they ever meet your institution. The fixes in this checklist are not redesign projects. Most are configuration changes, content updates, and small template edits that a competent web team can deliver in days.

Related articles: University website pages that convert · Mobile-first enrolment UX checklist · What Gen Z expects from a university website