QA Checklist for Webflow Projects: What Agencies Should Demand

TL;DR: A Webflow QA checklist covers six areas before any project is signed off:

• Responsive layout tested on real breakpoints, not the Designer canvas
• Core Web Vitals measured, not promised
• Images compressed, converted, and lazy loaded
• SEO and schema present on every key page
• CMS, forms and integrations tested under realistic load
• Accessibility verified by keyboard

If an agency cannot show a pass on each area, the site is not finished. It only looks finished.

In my work handing off Webflow builds to agencies and their clients, the sites that come back with problems almost always failed a check that takes minutes to run. This is the checklist I would demand as a client.

The Webflow QA checklist at a glance

Here is what a proper pre-launch pass looks like, with the standard each item has to meet.

1. Does the Webflow site hold up on every breakpoint?

Test the published site on mobile, tablet, desktop and an oversized monitor, not the Designer canvas. Layout is the fastest thing to break and the fastest to spot, so shipping it broken has no excuse.

What to look for

• Horizontal overflow causing sideways scroll on phones
• Collapsed or doubled spacing between sections
• Text overlapping images or running outside its container
• Navigation and modals working on touch, not just hover

2. Does the build pass Core Web Vitals?

Performance is where most "finished" Webflow sites quietly fail. Ask for a real measurement from field data rather than a promise or a single Lighthouse run on a fast laptop.

The targets to hold your developer to

A good page reaches Largest Contentful Paint within 2.5 seconds, responds to interaction with an Interaction to Next Paint of 200 milliseconds or less, and keeps Cumulative Layout Shift at 0.1 or less, all measured at the 75th percentile of real visits (web.dev).

3. Are the images actually optimised?

Two Webflow specifics catch teams out here, and both are invisible until someone loads the site on mobile data. Neither takes more than a few minutes to fix before launch.

The rich text trap

Webflow automatically generates responsive image variants and a srcset for inline JPG, PNG and WebP images, but images placed inside a rich text element do not get those variants (Webflow Help). A hero image dropped into a rich text block ships at full desktop weight to phones.

The conversion tool nobody runs

Webflow has a built-in image conversion tool that converts JPEG and PNG assets to AVIF or WebP in the Assets panel, and new images lazy load by default (Webflow Help). My guide to speeding up a Webflow site goes deeper.

4. Is the SEO and schema markup in place?

Check that every important page carries a unique title, a meta description, one clear H1, and a sensible heading order. Missing metadata on CMS template pages is the single most common gap I find.

Structured data is not optional now

Webflow has a native Schema markup field in Page Settings for static and Collection pages, with one-click AI generation, so key pages have no reason to ship without it (Webflow Help). Article and FAQ schema is what pulls a page into rich results and AI answers.

5. Are the CMS, forms and integrations safe under load?

A design that ignores Webflow's structural limits works perfectly on launch day and breaks once the CMS fills up. Confirm the build respects them before sign-off rather than after.

The limits to check against

Webflow allows up to 40 Collection lists per page, 10 nested Collection lists per page, and 100 items per list without pagination (Webflow Help).

What to test by hand

• Submit every form and confirm the notification actually arrives
• Check the success and error states, not just the happy path
• Test each third-party integration end to end with real data
• Load a Collection list with more items than launch content

6. Is the Webflow site accessible?

Accessibility overlaps heavily with SEO and is increasingly a contractual client requirement rather than a nice-to-have. The fastest meaningful test needs no tooling at all.

The keyboard test

Tab through every page and confirm you can reach and operate every link, button and form field, with a visible focus outline at each stop. If a build cannot be operated without a mouse, it is not ready to launch.

What else to verify

• Alt text on every meaningful image, empty alt on decorative ones
• Colour contrast legible for body text and buttons
• Form fields with real labels, not placeholder text alone
• Headings in order, with no levels skipped for styling

Who should run the Webflow QA pass?

The person who built the site is the worst person to sign it off, because builders stop seeing their own gaps after weeks inside a project. Insist that someone other than the builder runs this list.

A reviewer can be a second developer, the agency lead, or an outside specialist. For teams handing off builds regularly, a repeatable process matters more than heroics, which I describe in the white-label Webflow workflow. If you want a second set of eyes on a build before it goes live, book a quick call and I will run it against exactly this checklist.