What belongs in a five-page business website?

Give every page a clear responsibility.

Page count is a scope boundary, not a measure of usefulness. A focused website should explain the business, establish credible reasons to trust it, reduce uncertainty, and make the next step easy.

Use the structure below as a starting point. A visual trade may need a project gallery instead of a separate process page. A practice may need appointment information. Put the most important customer task first, then decide where the information belongs.

Make the offer understandable.

Home: establish the right fit.

Near the top, explain what you do, who you help, and where you work when location matters. Pair that with one main action. An evocative headline can work, but nearby text must make the offer clear.

Services: answer the questions that determine fit.

Explain what each service includes, who it helps, what may fall outside the scope, and what you need to provide an estimate. Use the language customers use on the phone. Show actual examples where you have permission.

If a service has a substantially different audience or needs a detailed explanation, give it room to grow into its own page. Do not repeat near-identical pages just to fill a location or keyword list.

Show the people and the process.

About: connect experience to customer needs.

A short explanation of your background, standards, and way of working can be more useful than a long biography. Use only current, verifiable credentials. Photographs of the actual team and work help establish who customers will be dealing with.

How It Works: remove avoidable uncertainty.

Explain what happens after an inquiry, how scope and pricing are agreed, what the customer should prepare, and when approvals are needed. Mention payment timing or service boundaries only when those terms are confirmed.

A process should reflect the way the company actually operates. If you cannot consistently respond within a particular time, do not publish that promise. Say what happens next and who is responsible for following up.

Test the whole contact route.

Ask for the information needed to start: a name, a way to reply, and a brief description of the need. A service-area business may also need a town or ZIP code. Avoid requesting sensitive documents, passwords, health information, or payment details in an ordinary inquiry form.

Give every field a visible label. Explain errors in words, preserve the visitor’s entries when something fails, and provide a confirmation that accurately reflects what happened. A second contact option helps when a form is unavailable.

1. Send a clearly labeled test inquiry from a phone.
2. Verify receipt in the destination inbox and check spam.
3. Reply to confirm the customer’s reply address works.
4. Try an invalid email and a missing required field.
5. Check the failure message if delivery is unavailable; it should not falsely claim success.

Assign an actual person to check incoming requests. Good page design cannot compensate for an unmonitored inbox.

Agree on quality before launch.

Ask the builder to demonstrate the site on a small screen, with a keyboard, and at increased text size. You should be able to read the content, see where the keyboard focus is, use the menu, and complete the main action without a mouse.

For normal-sized text, WCAG’s minimum contrast benchmark is 4.5:1; large text has a 3:1 benchmark. Contrast is one check, not a complete accessibility assessment. Images that convey meaning need useful text alternatives, and form labels should remain visible.

Performance is also a customer experience issue. Google’s “good” Core Web Vitals thresholds are a largest-content load time of 2.5 seconds or less, interaction latency of 200 milliseconds or less, and layout shift of 0.1 or less. These are assessed at the 75th percentile of real visits. A new or low-traffic site may not have enough field data; a lab test is a diagnostic, not proof of every visitor’s experience or a ranking guarantee.

You do not need to memorize those measures. Ask whether the main content appears promptly, whether taps respond, and whether content jumps while you are trying to use it.

Keep the first version focused—and the handoff complete.

Prepare approved logo files, current service descriptions, contact details, a few strong real photographs, and your genuine customer questions. Do not delay a useful site for testimonials or statistics you do not have.

Keep a short list of improvements for later. After launch, use actual inquiries and repeated questions to decide what deserves more space. A five-page site succeeds when it helps the customer and remains manageable for the owner.