Gen Z Attention Span: What It Means for Your Course Page

Does a prospective student really decide in eight seconds?

No — and the number itself does not hold up. The "attention span shorter than a goldfish" claim has circulated in marketing decks for a decade, but BBC journalist Simon Maybin traced it in 2017 to an unverifiable source called Statistic Brain, not to Microsoft's actual 2015 Canada consumer report or to any peer-reviewed study (BBC News, "Busting the attention span myth"). Neither Microsoft nor any subsequent researcher has replicated an "eight-second" figure for anything resembling human attention.

That does not mean attention on a course page is unlimited or unmeasurable — it means the real data is less catchy and more useful. Nielsen Norman Group's eyetracking research (120 participants, over 130,000 fixations) found that roughly 57% of viewing time on a page happens above the fold, down from about 80% in 2010 as scrolling behaviour became habitual, and 74% of viewing time still concentrates in the first two screenfuls, roughly the top 2160 pixels (NN/g, "Scrolling and Attention"). For a course page, that means most of the persuasion has to happen before a prospective student touches the trackpad a second time.

This matters more for a school's course page than for most other content, because a school is competing with a dozen other open tabs — UAC, VTAC or QTAC comparison spreadsheets, other institutions, a parent's WhatsApp message asking "so what's the cost". A course page that spends its first screenful on a hero photo and a mission statement has already lost the moment that decides whether the visitor scrolls, clicks through, or closes the tab. Our broader look at what Gen Z expects from a school website covers the behaviour behind that impatience in more depth.

Why prospective students scan a course page instead of reading it

Scanning, not reading, is the default mode for almost every visitor, on every device. NN/g's long-running eyetracking work on the F-shaped reading pattern found that 79% of users scan a page rather than reading word by word, and only 16% read most of the text on an average page (NN/g, "F-Shaped Pattern For Reading Web Content"). A prospective student is not reading your program description as prose — they are hunting for a handful of specific facts and moving on the moment they find, or fail to find, them.

That scanning behaviour follows a predictable shape: a horizontal sweep across the top of the content, a shorter sweep further down, then a vertical scan down the left edge looking for the next heading or number worth stopping for. Dense paragraphs of brand language sit outside that path almost entirely. Headings, bolded figures, and short lists sit directly inside it.

For a course page this has a concrete implication: if tuition or the student contribution amount, the delivery format, and the next intake date are buried in paragraph three, most scanning visitors will never reach them — not because they weren't interested, but because the page asked them to read when they came to scan.

What happens in the first fifteen seconds on a course page

Most visitors decide whether a page is worth their time well before they've engaged with most of it. Chartbeat's analysis of engaged time across a 100,000-page-visit sample over one week found that about 34% of visitors leave within 15 seconds of active engagement, and that landing pages typically hold an audience for only 5 to 30 seconds of engaged time — compared with 60 to 90 seconds for a news article and 3 or more minutes for long-form content (Chartbeat, "Using Engaged Time to Understand Your Audience"). A course page behaves closer to a landing page than to an article: it is consulted for specific facts, not read start to finish.

That short window is not a reason to panic — it's a design constraint. A visitor who leaves after 15 seconds without finding tuition, format, or the next semester start date has not rejected the program; they've rejected the page's failure to answer three or four questions fast enough. The difference matters because the first outcome is unfixable and the second is a layout problem.

What a course page must answer above the fold

Given how little of the page most visitors actually see, everything that decides whether a prospective student keeps scrolling, opens the tertiary application portal, or messages the school has to sit in the first one or two screenfuls. Five things carry most of that weight.

None of these needs a paragraph. A course page that states the current tuition or student contribution figure, names the format, gives one or two concrete graduate outcomes, states the next intake, and offers a single clear next step has covered the ground that 74% of a visitor's attention will actually reach — everything below that point is for the smaller group who scroll further to compare details before applying.

The order matters almost as much as the content. Prospective students triage against a calendar most schools don't control: ATAR results land in mid-December, main offer rounds follow in mid-January for Semester 1 entry, and Semester 1 itself starts in late February or early March, with Semester 2 starting late July. A course page that doesn't surface the relevant intake date near the top forces a visitor who's watching that calendar to go hunting for it, at the exact moment they're most likely to give up and check a competing university's page instead. Mobile makes this tighter still, since most prospective students are scanning on a phone rather than a laptop — our mobile-first enrolment UX checklist and website UX checklist for forms, mobile and open days both dig into what that changes for layout.

When the page still doesn't answer the question

Even a well-built course page can't anticipate every question a prospective student brings to it — a specific pathway from a diploma, a query about credit transfer, a parent asking about accommodation near a particular campus. No amount of above-the-fold optimisation replaces the ability to ask a direct question and get a direct answer.

This is the gap a chatbot on the course page is built to close, not replace. A visitor who scans the page, doesn't find the one detail they came for, and would otherwise close the tab instead gets to ask it directly — without hunting through a course guide PDF or waiting for an enquiry form to be answered days later. Skolbot sits on the course page itself, reads the same information the page shows, and answers the specific question a prospective student didn't find in the first two screenfuls, then routes anything it can't answer to the admissions team.