—
—
The seven disciplines
Each discipline is scored from its own weighted checks, then weighted again into the overall number. The weight is printed so you can see what we think matters.
The itemised findings
Your score above is real and complete — nothing about it is held back. What is held back is the list below: what specifically is wrong, why it costs you patients, and the exact fix for each one. Those findings are not in this page's code, so there is nothing to inspect your way around. Tell us where to send them and they appear here instantly.
Fix these first
Ranked by the weight of the check and the weight of its discipline — so the top of this list is where the score moves most, not simply what failed.
Every check, in full
All 94, grouped by discipline, with what we found and what to do. Open any discipline to read it.
Compare against another practice
Put in the site of the practice down the road — or the one that outranks you — and we will run the same 94 checks and show the two side by side.
How this is measured
Written plainly, including what the tool cannot do. A grade you cannot check is worth nothing.
Everything is observed
Our server requests your page the way a browser would and times every stage of it — DNS, connection, TLS handshake, time to first byte, full download. Then it fetches up to 34 of your stylesheets, scripts and images at once to measure real page weight, compression, cache headers and minification.
It requests the page a second time as an iPhone, reads robots.txt, sitemap.xml and your favicon directly, and makes a plain http:// request to confirm whether the HTTPS redirect actually fires. No figure on this page is estimated from a database of averages.
The markup is parsed, not pattern-matched
Structure, headings, form labels, landmarks, link names, image attributes, structured data and meta tags are read from a real DOM. Colour contrast is computed with the actual WCAG relative-luminance formula against colour pairs found in your own stylesheets — not guessed from a screenshot.
Healthcare-specific signals — booking paths, tap-to-call, opening hours, insurance information, provider credentials, required notices and third-party tracking — are matched against the rendered text of the page, so a phrase buried in a script does not count.
What it cannot see
It does not run your page in a browser. It cannot judge visual design, animation, or how the layout truly behaves at every screen size, and it does not pretend to — those checks report for a human and score nothing at all.
Where a finding comes from a sample of your assets, it says so. Contrast pairs are pulled from your CSS without knowing which are actually rendered together, so that check is a list to verify rather than a verdict.
The compliance checks, honestly
This is not a HIPAA audit, an ADA certification, or legal advice, and it cannot become one. Compliance checks report what is observable in your markup — whether forms travel encrypted, whether advertising pixels run alongside patient forms, whether the notices a practice is generally expected to publish are present.
Those are the questions a regulator or a plaintiff's lawyer would start from, which is why they are worth knowing. What they mean for your practice specifically is a conversation with your own counsel and privacy officer.
A score is only useful if something changes.
Every Oakline template ships responsive, accessible, fast and structured for local search — with tap-to-call, booking paths and the notices a practice site needs already in place. One-time licence, no subscription. Or send us your report and we will tell you honestly whether your current site is worth fixing instead.