Homepage mistakes that quietly kill enquiries

A homepage fails when a first-time visitor cannot quickly understand four things: what you offer, whether it is relevant to them, why they should trust you and what they should do next.

The page can still look polished. It can contain accurate information, impressive animation and a carefully written company history. Yet if visitors have to interpret vague claims, compare too many options or search for evidence, the homepage quietly adds work to every buying decision.

That does not mean every unclear homepage needs a complete redesign. Some problems are local and can be corrected with sharper copy, hierarchy or form design. Others are symptoms of a deeper structural limitation.

Score your homepage before changing it

Review the page as if you know nothing about the business. Give each question 0, 1 or 2 points: 0 for no, 1 for partly and 2 for clearly.

Area	Question	Warning sign
Offer	Can a visitor explain what you sell?	The headline could describe hundreds of companies
Fit	Is the intended customer or situation clear?	Everyone appears to be the target
Priority	Is one offer or route visibly primary?	Several services and buttons compete equally
Proof	Is credible evidence visible before a major commitment?	Claims appear without examples or specifics
Sequence	Does each section answer the next buying question?	Sections feel like an internal content checklist
Mobile	Does mobile preserve the same meaning and priority?	Important content disappears or becomes awkward
Performance	Does the page load, respond and remain stable?	Slow hero media, delayed taps or jumping content
Contact	Is the next step easy to understand and complete?	Hidden details, excessive fields or unclear feedback

As a working heuristic, 13 to 16 suggests targeted improvements may be enough. Between 8 and 12, test the weak areas before deciding. Below 8, the page may have a structural problem rather than a collection of small copy issues.

This score is not an industry benchmark. A complex consultancy and a local specialist require different levels of explanation. What matters is whether the page supports the real decision the buyer is trying to make.

The five-second test is recall research

The five-second test is often reduced to a slogan: your website has five seconds to convert someone. That is not what the method proves.

A genuine five-second test is a qualitative first-impression exercise. Participants see a page or static image briefly, then answer recall questions. Maze describes it as a way to assess what people remember, what stood out and whether the main message reached them.

Useful questions include:

• What do you think this company offers?
• Who do you think it serves?
• What words, images or claims do you remember?
• What would you expect to happen next?
• What, if anything, felt unclear?

Recruit people who resemble the intended audience. Do not tell them what they are supposed to notice. Look for patterns across responses rather than treating one participant’s wording as a verdict.

Five seconds is the research setup, not a universal deadline for every visitor or purchase. People may explore a credible site for much longer. The test simply removes the extra context that founders and internal teams unconsciously bring to the page.

If participants cannot recall the offer or confuse it with something else, the symptom is poor comprehension. The cause might be a vague headline, competing visual elements, unfamiliar language or a mismatch between copy and imagery. Change the cause, then test again.

Clarity breaks in the hero

A vague hero is the most visible homepage problem, but “rewrite the headline” is not always the full solution.

Headlines such as “Unlock your potential”, “Ideas that move businesses forward” or “Building tomorrow together” express ambition without identifying an offer. A visitor cannot tell whether the company provides strategy, software, recruitment, finance or coaching.

A useful hero normally establishes:

1. The service or product category.
2. The customer, problem or context.
3. A meaningful point of difference.
4. A credible next step.

It does not need to explain the whole business. It needs to make the rest of the page worth reading.

Internal language creates a related problem. Service names shaped by an organisation chart, proprietary framework or creative workshop may make sense to the team but not to a buyer. Visitors search and think in terms such as “custom website”, “employment law advice” or “B2B lead generation”, not necessarily your internal package names.

The small fix is to make the headline concrete, add a plain-language supporting sentence and relabel unfamiliar offers. A custom rebuild becomes relevant when the design cannot accommodate a clear message, the navigation reflects outdated business units or every page depends on rigid builder sections that fight the new hierarchy.

Too many offers create equal noise

A homepage can be accurate and still fail because everything receives the same emphasis.

Five service cards, three navigation buttons, two announcement bars and several differently worded calls to action force visitors to compare before they understand. The problem is not the number of links by itself. It is the absence of priority.

Choose the action that best fits a qualified first-time visitor. That may be viewing relevant work, understanding a core service, booking an introduction or starting an enquiry. Secondary routes can remain available without looking equally important.

Calls to action should also describe distinct outcomes. “Learn more”, “Discover”, “Get started” and “Let’s talk” placed together do not create meaningful choice. Labels such as “View website projects” and “Discuss your website” tell people what follows.

The small fix is to establish one primary CTA style and reduce duplicated routes. Consider rebuilding when the business has changed direction, the current information architecture treats old and new offers equally, or the component system cannot express visual priority consistently.

This principle also clarifies the homepage versus landing-page question. A focused campaign often benefits from a dedicated landing page because its audience, promise and next step are narrow. But not every advertisement should avoid the homepage. Branded search, broad awareness or an offer that genuinely matches the homepage may send visitors there successfully. Destination choice should follow message match and visitor intent, not a blanket rule.

Proof must arrive before the doubt

Many homepages make ambitious claims at the top and postpone evidence until the footer. Others use logo strips, generic testimonials or isolated statistics without enough context to evaluate them.

Trust proof is useful when it helps a visitor answer a real question:

• Have you solved a problem like mine?
• What does your work actually look like?
• Who will deliver it?
• Is your process credible?
• Are the claims specific and verifiable?

Proof can include relevant work, named credentials, process detail, product demonstrations, independently verifiable reviews or clear examples of thinking. The right form depends on the business. A young specialist should not imitate the proof pattern of a global consultancy.

Place evidence close to the claim it supports. If you say your websites are custom, show or explain what that changes. If you describe a specialist process, make its stages understandable. Do not make visitors collect fragments from several pages before they can assess credibility.

Weak proof is the symptom. The cause may be poor placement, generic presentation or a genuine lack of publishable evidence. Design cannot manufacture credibility. A small fix can move and contextualise existing proof. A rebuild is justified when case studies, service pages and homepage claims need a shared content structure that the current site cannot support.

Sections need a decision sequence

A homepage is not a storage page for everything the company wants to mention. Its sections should follow the visitor’s decision.

A practical sequence for many service businesses is:

1. What is this and is it relevant?
2. What problem does it solve?
3. What exactly is offered?
4. Why this approach or provider?
5. What evidence supports that?
6. What happens if I enquire?
7. What should I do next?

The exact order can vary. A visually led studio may show work earlier. A regulated service may need credentials sooner. The test is whether each section earns the next one.

Symptoms of a broken sequence include repeated introductions, service grids without context, an “about us” section before the visitor understands the offer and a contact CTA before any risk has been reduced.

The small fix is to reorder, remove or combine sections. A rebuild becomes more sensible when pages are assembled from disconnected templates, the content model forces repetition or important buyer questions have no suitable component.

Mobile is not compressed desktop

A responsive homepage should preserve the same primary content and meaning across devices. Google recommends responsive design and says the mobile version should contain equivalent primary content, clear headings and relevant metadata because its systems use the mobile version for indexing.

Equivalence does not mean an identical layout. Mobile can use a different arrangement, shorter navigation, appropriately sized media and progressive disclosure where it remains accessible. It should not hide the proof, explanation or next step that makes the desktop version persuasive.

Common mobile failures include:

• A hero headline wrapping into an unreadable block.
• Important work or proof removed to shorten the page.
• Tap targets placed too closely together.
• Sticky interface elements obscuring content.
• Desktop-sized images downloaded for small screens.
• Forms that trigger awkward zooming or keyboard overlap.
• Horizontal carousels with no clear controls or alternative.

The cause is often that mobile was reviewed after desktop approval rather than designed alongside it. A small fix can correct spacing, typography, media sizing and controls. Rebuild when the component system relies on fixed dimensions, duplicated mobile content or interactions that do not translate to touch and keyboard use.

Performance and forms are part of persuasion

A clear proposition still loses force if the hero arrives late, buttons hesitate or content shifts while someone tries to read it.

Core Web Vitals cover three aspects of user experience:

• Largest Contentful Paint (LCP): loading performance, with a good threshold of 2.5 seconds or less.
• Interaction to Next Paint (INP): responsiveness, with a good threshold of 200 milliseconds or less.
• Cumulative Layout Shift (CLS): visual stability, with a good threshold of 0.1 or less.

These targets should be assessed at the 75th percentile of page loads, segmented between mobile and desktop. Field data reflects real devices, networks and interactions. Lab tools remain useful for diagnosis and catching regressions, but they do not replace field measurement.

Core Web Vitals are UX metrics, not conversion guarantees. Passing them does not make an unclear offer persuasive. Failing them can still introduce delay, instability and frustration at commercially important moments.

Common causes include oversized hero media, unnecessary third-party scripts, poorly loaded fonts, excessive client-side JavaScript and images without reserved dimensions. Small optimisations can resolve isolated issues. Rebuilding may be more efficient when a builder outputs heavy markup, essential templates depend on layered plugins or every new edit reintroduces performance problems.

Contact friction deserves the same scrutiny. Ask only for information needed to handle the enquiry. W3C WAI guidance recommends identifiable form controls, clear instructions, useful validation and notifications for errors and successful completion:

• Keep visible labels instead of relying only on placeholders.
• Explain required formats before submission.
• Identify the affected field and how to correct an error.
• Preserve entered information when validation fails.
• Confirm clearly when the message has been sent.
• Provide a workable alternative contact route when appropriate.

The small fix is often better labels, fewer fields and clearer feedback. Rebuild the interaction when the form is unreliable, inaccessible, difficult to maintain or disconnected from the actual enquiry process.

Run this 15-minute self-audit

Set a timer and use a phone as well as a desktop screen.

Minutes 0 to 3: test recall

Show the homepage to someone unfamiliar with the business for five seconds. Hide it and ask what the company offers, who it serves and what they remember. Record their words without correcting them.

Minutes 3 to 6: inspect priority

List every visible offer and CTA in the first two screenfuls. Circle the intended primary action. If several elements compete with it, note what can become secondary or disappear.

Minutes 6 to 9: trace the decision

Write the question answered by each section. If two sections answer the same question, or a section answers none, mark it. Check whether proof appears near the claim it supports.

Minutes 9 to 12: use mobile

Load the page on a real phone. Read the hero, open the navigation, use interactive elements and begin the form. Look for hidden content, unstable layouts, intrusive overlays and difficult controls.

Minutes 12 to 15: check evidence

Review PageSpeed Insights or your field monitoring, separating mobile and desktop data. Then submit the contact form with an intentional error and a valid entry. Check labels, instructions, error handling and success feedback.

You will finish with observations, not a redesign brief. Group them by cause before choosing solutions.

Refresh or commission a custom rebuild?

Choose a focused refresh when the offer and audience remain stable, the site structure supports the buyer journey, useful proof already exists and the underlying system can handle copy, hierarchy, accessibility and performance improvements cleanly.

Choose a custom rebuild when the business has materially changed, visitors cannot navigate the offer, mobile and desktop require separate workarounds, performance problems return after optimisation or the builder structure constrains every meaningful improvement.

Also consider the cost of continued accommodation. A builder project is not automatically the economical option once template workarounds, plugin dependencies, redesign compromises and maintenance are included. A lean custom website can sometimes cost less while producing a cleaner system, but the right choice depends on scope and requirements.

The decision in one sentence: refresh when the foundation supports the message, rebuild when the foundation is the reason the message cannot work.