Will It Vibe?Live UX Audit
How the audit works
A Live UX Audit renders your deployed page in a real browser and measures what it actually does, rather than reading your source or checking a box. Here is what goes into it.
It is a live render, not a scan
We load your URL in a headless browser at mobile, tablet, and desktop widths, let it run, and observe the result: the rendered DOM, the load metrics, and any errors the page throws. Every problem the render turns up becomes a finding. Because the audit reads a real page state, the same page in the same state produces the same score every time — there is no model guessing in the middle.
The six areas
Each area gets its own 0–100 score from the checks that apply to it. The overall score is a weighted blend of the six, with accessibility carrying the most weight because it most directly decides whether people can use the page. We do not publish the exact weights; they are tuning, and a page earns a good score by rendering cleanly, not by reverse-engineering a formula.
Accessibility
Whether people using a keyboard, a screen reader, or a high-contrast display can actually operate the page. We run axe-core against the rendered DOM for the well-established rules — labels, roles, contrast, focus order — and add checks for things axe does not cover. This is the heaviest area, because a page that looks fine but cannot be operated is not really usable.
Responsive & mobile
How the page holds up at real phone, tablet, and desktop widths. We flag pages wider than the viewport (the sideways-scroll problem), interactive controls smaller than a comfortable 44px touch, and a missing responsive viewport that leaves mobile users pinching to read.
Performance
How the page feels while it loads. We read the largest paint, how much the layout shifts as things arrive, the total weight transferred, and the number of requests. These are one reading from one render — real-world conditions vary — so we treat them as observations, not a lab benchmark.
Reliability & errors
Whether the page loads cleanly. We watch for JavaScript console errors, failed and error-status requests, broken images, insecure sub-resources on an HTTPS page, and pages served over plain HTTP. These are the cracks that make a site feel unfinished.
Structure & semantics
Whether the markup gives the page a clear shape. We look for landmark regions, a single obvious main heading, and whether the page is built from semantic elements or mostly bare divs. Good structure helps assistive tech and search engines alike.
Content & metadata
The small things that shape first impressions and link previews. A useful page title and description, no placeholder copy left in by accident, and a declared favicon.
How scoring behaves
A check either fires or it does not. When one fires, it costs a fixed amount by how serious it is, and it costs that amount once — a page with two hundred low-contrast elements is not driven into the ground any faster than one with two. Repeated instances are counted and shown so you can see the scale of a problem, but they do not multiply the penalty.
The headline counts are honest about scope: we tell you how many checks ran on your page, including the accessibility rules that actually applied, and how many flagged something.
What it is not
This is a live audit of one render of your deployed page, not a WCAG certification or a guarantee of compliance. Automated checks catch a real and useful slice of accessibility and quality problems, but they cannot judge everything a human reviewer would — meaning, context, and intent still need a person. Treat a high score as a good sign and a clean render, not as a legal sign-off. Nothing here is legal or professional advice, and Will It Vibe is independent of the sites it audits.
Back to the Live UX Audit workspace.