It reads a website the way a designer does.
Nine typefaces. Body text at 13px. Forty-one spacing values on no grid at all. The things a designer notices in ten seconds, measured and written down.
01Measured from the rendered page
Not from the stylesheet, which lies: it lists rules nobody hits and misses everything a script applied afterwards. pagehaul reads the computed style and the real geometry of every visible element, so the type scale it reports is the one a visitor actually sees.
That distinction matters more than it sounds. A site can declare a tidy design system and still render eleven font sizes, because of a plugin, a pasted embed and a theme update nobody audited.
02What gets checked
Typography: typeface count, size count, body size, heading-to-body ratio, line length in characters, line height. Colour: distinct colours, accent, and every sampled text pair scored against WCAG AA with the real ratio. Spacing: distinct values and whether a base unit exists. Layout: alignment edges, widest text block, what falls above the fold. Plus hierarchy, consistency, interaction states, imagery, navigation, forms, motion and content weight.
03Honest about what it could not see
A page behind a bot wall, a capture that timed out, a stylesheet on another origin the browser would not let us read: each of those becomes a line saying so, not a silent pass. A tool that reports “no issues found” when it could not look is worse than one that reports nothing.
Ready to send it to a client? The teardown report wraps these measurements in your voice as a PDF, and the website audit tool covers speed, SEO and conversion alongside the design.
04Questions people ask
What is a UX audit?
A structured review of how a page works for the person using it: whether the hierarchy guides the eye, whether text is readable, whether controls are reachable and obvious, whether the design holds together. pagehaul measures the parts that can be measured and leaves judgement to you.
Which UX things can actually be measured?
More than most people expect. Typeface and font-size counts, body size and line length, line height, colour contrast ratios against WCAG AA, how many distinct spacing values are in use and whether they sit on a grid, alignment edges, competing calls to action above the fold, tap target sizes, navigation item counts, form field labelling and visible focus states.
Does it check accessibility?
It checks the parts a rendered page can be measured for: colour contrast with real ratios, visible focus styles, form labels, alt text presence and tap target size. It is not a substitute for a full WCAG conformance review with assistive technology.
Does it tell me what to change?
Every finding is written as what was found, why it matters to the business, and the specific change that fixes it. Not principles, changes.
Can it judge how a page looks, not just measure it?
Measurement has a ceiling: it can count nine font sizes but cannot tell you the hero photo is a stock handshake. When a vision model is configured, a second pass looks at the screenshots and adds that reading, clearly marked as interpretation rather than measurement.
Paste a prospect's link and get a report you can send.
Tear down a site free