What makes a website lead-ready?
A lead-ready website lets someone who has decided to get in touch do it from the page they are on, in one step: a phone number that dials on tap, a short form that has been tested end to end, a "book a call" link, and a clear promise of when you will reply. Behind it, every enquiry is recorded with the page it came from, so you know which pages earn their keep.
By Jarek Piotrowski · Last updated
The checklist
- Contact on every page. Phone, form and booking reachable without leaving the page, on a phone as well as a desktop.
- A short form. Name, phone or email, and what they need. Every extra field costs enquiries.
- A form that is tested. Submit a real test enquiry after every change and check it arrives. A form that fails silently is worse than no form.
- A reply promise. Say when you will reply, and keep it.
- Every enquiry traced. Record which page each form, call tap and booking click came from.
- Fast on a phone. Google's Core Web Vitals set the bar: the main content shown within 2.5 seconds (LCP), responses to taps within 200 milliseconds (INP) and layout shift under 0.1 (CLS).
- Easy to tap. WCAG 2.2 sets a 24 by 24 pixel minimum for tap targets; I build buttons and form fields to at least 44 pixels, and body text to at least 16 pixels.
What it is not
A pop-up that opens by itself, or a form behind a "Contact" page three taps away. Those get in the way of the visitor who has already decided.
Each item on this list is part of a LayerOps website build.
Jarek Piotrowski runs LayerOps from Canberra: fast, lead-ready websites, and SEO and AI-answer visibility for professional and service businesses Australia-wide.