What 30 small business websites actually ask of their visitors

The five checks

• Headline clarity — Does the H1 say what the business actually does?A headline that names the service and area lets a visitor self-qualify in one glance; one that is purely aspirational makes them scroll or guess.
• Form friction — How many fields does the main inquiry form ask for?Banded 1–3 / 4–10 / 11+. Every field is a decision the visitor has to make before they can become a lead.
• Capture redundancy — Is there a form anywhere, or phone-only intake?Phone-only intake means after-hours and shy visitors have no path to become leads.
• Speed signals — Do they promise a response time, or offer self-serve booking or chat?What visitors can verify before they commit. Note: this measures published promises, not actual response times.
• Tracking maturity — Is analytics present, and is the form positioned where visitors see it?Analytics presence is a rough proxy for measurement maturity; form position is measured as markup position (a limitation, noted below).

Findings

Headline frequencies from the 30-site sample. Each finding links back to the table below so you can see the composition.

• 9/30

  main headlines don't say what the business does — a visitor has to scroll or infer.

• 2/30

  have no inquiry form at all anywhere on the site — phone or email only.

• 6/30

  ask 11 or more fields on their main form; only 2 keep it to 1–3 fields.

• 3/30

  publish any commitment about how fast they respond to an inquiry.

• 10/30

  offer self-serve booking; 5 offer chat.

• 15/30

  have no form on the homepage itself — 13 show one; 2 have no form anywhere.

The dataset (anonymized)

Methodology and limitations

• Sample: 30 sites, 6 industries × 5 sites, drawn from first-page organic results for "[industry] company [metro]" queries in six mid-size US metros. This is a convenience sample of businesses that are visible in search — not a random sample of all US service businesses, and not necessarily representative of offline businesses with weaker web presence.
• Checks are public-HTML based, verified in a real desktop browser where forms are rendered by JavaScript. No page submitted any form, called any phone number, or interacted beyond rendering.
• "Response promise" measures explicit written commitments found on the site (e.g. "within 24 hours"). It is not a measure of actual response behavior — measured response times would require submitting inquiries, which this study deliberately does not do.
• Form field counts include native form fields; two sites route inquiries through third-party embeds (Buildertrend, Google Forms) where field counts are not measurable from the public page — these are banded separately.
• Homepage load time is full HTML fetch time from a residential connection in a single geographic location on one afternoon; it is directional, not a performance benchmark.
• No statistical significance is claimed at n=30. Treat frequencies as a field snapshot, not law. The audit script and raw results are preserved in the repository for reproducibility.

Frequently asked questions