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.
68
Site Health Index
Fail · Poor
Coverage
How thoroughly the engine looked.
13
Pages discovered
13 pages fully interacted
617
Interactions attempted
360 succeeded · 15 errored · 1 skipped
376
Interactive elements
306 links · 58 buttons · 12 inputs
96%
Element coverage
Of all elements, how many were exercised
4
Breakpoints tested
1920 · 1440 · 768 · 375
52
Viewport snapshots
13 pages × 4 breakpoints
Defects
Where the engine found friction.
22 defects across the run, broken down by severity. Open a row to see the actual selector or URL the engine hit, the error it surfaced, and whether a fix is queued. None of these are auto-fixable — they all need a human eye, which is by design.
Critical
0
Site-breaking · none this run
High
1
Real user pain · needs attention
Medium
19
Interaction / layout / network
Low
2
Cosmetic · server noise
High · console-error Failed to load resource — HTTP 400 from Supabase auth supabase.co/auth/v1/token
- Severity
high— surfaced as a console error during the contact-form interaction path- Source
console- URL
https://azrqlchfxqktmzsxfzcm.supabase.co/auth/v1/token?grant_type=password- Auto-fixable
- No — needs-attention
- Occurrences
- 1
Failed to load resource: the server responded with a status of 400 ()
Low · occluded-element Load-more button is hidden but still in the DOM #load-more
- Severity
low— visibility issue, the element is rendered but not visible- Category
button- Element text
Load more- Auto-fixable
- No — needs-attention
- Occurrences
- 1
locator.waitFor: Timeout 3000ms exceeded.
- waiting for locator('#load-more').first() to be visible
10 × locator resolved to hidden <button id="load-more" class="load-more">Load more</button>
; force: locator.click: Element is not visible
Low · http-400 HTTP 400 on Supabase auth POST supabase.co/auth/v1/token
- Severity
low— server-side rejection on auth endpoint- Source
http- Fix type
server-error— review the Supabase configuration- Auto-fixable
- No
- Occurrences
- 1
HTTP 400 on POST https://azrqlchfxqktmzsxfzcm.supabase.co/auth/v1/token?grant
Medium · interaction-error 12 gallery buttons unreachable — interaction timed out #gallery-grid > div:nth-child(6..11) · View result / Share
- Severity
medium— interaction path is broken; user can't reach those actions- Category
button- Fix type
form-fix— investigate visibility / scroll-into-view behaviour- Auto-fixable
- No
- Occurrences
- 12 across six gallery cards (View result → and Share on items 6–11)
locator.waitFor: Timeout 3000ms exceeded.
- waiting for locator('#gallery-grid > div:nth-child(N) > div:nth-child(2) > button:nth-child(4)').first() to be visible
; force: locator.click: Timeout 2000ms exceeded.
Affected selectors:
#gallery-grid > div:nth-child(6) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(6) > div:nth-child(2) > button:nth-child(5) — "Share"
#gallery-grid > div:nth-child(7) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(7) > div:nth-child(2) > button:nth-child(5) — "Share"
#gallery-grid > div:nth-child(8) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(8) > div:nth-child(2) > button:nth-child(5) — "Share"
#gallery-grid > div:nth-child(9) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(9) > div:nth-child(2) > button:nth-child(5) — "Share"
#gallery-grid > div:nth-child(10) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(10) > div:nth-child(2) > button:nth-child(5) — "Share"
#gallery-grid > div:nth-child(11) > div:nth-child(2) > button:nth-child(4) — "View result →"
#gallery-grid > div:nth-child(11) > div:nth-child(2) > button:nth-child(5) — "Share"
Medium · interaction-error 2 more gallery buttons unreachable (items 4–5) #gallery-grid > div:nth-child(4..5) · View result / Share
- Severity
medium— same interaction-timeout pattern as the other gallery cards- Category
button- Auto-fixable
- No — form-fix
- Occurrences
- 2
locator.waitFor: Timeout 3000ms exceeded.
- waiting for locator('#gallery-grid > div:nth-child(4) > div:nth-child(2) > button:nth-child(4)').first() to be visible
- waiting for locator('#gallery-grid > div:nth-child(5) > div:nth-child(2) > button:nth-child(4)').first() to be visible
; force: locator.click: Timeout 2000ms exceeded.
Medium · network-error mailto: link navigation aborted by the browser mailto:projects@saffrondesigns.io?subject=Project enquiry — Test User
- Severity
medium— the engine's GET on the mailto link was aborted; not all environments handle this gracefully- Fix type
link-check- Auto-fixable
- No
- Occurrences
- 1
GET mailto:projects@saffrondesigns.io?subject=Project%20enquiry%20%E2%80%94%20Test%20User&body=OmniSphere%20stress%20test%20submission. — net::ERR_ABORTED
Medium · layout-issue ×4 Off-screen element detected across 4 viewport checks desktop-1920 · desktop-1440 · tablet-768 · mobile-375
- Severity
medium— at least one element on the page extends beyond the visible viewport- Source
viewport- Fix type
responsive-fix- Auto-fixable
- No
- Occurrences
- 4 — one per breakpoint, mobile-375 had two
Issues at desktop-1920: off-screen-element Issues at desktop-1440: off-screen-element Issues at tablet-768: off-screen-element Issues at mobile-375: off-screen-element
Performance signals
What the browser told us.
Console errors
1
Real issue from the page itself
Page errors
0
Uncaught exceptions during the crawl
Failed requests
1
Network calls that didn't come back
HTTP 4xx / 5xx
1
Server-side rejections
Third-party noise
10
Suppressed (analytics, ads, etc.)
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.