What Makes a Good Website?

A good website does not have to be flashy, expensive, or built from scratch. It has to do its job for the people who visit it.

Imagine two repair shops. One has an elaborate website with moving graphics but no clear opening hours, hard-to-read text, and a contact form that fails on a phone. The other has a simple website showing services, hours, location, and an easy way to request an appointment. For someone trying to arrange a repair, the simpler site may be the better one.

That is the standard this chapter uses: Can visitors find trustworthy information and complete their task without avoidable obstacles? We will examine seven parts of that answer, and show you how to check your own site without buying an audit.

1. Give the website a clear purpose

Start with one question: Why would someone visit this website? A restaurant visitor may want a menu, hours, or directions. Someone hiring a contractor may want to see the services offered, the area served, and how to get an estimate. A parent looking at a community organization may need event dates and contact information.

Put the most useful answers where people can find them. Use headings that say what they mean, keep important facts current, and make the next step obvious. A visitor should not have to watch an animation or read a sales pitch just to learn whether a business is open on Saturday.

Google recommends content created primarily to help people, rather than material written mainly to manipulate search rankings. It also asks whether readers leave with enough information to achieve their goals.^[1]

Try it: Show your homepage to someone unfamiliar with the business for 15 seconds. Then ask what the business offers and what they should do next. If they cannot tell, simplify the message before adding more features.

2. Make it easy to use, especially on a phone

A website is usable when visitors can move through it, read it, and finish common tasks without guessing. Menus should have clear names. Buttons should explain their actions. Forms should ask only for information actually needed.

A mobile-friendly website should fit a narrow screen without forcing people to scroll sideways, zoom repeatedly, or fight tiny buttons. Important details should remain available on mobile, not disappear because the layout is smaller. Google uses the mobile version of website content for indexing and ranking, so leaving useful content out of the mobile version can also cause search problems.^[2]

Try it: On a real phone, find your hours, send a message, and complete the most important action on the site. Test both portrait and landscape views. Pay attention to awkward taps, unreadable text, overlapping elements, and forms that lose what you typed. Do not rely solely on a desktop browser's mobile preview.

3. Make the site accessible

Accessibility means people with disabilities can use a website, including people who navigate with a keyboard, use a screen reader, need captions, or have difficulty reading low-contrast text.

The Web Content Accessibility Guidelines (WCAG) provide a technical standard organized around four ideas: content should be perceivable, operable, understandable, and robust. WCAG includes testable requirements at levels A, AA, and AAA.^[3]

For a beginner, useful starting points include:

• Make text readable against its background and avoid communicating meaning by color alone.
• Give meaningful images useful text alternatives; decorative images generally do not need descriptions.
• Give forms clear labels and errors that explain how to fix a problem.
• Make interactive controls usable with a keyboard, with a visible focus indicator.
• Provide captions for videos with meaningful speech.^[4]

Try it: Press Tab repeatedly. Can you tell where keyboard focus is? Can you reach the menu, links, and forms without a mouse? Zoom the page to 200%. Do important controls remain usable? W3C publishes free Easy Checks to guide a first review.^[4]

Automated scans, including Lighthouse accessibility scores, can identify some issues but cannot establish that a website is fully accessible. Human judgment and manual testing remain necessary.^[5][6]

A separate legal question is whether a site satisfies applicable accessibility law. WCAG conformance and Americans with Disabilities Act (ADA) obligations are not interchangeable claims. The U.S. Department of Justice provides accessibility guidance, and the applicable requirements depend on the organization and circumstances. Its general guidance links to separate requirements for state and local governments. A passing scanner result is not a legal certification.^[7]

4. Care about performance, not just a score

Performance is what a visitor experiences while a website loads and responds. A page that shows its content promptly, responds to taps, and does not jump around is easier to use than one that makes visitors wait.

Google's Core Web Vitals describe three parts of that experience:

• Largest Contentful Paint (LCP): how quickly the main visible content loads. The recommended good threshold is 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly a page responds after a user interacts with it. The recommended good threshold is 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much visible content unexpectedly moves. The recommended good threshold is 0.1 or less.

These thresholds are assessed using real-user experience at the 75th percentile, assessed separately for mobile and desktop, rather than a single perfect test run.^[8]

Google's free PageSpeed Insights can show simulated test results and, when enough information is available, measurements from actual visitors. These are different kinds of evidence. A new or low-traffic page may not have enough real-user data.^[9]

Try it: Test the homepage and one important interior page on mobile. If the report flags large images, unstable layouts, or slow responses, investigate those concrete problems. Then use the site on an ordinary phone. A score of 100 is not proof that the information is useful, the forms work, or the business is trustworthy.

5. Build trust through safe and responsible operation

A website should be clear about who is behind it and what happens when someone submits information. Publish accurate contact information, honest descriptions of products or services, and policies that match what the business actually does.

Look for HTTPS at the beginning of the address. HTTPS uses Transport Layer Security (TLS) to protect information while it travels between a visitor's browser and the website.^[10] It does not prove that the company is legitimate or that everything behind the website is secure.^[11]

Responsible operation also means keeping site software and accounts maintained, limiting who can change the website, using strong account protection, and keeping recoverable backups when appropriate.^[12] If customers pay online, consider a payment provider that meets PCI DSS requirements for the services it provides, rather than inventing a do-it-yourself system for handling payment card details. Outsourcing still leaves you responsible for checking the provider and understanding your remaining payment-security duties.^[13]

Try it: Confirm that pages and resources load over HTTPS, the contact method works, outdated promotions have been removed, and the people responsible for updates and backups are identified. Ask what would happen if the website were accidentally deleted tomorrow.

6. Help search engines and people find the right pages

Search engine optimization (SEO) means making a site easier for search engines to discover and understand, and helping people judge whether a result answers their question. It is not a purchase of a guaranteed ranking. Google explicitly says there is no secret method that automatically puts a site first, and inclusion in Google's index is not guaranteed.^[14]

Begin with straightforward improvements: clear page titles, descriptive headings, readable text, useful links, and individual pages for genuinely distinct services or information. Describe where a business actually operates when location is relevant. A hypothetical Fort Smith repair shop might explain the repairs it performs and its real service area; it does not need separate near-identical pages repeating the names of Fort Smith, Van Buren, and Sallisaw.

Google Search Console is a free tool for site owners to check how Google discovers and indexes their pages, inspect search performance, and identify certain technical issues. It helps you diagnose problems; it cannot promise visits or sales.^[15]

Try it: Search for your business name, check whether important pages appear, and inspect those pages in Search Console after verifying ownership. If a page is not indexed, investigate the reason rather than buying an unexplained 'ranking package.'

7. Know what you own and what must be maintained

A website involves several different things: a domain name (the address), hosting (where the website runs), content (the words, photos, and other material), and sometimes a builder or platform (the software used to manage it). Paying for one does not necessarily mean you control all the others.

Before choosing a builder or hiring someone, find out:

• Who controls the domain registration and renewal?
• Who can log into the hosting account, builder, and analytics tools?
• Can you export your text, images, product information, or other important data?
• What happens to the website when a subscription or service agreement ends?
• Who handles updates, backups, accessibility problems, and security fixes?
• Which costs recur, and what requires an additional fee?

ICANN publishes information on the rights and responsibilities attached to domain registration. For a business, independently controlled domain access and reliable renewal arrangements are practical safeguards.^[16]

A third-party builder can be a sensible choice for a simple business website. Templates are not automatically inferior to custom code, and a monthly subscription is not automatically wasteful. Compare whether the tool meets your needs, lets you make routine changes, and leaves you with acceptable costs and control. Custom development can be useful for unusual workflows or integrations, but complexity is a cost to justify, not a badge of quality.

Try it: Write down where your domain, hosting, content, and backups live. Then test whether you can update a phone number yourself. If leaving a provider would strand your business information, understand that limitation before renewing.

An example: two approaches to the same business

Imagine a small bakery taking orders for pickup. Website A has animations, elaborate transitions, and a custom-built ordering interface, but the pickup hours are buried and the order button breaks on mobile. Website B uses a standard template, lists popular products, explains lead times, and offers a reliable order form or clear contact method.

For this task, Website B is better. That judgment is based on what a customer can accomplish, not on what either site cost. It does not mean template sites always win, or that design quality is irrelevant. Good design helps people understand and use the website. Decoration that blocks the task does not.

Check your own website

Use this as a first-pass review. A checked box means you tested it, not merely that you assume it works.

• A new visitor can explain what the website offers and what to do next.
• Hours, contact details, locations, prices, and important policies are accurate where relevant.
• Navigation and important actions work on an actual phone.
• Important content is available on mobile as well as desktop.
• The page can be navigated by keyboard and focus remains visible.
• Text, images, video, and forms have received basic accessibility checks.
• Important pages load and respond acceptably on mobile, without disruptive layout shifts.
• HTTPS works and someone is responsible for updates and backups.
• Pages have descriptive headings and can be inspected in Search Console.
• You know who controls the domain, platform, content, and recurring costs.

Free tools to start with

• W3C Easy Checks: Follow a guided first accessibility review. It is not a complete audit.
• PageSpeed Insights: Compare mobile and desktop diagnostics, and read real-user information if available.
• Google Search Console: Monitor search visibility and indexing once site ownership is verified.
• Your phone and keyboard: Test the real tasks your visitors need to finish. Both are more useful than guessing from a screenshot.

The takeaway

A website is good when it is useful, usable, accessible, reasonably fast, trustworthy, discoverable, and maintainable for its intended audience. No single score, platform, agency, or price tag can establish all seven qualities.

In later chapters, we will use these same questions to compare website builders and evaluate services. The burden of proof stays with the claim: if someone says a website is better, ask better for whom, at what task, and based on what evidence?