PracticalMode ·
Where the request form appeared
We started at each contractor’s homepage in a mobile browser. Eleven sites had a usable request form on that page. On eleven more, a single tap opened one. On one site we opened the menu and tapped Contact Us. Across those 23 verified routes, the median was one navigation tap.
| From homepage | Columbus | Indianapolis | All |
|---|---|---|---|
| Form on page | 5 | 6 | 11 |
| One tap | 5 | 6 | 11 |
| Two taps | 0 | 1 | 1 |
| Unresolved | 7 | 5 | 12 |
| Sites tested | 17 | 18 | 35 |
Eight homepage forms started below the first screen
We could locate the first field in page coordinates on 10 of the 11 homepage forms. Eight started below the initial 844-pixel screen. On two sites, the first field began more than 9,000 CSS pixels down the page. The eleventh form sat inside an embedded frame, so we left it out of the position count.
A clearly labeled button near the top can take a visitor directly to a form farther down. We measured where the fields appeared. We did not time the scroll or test how quickly a homeowner would notice a shortcut.
What counted as reaching a form
We tested 35 distinct domains associated with foundation contractors serving Columbus, Ohio, or Indianapolis, Indiana. We selected sites from public searches and our existing contractor research. This small, nonrandom sample cannot establish which city performs better or how common these designs are nationally.
Each visit began in a fresh Chrome session emulating a 390 × 844 Android touchscreen. We allowed scrolling and waited for embedded forms. A route qualified when we could reach an actionable field in a form that accepted an inspection, estimate, consultation or service inquiry. A general callback form qualified if a homeowner could use it to ask about a foundation problem.
We counted the shortest route we actually verified. Scrolling, typing and pressing Submit were outside the count. We entered no homeowner information, placed no calls and submitted no requests. The results describe access to the form. Delivery, confirmed appointments and conversion rates were outside the study.
Why 12 sites have no tap count
Four sites returned an access challenge or blocked our browser. One hostname failed to resolve and one failed certificate validation. One site offered a phone estimate and email. Three contact routes yielded no actionable form in our session. One stopped at a ZIP-code check, and another routed us differently across visits. We could not assign those sites a reliable count. A homeowner on a different device or network might see a different result.
Try the same check on your phone
Open your homepage and look for the action you would take if you had just found a crack in a basement wall. Count the taps to the first field and notice whether the next screen explains who will call back. If your homepage button jumps to a form, check where the jump lands with your mobile header in place. Our foundation inspection request form guide covers what to ask once the homeowner gets there.
All owner guides