What it checks
Public HTML from the homepage and up to three likely contact, quote, booking, appointment, or service-request pages. It looks for observable signals such as tap-to-call links, common forms, conversion CTAs, trust proof, analytics tags, structured data, service-area language, mobile viewport setup, HTTPS, titles, descriptions, and an initial server-response observation.
What it can miss
JavaScript-rendered forms, dynamically injected phone links, private analytics, CRM behavior, call-center performance, off-site booking tools that are not linked in the scanned path, and anything behind authentication. A missing signal means “verify this,” not “we proved it does not exist.”
What priority means
Priority is a product heuristic based on how directly an observed condition can interfere with contacting the business. It is not a calibrated conversion probability, industry percentile, or financial forecast. That is why public result pages emphasize findings rather than a letter grade.
What it will not claim
The scanner does not know traffic volume, paid-media spend, close rate, average ticket, gross margin, call-answer rate, or actual lost revenue unless the business supplies that data. SmallBizzWizz therefore does not manufacture a monthly “revenue leak” dollar figure from a public website alone.
Performance caveat
A single server-response measurement is a clue, not a benchmark. Any speed finding should be reproduced using repeated measurements and, when available, real-user field data before material work is commissioned.
Before implementing
High-value work should be verified against the live site on real devices. For outbound prospects, SmallBizzWizz manually checks the specific issue mentioned in the first message before using it as the basis of a sales conversation.