Articles ·

What applicants need from a university website — and what the law requires

Most applicants compare universities on a phone, often late in the evening. In a few minutes they want to know three things: can I get in, how much will it cost, and what do I do next. Here is what that means for a university website.

A quick test of six large universities

On 17 October 2026 we checked the home pages of six large universities in Ukraine with Google PageSpeed Insights in mobile mode. We do not name them: the point is the typical picture, not blame.

Google speed score on a phone, out of 100
  • University A70
  • University B59
  • University C56
  • University D52
  • University E40
  • University F27

Google’s green zone starts at 90. None of the six got there.

Seconds until the main content appears on a phone
  • Google guideline2.5 s
  • University A8.4 s
  • University C10.2 s
  • University D13.8 s
  • University E14.6 s
  • University B15.1 s
  • University F29.9 s

Scale up to 30 seconds. Even the fastest of the six is three times slower than the guideline.

Google accessibility score, out of 100
  • University B95
  • University F92
  • University C87
  • University D75
  • University E66
  • University A41

Same letters as above. The fastest site (A) has the worst accessibility, and the slowest (F) one of the best: speed and accessibility have to be done together.

It is worth running the same test on your own website: open PageSpeed Insights, paste the address of your home page and of one programme page, and look at the mobile result.

What applicants look for

  1. Entry requirements: grades, tests and language level for each programme.
  2. Fees: per year and for the whole programme, on the programme page rather than in a PDF.
  3. Intakes and deadlines.
  4. What students learn and where graduates work.
  5. Next steps and a contact: who to write to, and how quickly they answer.
  6. For international students: visas, arrival, housing, scholarships.

Most of this usually exists somewhere on the site, but scattered across PDFs and different departments’ pages. Applicants do not put the puzzle together — they go where the answer is clear the first time.

A programme finder instead of a list

The most useful feature for applicants is a programme finder: filter by subject, level and language, compare a few programmes side by side and keep a shortlist to share with family. In our demo for Ukrainian universities, applicants enter their national test scores once and see their chances for every programme.

University website demo (in Ukrainian): a programme finder with test score fields and a list of programmes with admission chances
OLBO closed demo for a fictional Ukrainian university, in Ukrainian because it follows Ukrainian admissions rules; figures are illustrative.

Accessibility is a legal duty

In the EU, the Web Accessibility Directive (2016/2102) requires public sector bodies, including public universities, to make their websites accessible and to publish an accessibility statement. In the UK, the Public Sector Bodies Accessibility Regulations 2018 set the same duty for universities and colleges. The technical standard behind both is EN 301 549, which refers to WCAG 2.1 AA.

In practice that means keyboard navigation, text that can be enlarged without breaking the page, enough contrast, alt text, clear forms and an honest statement of what is not accessible yet. For related reading, see Accessibility fines in Europe.

Analytics for leadership

The same data that feeds programme pages can show leadership how admissions are going: applications by faculty, competition per place, intake against targets. After the cycle, a short summary shows which programmes were under-filled and how demand changed against last year — material for planning the next intake and marketing.

Admissions review for university leadership: where demand rose and fell, programmes at risk of unfilled places and conclusions for the next intake
Analytics for leadership in the OLBO closed demo (English version); fictional university, illustrative figures.

A website the university owns

A common problem is dependence on a single developer: changing a fee or a deadline means writing to them and waiting. A good university website has a CMS with roles, so admissions, faculties and the press office update their own pages, and the rights to the design and content belong to the university.

Where to start this week

  1. Test your home page and one programme page in PageSpeed Insights on mobile.
  2. Follow an applicant’s path from the home page to the fees and entry requirements of one programme. How many clicks, and did you have to open a PDF?
  3. Use the site with a keyboard only and zoom the text to 200%. Does anything disappear or overlap?
  4. Check that your accessibility statement exists, is up to date and says how to report a problem.

This article is general information, not legal advice.

At OLBO we build fast, accessible university websites and run accessibility audits — see websites for universities and colleges, or check your own site with the free Website Checker.

Read also

Is your website holding you back? 5 quick questions

  1. 1. Was your website built or last redesigned more than 4 years ago?
  2. 2. Is it awkward to use on a phone — tiny text, zooming, menus that misbehave?
  3. 3. Have you ever seen «Not secure» or a certificate warning on it?
  4. 4. Do you need a developer just to change a price, a photo or a sentence?
  5. 5. Do fewer enquiries come from the website than you would expect?

Website Checker

Hosting, security, platform age, speed, accessibility, Google and AI visibility — 13 indicators in about a minute, every step shown live. No sign-up. Free: score out of 100, colours, one-line results and an infographic. Full report with fixes: €25.

More about the Website Checker →