Digital
5 min read
The homepage doesn’t need to explain everything
Homepages are asked to serve every audience at once. The ones that perform usually do less — orienting quickly, then getting out of the way.
The pressure to cover everything
A homepage is the only page every team believes belongs to them.
Sales wants the proof points. Product wants the new release. Recruitment wants the culture section. Leadership wants the positioning statement. All of it is legitimate, and all of it lands on the same page.
The result is a homepage built by negotiation rather than by intent — long, evenly weighted, and organised around internal structure instead of what a visitor is trying to do.
It is worth remembering that most visitors do not read a homepage. They scan it long enough to decide whether they are in the right place, then leave for somewhere more specific.
What it is actually for
The homepage is a junction, not a destination.
Its job is orientation. Who this is, whether it is relevant, and where to go next. Three things, answered quickly, in roughly that order.
Everything beyond that is better handled by pages built for a single purpose, where the content can be as detailed as the audience needs without competing for space.
This is also how people actually arrive. A meaningful share of traffic enters through search, a shared link or a campaign, landing deep in the site and never seeing the homepage at all.
Designing the homepage as if it were the only entrance overweights it. Designing it as a junction makes the whole site work harder.
The cost of over-explaining
Length is not thoroughness — past a point it reads as uncertainty.
A page that explains everything signals that nothing could be left out, which tends to read as a lack of confidence rather than a wealth of substance.
It also flattens hierarchy. When every section carries the same weight, visitors cannot tell what matters, and the page stops making an argument at all.
Most over-long homepages are compensating for an unresolved question further upstream. When a company cannot say what it does in a sentence, the page ends up trying every version at once.
Fixing that is not a design task. But the homepage is where the absence becomes impossible to ignore, which is often what finally forces the decision.
The bigger picture
“Nothing is being cut. It is being given somewhere it can actually be read.”
Editing a homepage is mostly an organisational exercise.
The design decisions are rarely the difficult part. Deciding whose content comes off the page is, because it means telling a team their priority is being handled somewhere else.
That conversation goes better when it is framed around the visitor’s sequence rather than internal hierarchy — not whose section matters, but what someone needs to know before they need to know anything else.
It also helps to make the alternative concrete. Content is not being deleted; it is moving to a page where it can be more thorough than the homepage would ever allow.
Teams that get this right review the homepage on a schedule and treat removal as routine maintenance, rather than as a negotiation reopened every time something new ships.
Looking ahead
Judge the homepage on what happens next, not on how much it contains.
The useful measure is whether visitors move, and whether they move somewhere relevant. A short page that routes people accurately is doing its job better than a long one that holds them without direction.
That reframing also settles most internal arguments, because it replaces an aesthetic debate with a question the analytics can answer.
