The engine · Omnisphere
The OmniSphere®
We prove the whole machine. Not a single page graded by Lighthouse — every page crawled, every button exercised, every link followed across four breakpoints, and one honest number returned: the Site Health Index.
Coverage
How thoroughly the engine looked.
Defects
Where the engine found friction.
Nine findings on the latest full audit — zero critical, zero high. Five medium (mobile tap-target density on the pricing pages) and four low: two are the engine’s own crawler reaching for an intentional keyboard-only skip link and custom radios, and two are the homepage X‑Ray widget, which submits by script on purpose. Every one is documented; none is site-breaking.
Proof · this very site
We point the engine at our own work first. On its remediation run it flagged real gaps here — pages missing skip-navigation links, absent hreflang tags, and sub-44px touch targets on mobile. We fixed every one and re-audited. That is the whole promise: findings, not adjectives.
- Site Health Index
65→83(FAIR → GOOD)- Skip-navigation defects
6→0- Missing hreflang tags
13→0- Critical / high severity
0/0
Medium · mobile Sub-44px touch targets on the pricing pages /rates · /rates/local · /rates/growth · /rates/enterprise
- Severity
medium— some controls in the dense pricing tables fall under the 44px tap-target guideline on a phone- Standard
- WCAG 2.5.5 (AAA); the site already meets 2.5.8 (AA, 24px)
- Occurrences
- Across the four rates pages
Medium · mobile Compact controls in the Brand Soul journey /brand-soul-lab
- Severity
medium— a handful of step controls sit under 44px on mobile- Status
- Queued for the next mobile pass
Low · engine Crawler reached for keyboard-only controls a.skip · custom radio inputs
- Severity
low— the interaction crawler tried to mouse-click an intentionally off-screen skip link and visually-hidden custom radios- Verdict
- Correct accessibility patterns (WCAG 2.4.1), not site defects — kept on the ledger for full transparency
Low · forms X‑Ray widget submits by script, not native submit / — homepage X‑Ray form
- Severity
low— the audit expects a native submit button; the widget runs the scan in-page by design- Verdict
- Intentional — a native submit would navigate away and break the live scan
Performance signals
What the browser told us.
Run it again
Want to prove your own machine?
Trigger a fresh X-Ray from the homepage — the OmniSphere runs against any public URL, not just ours. The result comes back as a Google Lighthouse report that names every failing check.