Webflow

Webflow site audit

Webflow makes it easy to ship something that looks designed and still loses visitors. The designer view is a desktop canvas, the visitor is on a mid-range phone, and the gap between those two realities is where conversions disappear.

A WTFB roast splits the report in two: measured facts (load timings, contrast ratios, broken links, missing metadata) and human judgement from testers who try to complete your main action on their own device.

What you get: measured facts separated from human judgement.

Start an audit

What we check

Interaction and animation cost

Webflow interactions are cheap to add and expensive to render. We measure main-thread blocking and check whether scroll-triggered reveals hide content from a visitor who scrolls fast.

Breakpoint drift

Tablet and landscape-phone breakpoints are the ones nobody opens in the Designer. Testers open them and report overlapping text, cut-off buttons and unreachable navigation.

CMS collection pages

Template pages inherit one meta description and one og:image for hundreds of items. We check title uniqueness, canonical tags and empty-state rendering when a field is left blank.

Forms and submissions

A form that silently fails looks identical to one that works. Testers submit real data and report whether they got confirmation, an email, or nothing at all.

Image weight

Hero images exported at 3000px and served to a phone are the single most common Webflow performance bug. We report the actual transferred bytes on the first screen.

Typical findings

  • Sticky nav covering the primary CTA on short phone viewports.
  • Scroll animations that never trigger because the visitor scrolled past the trigger point.
  • CMS items sharing one meta description across the whole collection.
  • Form success state shown, but no email actually delivered.

Questions

Do I need to give access to my Webflow project?

No. Everything is checked against the published URL, exactly as a visitor sees it.

Will this replace my designer?

No. It gives your designer a prioritised list of problems with evidence instead of opinions.

How long does it take?

The automated part is minutes. Human tester reports usually land within 48 hours.

See also

A roast is an automated audit plus reports from real testers, with evidence attached.