01. A hidden contact path
Evidence: The “before” concept has no call action in its first screen.
Why it matters: A visitor who is ready to call must keep searching.
Fix: Add a tap-to-call button in the first screen; test it at 360px.
Examples, not invented results
These examples show how the work is approached. They are clearly labeled concepts and samples, not client projects or claims of improved leads.
Concept example · Fictional home-service site
Before: A vague headline and a “learn more” link leave the service area and contact route unclear.
After: The service and area sit beside a prominent call action. This is an interface concept; no conversion improvement is claimed.
Sample Website Check · Illustrative
A real check includes screenshots from the actual site. Here, the paired concept illustrations above are the evidence for the sample below.
This website’s own checks
Release targets: Lighthouse performance at least 90, accessibility 100, best practices at least 95 and SEO 100, with zero axe violations.
Production measurements are not yet available. The site is awaiting owner details and launch validation. These are targets, not reported scores.
Measured local review results and their limitations are recorded in the project’s TESTING.md. Production figures will be published here after the release build is tested.
Automated checks do not establish WCAG conformance. Keyboard, screen-reader and real-device checks are also part of the launch checklist.
Start with a clearer picture
3 specific findings. A person looking at your website. No sales call needed.