Lonta · Local browser lab

Does the call link match the number people see?

Run a controlled number-swap experiment, then check observations from your own website. Everything runs in this browser.

Synthetic teaching fixture. These are example numbers and our own replacement code. This lab does not test CallRail or another provider. The rendered sample links sit inside an inert, interaction-disabled fixture; inspect their values in the results. PASS means comparable details agree; call routing and attribution remain unverified.

1. Run the eight-state lab

Three call links represent a header, page body and mobile bar. The defective replacement changes their text and accessible label, leaving the old tel: destination. The repair updates all three.

Ready. Run the lab to inspect each state.

Initial contact details

Disabled sample: use the expanded results to inspect or copy every phone value.

Observed matrix

2. Check your own observations

Have your site engineer run the supplied console auditor on a page you control. Paste its rows array here, or enter observations in the same JSON format. Pasted markup stays text and is never executed. This page does not fetch a website.

Number comparison scope

Expected tracking number (optional)

Known fallback business number (optional)

Set the expected number from the specific visitor/source configuration. Leave it blank when unknown. A blank expectation cannot confirm the intended tracking number. These fields compare syntax; they cannot confirm that a number is assigned or reaches your office.

CTA observations, JSON array

Each row: id, text (visually displayed label), href (raw destination), accessible (ARIA label or name, optional). Maximum 200 rows and 100,000 characters.

No observations checked.

3. Hand this to your site engineer

Open console-snippet.js as text, review the code, then run it in developer tools on a site you control. It reads visible light-DOM candidates and prints a snapshot. It makes no requests, installs no observer and changes no page data. Rerun after navigation or number replacement.

Configure window.tapAuditOptions before running the snippet:

window.tapAuditOptions = {
  country: 'US',
  expected: '+12025550101',
  fallback: '+12025550100'
};

Use the expected value from your own setup. Inspect missing CTAs manually. Selectors cover visible tel: anchors, visible anchors whose labels normalize to a number, and elements explicitly marked data-phone-cta. Frames, shadow roots, number images, custom JavaScript calling buttons and full accessible-name computation require manual checks. Scroll to every CTA and inspect overlays and hidden text yourself.

Result meanings: PASS = comparable text and destination agree. FAIL = observed mismatch or missing/non-phone link. UNKNOWN = insufficient or unsupported input. FALLBACK = known fallback details agree; expected tracking is not established. All four leave actual calling and source attribution unverified.