Audit your quote page on a phone before blaming low website traffic: working record
Use this six-field worksheet to test the full small-screen inquiry journey, including errors and receipt, rather than layout alone.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Device and page | Task attempted | Observed obstruction | Error recovery result | Delivery evidence | Repair and retest owner |
|---|---|---|---|---|---|
| Illustrative: phone and quote page | Submit internal test | Keyboard covers final action | Not yet retested | Inbox check pending | Website owner |
- The starting row is fictional, not merchant evidence. Replace it with your own verified record. Blank fields remain unresolved.
- Create one row per decision or observation described in the article. Use the worked example to understand the method, not as proof about your business.
- Record exact public URLs and collection dates where relevant. Unknown, failed and not checked are different from a verified pass.
- Keep customer information, account credentials and private documents outside this worksheet. Use role names or internal references.
- A completed row does not prove publication, authorization, indexing, rankings or revenue. Record the actual acceptance check separately.
- Export the record to approved business storage if needed. Browser edits are cleared on reload.
A page can look good in a desktop screenshot and still make it difficult to inquire on a phone. Customers need to read the offer, find the right action, enter their info, recover from errors, and understand the result. Audit the whole journey before assuming the only problem is traffic.
Use with this guide
website audit tool
Review the current scope and workflow for website audit tool.
business website tool
Review the current scope and workflow for business website tool.
Machining inquiry forms: qualify scope without drawings
Start with nonconfidential scope questions to qualify machining inquiries. Use the intake worksheet before arranging a controlled exchange of customer drawings.
Choose the customer task before choosing a device
Start with the action people came to take: request a repair appointment, get a wrap estimate, or arrange a consultation. Start the test on the relevant service page, not automatically on the homepage. Search visitors can land anywhere on your site. The website audit tool sorts the findings, but each one should say what failed and where. Google’s starter guide calls for clear, organized content and helpful navigation. So test the words and action labels on a phone, not just the spacing. Decide what counts as a successful submission before you record the result.
Sources for this section: Google Search Central: SEO starter guide
Test the difficult states, not only the empty form
Try a long business name. Leave out a required field, then fix an invalid value. Does the form show what went wrong and keep the useful information you entered? Check whether the on-screen keyboard covers the button, a sticky banner blocks a field, or a dropdown runs offscreen. Repeat the critical route on a tablet if that matters to your customers. These are practical acceptance tests for observable behavior, not full accessibility certification. Keep specialist accessibility issues flagged for qualified review. One successful phone test does not mean the site is compliant.
Sources for this section: Google Search Central: helpful, reliable, people-first content
Verify receipt separately from the thank-you screen
Use an approved internal test and confirm the destination receives the expected service context. A success page alone confirms neither that staff received it nor that a booking is confirmed. In an illustrative test, the form accepts a request and shows “Appointment confirmed,” but the backend only sends an email for manual review. That is both a workflow and wording problem. The business website tool supports maintaining content and supported forms within the account scope, but a third-party scheduler needs its own verified behavior. Record the actual state reached and label it accurately. Do not submit unnecessary real appointments while testing.
Sources for this section: Google Search Central: SEO starter guide
Use performance evidence to explain observed friction
If the page responds slowly or shifts when a customer taps, get evidence. Don’t guess. Google’s Core Web Vitals guidance looks at loading, interactivity, and visual stability. A lab score helps diagnose problems, but it can’t guarantee what every customer sees on their device. Note the device, connection context, and exact behavior in your report. A big hero image might delay useful content. A third-party widget might affect interaction. Ask the developer for one focused change, then retest the same task. Don’t cut essential consent or service information just to make the form look shorter.
Sources for this section: Google Search Central: Core Web Vitals
Keep a mobile acceptance sheet
Use one row for each task and device context. Describe the problem so a developer can reproduce it, and name the affected field or button. Record error recovery and delivery evidence separately. Give the repair an owner, and save the original test reference for comparison. Keep personal data out of screenshots and worksheet entries. Close a finding when the customer task works under the tested conditions, but document any limits that remain. BlueFinch’s audit does not automatically repair an external website or certify every device. It gives the owner a clearer work order and a way to check that the customer obstacle was actually removed.
If the keyboard blocks something, note which field had focus and whether the customer could scroll to the button. A screenshot without that state may not reproduce the issue. After the fix, repeat the same steps. Then make sure the change didn’t hide the error message or remove useful instructions.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
- Google Search Central: SEO starter guide
- Google Search Central: helpful, reliable, people-first content
- Google Search Central: Core Web Vitals
Use this page for general business information. It is not legal, tax, or accounting advice.