ChatGPT
Claude
Perplexity
Gemini
GrokHow poor UX silently drains your applicant pipeline
Nine out of ten prospective students leave your website having never made contact. That is not a headline designed to alarm — it is a measured finding. 91 % of visitors to a school's website leave without ever making contact (Source: Skolbot funnel analysis, 30 schools, 2025–2026). They read your programme pages, scroll through your fee tables, and then disappear — silently, with no enquiry submitted and no open day booked.
The instinctive explanation is a marketing problem: not enough traffic, wrong audience, weak campaign copy. The data tells a different story. The drop-off is not predominantly at the top of the funnel; it happens at the moment of conversion — when a prospective student reaches for a form, tries to register for an open day on a mobile phone, or waits for a page to load while sitting on the train. These are UX failures, not marketing failures, and they are fixable.
The scale of the problem is made vivid by session-level data. Prospects visit an average of 4.7 pages before submitting their first question, with the highest-visited pages being programmes (92 %), fees and funding (78 %), and admissions (71 %) (Source: analytics and session replay, 15,000 prospect journeys, 2025–2026). That means a prospective student is already deeply interested in your institution before they hit a broken form or a registration flow that has not been tested on a smartphone. The investment in reaching them — SEO, paid search, open day marketing — is wasted in the final ten seconds of the journey.
The timing compounds the problem. 67 % of prospect activity occurs outside business hours, with a peak on Sunday evenings between 8 pm and 9 pm (Source: Skolbot interaction logs, 200,000 sessions, Oct 2025–Feb 2026). When a prospective student tries to register for an open day on a Sunday night and encounters a broken date-picker or a form that requires a desktop browser, there is no admissions team member available to recover the situation. The lead is lost.
This checklist addresses the three highest-impact UX areas: mobile experience, enquiry forms, and open day registration. For each, we provide a prioritised list of fixes with effort ratings, so your web team knows where to start.
For context on what conversion rates to aim for, see our school website conversion rate benchmarks and the companion pages that convert analysis.
Mobile UX checklist
More than 60 % of visits to UK university and college websites now originate from mobile devices. Yet the majority of admission-critical pages — programme finders, fee calculators, enquiry forms — were designed on a desktop and tested on a desktop. The result is a mobile experience that is technically functional but practically unusable.
Work through the following checks on your own device before reading any further.
Load speed: <3 s on a 4G connection
Run your programme pages and your main enquiry form through Google PageSpeed Insights. A load time above 3 seconds on mobile correlates with a bounce rate increase of over 30 %. Image carousels, unminified JavaScript bundles, and third-party tag stacks are the most common culprits on school sites. Target a Largest Contentful Paint (LCP) of <2.5 s and a Cumulative Layout Shift (CLS) score of <0.1.
Tap targets: minimum 44 × 44 px
The WCAG 2.1 guideline 2.5.5 recommends a minimum touch target of 44 × 44 CSS pixels. Navigation links, form submission buttons, and date-picker controls on school sites routinely fall below this threshold. A prospective student trying to select a programme on a phone in a commuter carriage should not need to zoom in.
Forms on mobile: keyboard type and field order
Every input field on a mobile form should trigger the correct keyboard. An email field must trigger the email keyboard (with the @ symbol prominent); a phone number field must trigger the numeric keyboard. This is set via the inputmode and type attributes in HTML and takes thirty seconds per field to implement. Yet it is missing on the majority of school enquiry forms audited in the Skolbot benchmark.
Field order matters too. Place the fields a prospect is most likely to complete first (name, email) at the top, and defer optional fields (preferred start term, how did you hear about us) to the end or remove them entirely from the mobile layout.
Viewport and zoom lock
Ensure your pages do not disable pinch-to-zoom via user-scalable=no in the viewport meta tag. The ICO and QAA accessibility expectations, aligned with the Public Sector Bodies Accessibility Regulations 2018, require that users can resize content. Zoom lock also triggers automatic WCAG 1.4.4 failures.
Test on real devices, not just browser dev tools
Browser device emulation does not reproduce real-world touch lag, font rendering, or the behaviour of autocomplete on iOS Safari. Test your open day registration form on an iPhone using Safari and on an Android device using Chrome before every major UCAS cycle deadline.
For a deeper treatment of mobile-first enrolment design, see our mobile-first enrolment UX checklist.
Enquiry form checklist
The enquiry form is the primary conversion mechanism on most school websites. It is also, in the majority of cases, the page that receives the least design attention. The following items cover field count, error handling, and multi-step architecture.
Field count: aim for five or fewer
Each additional required field reduces form completion rates. Internal analysis of enquiry forms across 30 institutions shows that forms with more than seven required fields have a completion rate of 23 %; forms with five or fewer fields achieve 51 %. If your form asks for date of birth, current institution, predicted A-level grades, and UCAS personal ID in the same flow as name and email, strip it back to the essentials and collect supplementary data via a follow-up email sequence.
Inline validation, not end-of-form error lists
Flagging all errors after a prospect clicks "Submit" is the most damaging UX pattern in form design. A prospective student who has spent two minutes completing your form and then receives a list of seven errors at the bottom of the page will, in most cases, abandon. Use inline validation to surface errors field by field, in real time, with clear instructional copy ("Please enter a valid UK mobile number, e.g. 07700 900000") rather than error codes.
Progress indicators on multi-step forms
If your enquiry or application form spans multiple steps — a common pattern for UCAS-aligned enquiry flows — display a progress indicator. "Step 2 of 4" is sufficient. Without it, prospects do not know how much further they have to go and abandon mid-flow. Session replay data from Jisc's digital experience insights survey consistently identifies unknown form length as a top-three cause of drop-off on HE websites.
Confirmation that does useful work
The confirmation message after form submission is almost universally wasted. "Thank you, we will be in touch" tells the prospect nothing. Replace it with: the name of the person who will reply, an expected response time, a link to the most relevant next step (e.g., the open day calendar), and — where consented — a calendar invite file for any upcoming open days they expressed interest in.
GDPR and ICO compliance copy
Under UK GDPR, the lawful basis for processing enquiry data must be stated at the point of collection. A generic "we take your privacy seriously" line does not satisfy this requirement. The ICO's guidance on consent and legitimate interests requires you to specify what data you collect, how it will be used, and how long it will be retained. This copy must appear adjacent to the form fields that collect personal data, not buried in a linked privacy policy.
No CAPTCHA on the main enquiry form
Invisible CAPTCHA (reCAPTCHA v3) is acceptable. Visible image-based CAPTCHA challenges (select all the traffic lights) on a mobile device, in an already-hesitant prospect journey, produce measurable form abandonment. If spam is a concern, use honeypot fields and rate limiting at the server level.
Open day registration UX
Open days are the single highest-conversion touchpoint in the UK school recruitment cycle. A prospective student who attends an open day is significantly more likely to make a UCAS application than one who does not. The quality of the registration UX therefore has a direct, traceable impact on application volumes.
The UCAS open day listings reach most UK universities' prospective students. Many prospective students discover your open day through UCAS rather than through your own website — which means the first impression of your registration flow is often the first impression of your institution's digital competence.
Single-page registration: maximum three fields
An open day registration form should ask for name, email, and the session or date the prospect wishes to attend. Nothing more. Additional questions — parking requirements, dietary needs, accessibility requirements — belong in a confirmation email, not in the registration barrier. Every additional field at the point of registration reduces conversion.
Date and session selection: use native controls on mobile
Date-picker widgets built in JavaScript frequently fail on iOS Safari and older Android browsers. Use the HTML5 <input type="date"> element as a baseline and layer a custom picker on top only if the native control is insufficient for your use case. If you offer multiple open day sessions on the same date, present them as a list of radio buttons rather than a dropdown — radio buttons are easier to tap accurately on mobile.
Automated confirmation and calendar integration
Every open day registration must trigger an immediate automated confirmation email containing a .ics calendar file. Prospects who receive a calendar invite have measurably higher attendance rates than those who receive only a text confirmation. Set up a reminder sequence: seven days before and 24 hours before the event.
Waitlist and cancellation flows
If a session is full, show a waitlist option rather than a dead end. "This session is full — join the waitlist and we will notify you if a space becomes available" retains the prospect. A cancellation link in every confirmation email reduces no-shows and allows real-time release of spaces to the waitlist.
Accessibility: WCAG 2.1 AA compliance
The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 require UK public universities to meet WCAG 2.1 Level AA. For private providers regulated by the Office for Students (OfS), accessibility is increasingly embedded in quality and standards expectations. At minimum, your open day registration page must be operable via keyboard alone, have sufficient colour contrast (4.5:1 for normal text), and include descriptive alt text on all non-decorative images.
Out-of-hours availability
Because 67 % of prospect activity occurs outside business hours (Source: Skolbot interaction logs, 200,000 sessions, Oct 2025–Feb 2026), your open day registration system must operate fully autonomously outside office hours. Manual confirmation workflows that require a staff member to approve registrations before a confirmation is sent are incompatible with the reality of when your prospective students are online.
Priority fix matrix
The table below summarises the UX issues covered in this checklist, ranked by impact on conversion and rated by implementation effort. Use it to triage your web team's backlog.
| UX Issue | Impact on Conversion | Implementation Effort | Fix First? |
|---|---|---|---|
| Form load time >3 s on mobile | Very high — direct bounce driver | Medium (image optimisation, JS audit) | Yes |
| More than 7 required fields on enquiry form | High — 51 % vs 23 % completion rate | Low (remove fields) | Yes |
| No inline form validation | High — end-of-form errors cause abandonment | Medium (JS validation library) | Yes |
| Open day registration >3 fields | High — registration barrier | Low (reduce fields) | Yes |
| Tap targets below 44 px | Medium — affects mobile users specifically | Low (CSS padding adjustment) | Yes |
| Broken date-picker on iOS Safari | Medium — blocks open day registration | Medium (switch to <input type="date">) | Yes |
| No calendar invite in confirmation email | Medium — reduces attendance rate | Low (add .ics attachment) | Yes |
| Visible CAPTCHA on enquiry form | Medium — mobile abandonment | Low (switch to reCAPTCHA v3) | Yes |
| Generic "thank you" confirmation page | Medium — missed re-engagement opportunity | Low (add next-step links) | No — quick win |
| No progress indicator on multi-step form | Medium — unknown length causes drop-off | Low (add step counter) | No — quick win |
Zoom lock (user-scalable=no) | Low-Medium — accessibility and legal risk | Very low (remove one attribute) | Yes |
| GDPR consent copy missing from form | Low on conversion, high on legal risk | Low (add inline copy) | Yes |
| No open day waitlist | Low-Medium — retains otherwise lost leads | Medium (waitlist logic) | No — second wave |
| Out-of-hours registration requires manual approval | High — affects 67 % of registrations | High (automate confirmation flow) | Yes |
How an AI chatbot addresses residual UX gaps
Even a fully optimised website will not recover all lost prospects. Some drop-off is structural: a prospective student has a highly specific question that no static page answers, or they reach the site at 11 pm and want an immediate conversation, not a form.
An AI chatbot addresses these cases directly. Sites with an AI chatbot reduce bounce rate from 68 % to 41 % — a 39.7 % relative reduction — and pages per session rise from 1.8 to 3.4, with session duration increasing from 1 m 45 s to 4 m 12 s (Source: A/B test on 22 partner school sites, Sept–Dec 2025). The chatbot does not replace good UX; it catches the prospects that good UX alone cannot retain.
For schools where the prospect-contact gap is the primary concern, see also: school landing page conversion and school website conversion rate benchmarks.
Test Skolbot on your school in 30 secondsFAQ
How many fields should a school enquiry form have?
Aim for five or fewer required fields. The core set — first name, last name, email address, programme of interest, and a free-text message — is sufficient to initiate a meaningful follow-up conversation. Every additional required field reduces completion rates. Optional fields (phone number, preferred contact time) can be included but must be clearly marked as optional and should not appear before the core fields.
What is the minimum page load time I should target for mobile?
Target a Largest Contentful Paint of <2.5 s and a total page load time of <3 s on a 4G connection. Use Google PageSpeed Insights to measure your current performance. The most common causes of slow load times on school websites are uncompressed hero images, multiple third-party tag scripts (CRM pixels, analytics, chat widgets), and render-blocking JavaScript.
Do UK schools have a legal obligation to make their websites accessible?
Public sector bodies — including most universities — are required to meet WCAG 2.1 Level AA under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. Private providers regulated by the Office for Students (OfS) are subject to the OfS's quality and standards conditions, which increasingly reference accessibility. The ICO separately enforces UK GDPR requirements that affect data collection forms. Non-compliance carries both reputational and legal risk.
Why does open day registration UX matter if we already promote open days heavily?
Promotion drives traffic to your registration page; UX determines what proportion of that traffic converts. A typical school invests significantly in open day marketing — email campaigns, social media, UCAS listing — but a registration form that is cumbersome on mobile will waste a large share of that investment. Because most registrations happen on mobile and outside business hours, the registration flow must work perfectly without any human intervention.
How does an AI chatbot complement UX improvements rather than replace them?
UX improvements reduce the structural friction that prevents motivated prospects from converting. A chatbot addresses a different problem: the prospective student who has consumed your content and is still undecided, or who has a specific question that no static page answers. The two interventions are complementary. Schools that fix their UX first and then deploy a chatbot see the largest combined gains — because the chatbot's conversion uplift is measured against a baseline of engaged, non-bounced visitors rather than a high-friction, high-bounce population.
What should the confirmation page say after an open day registration?
At minimum: the name of the event, the date and time, the venue address with a Google Maps link, a .ics calendar download, and a contact email address for queries. Optionally, include a link to prepare for the day (virtual campus tour, programme highlights video) and social sharing prompts. The confirmation email should be sent within 60 seconds of registration and should contain all the same information.
