QA Checklist for Webflow Projects: What Agencies Should Demand

Short answer: A solid Webflow QA checklist covers six areas before any project is signed off: responsive layout on real breakpoints, Core Web Vitals and image optimisation, SEO and structured data, CMS and dynamic content limits, forms and integrations, and accessibility. If an agency cannot show you a pass on each of these, the site is not actually finished, it just 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. So this is the checklist I would demand as a client, with the specific things that quietly break in Webflow and the verified targets to hold your developer to.

The Webflow QA checklist at a glance

Here is what a proper pre-launch pass looks like, and why each item earns its place.

1. Does it hold up on every breakpoint?

Test the live layout on mobile, tablet, desktop, and an oversized monitor, not just the Designer canvas. Look for horizontal overflow, collapsed spacing, and text that overlaps images. This is the fastest thing to break and the fastest to spot, so there is no excuse for shipping it.

2. Does it pass Core Web Vitals?

Performance is where most "finished" Webflow sites quietly fail. Hold the build to Google's Core Web Vitals: a good page reaches largest contentful paint (LCP) within 2.5 seconds, responds to interaction (INP) in 200 milliseconds or less, and keeps cumulative layout shift (CLS) at 0.1 or less, all at the 75th percentile of real visits (web.dev). Ask for a real measurement, not a promise.

3. Are the images actually optimised?

Two Webflow specifics catch teams out here. First, 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). So a hero image dropped into a rich text block can ship at full desktop weight to phones. Second, 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). Demand that both are used. My guide to speeding up a Webflow site goes deeper on this.

4. Is the SEO and schema in place?

Check that every important page has a unique title, meta description, one clear H1, and a sensible heading order. Then check structured data. Webflow has a native Schema markup field in Page Settings for static and Collection pages, with one-click AI generation, so there is no reason for key pages to ship without it (Webflow Help). Article and FAQ schema is what helps you get pulled into rich results and AI answers.

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

Confirm the build respects Webflow's dynamic content limits: up to 40 Collection lists per page, 10 nested lists per page, and 100 items per list without pagination (Webflow Help). A design that ignores these breaks the moment the CMS fills up. Then submit every form, confirm notifications land, and test any third-party integration end to end. For teams handing off builds regularly, a repeatable process matters more than heroics; I describe mine in the white-label Webflow workflow.

6. Is it accessible?

Every meaningful image needs alt text, interactive elements need visible focus states, colour contrast has to be legible, and the whole site should be navigable by keyboard alone. Accessibility overlaps heavily with SEO and is increasingly a client requirement, not a nice-to-have.

A quick way to run this is to test with the keyboard alone: 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. Screen reader users and search crawlers benefit from the same clean structure, so fixing accessibility rarely helps only one audience. If a build cannot be operated without a mouse, it is not ready to launch.

Who should run the QA pass?

The person who built the site is the worst person to sign off on it, because they stop seeing their own gaps. Whether it is a second developer, the agency lead, or an outside specialist, insist that someone other than the builder runs this list before launch. If you want a second set of eyes on a Webflow build before it goes live, book a quick call and I will run it against exactly this checklist.