Est. 2019
Est. 2019
Last Updated:
April 21, 2026
Parth Gaurav
Founder & CEO
A comprehensive Webflow QA checklist should cover 9 categories: functionality testing, cross-browser testing, responsive design, user experience, performance (Core Web Vitals), SEO elements, accessibility (WCAG 2.1), third-party integrations, and final review. Based on 50+ Webflow launches at Digi Hotshot, the most commonly missed items are: custom code not working on staging vs production, Safari-specific CSS bugs, mobile tap targets under 48px, and missing schema markup. A thorough QA process takes 3-5 days for a mid-complexity B2B site.
We've launched over 50 Webflow sites since 2019. B2B SaaS companies, fintech platforms, healthcare brands, real estate firms — all different, but the QA mistakes? Basically the same every time.
After the first dozen launches, we stopped winging it. We built a checklist. Then we broke things anyway, so we made it longer. Then we broke different things, so we added those too.
This is the actual list we run through before every single launch. 47 tests, 9 categories, zero guesswork. If you're about to push a Webflow site live, bookmark this page and work through it top to bottom.
Fair warning: this isn't a "make sure your site looks nice" overview. This is the nitty-gritty, test-every-form, check-every-breakpoint, crawl-the-whole-site process that separates a clean launch from a "why is the homepage broken on Safari" panic at 10pm.
This is where most teams start and — honestly — where most teams also cut corners. Every interactive element on the site needs to work. Not "looks like it works in the Designer." Actually works, on a published staging URL.
Test 1: All links (internal, external, anchor). Click every single one. Internal links should go where they say they go. External links should open in a new tab. Anchor links should scroll to the right section, not jump past it or land 50px too high because of a sticky nav.
Test 2: All forms. Submit every form on the site. Check that the thank-you page or success message appears. Check that the email notification arrives (and doesn't land in spam). If the form connects to a CRM — HubSpot, Salesforce, whatever — verify the lead actually shows up with the right field mapping. We test each form at least twice.
Test 3: All buttons and CTAs. Every button needs a working hover state, a correct click action, and a tap target that's actually hittable on mobile (minimum 48px). You'd be surprised how many "Book a Demo" buttons go nowhere because someone forgot to add the link.
Test 4: Sliders, tabs, accordions. Check all states — not just the first slide or the default open tab. If there's auto-play, make sure it pauses on hover. Test keyboard navigation (arrow keys for sliders, Tab + Enter for accordions).
Test 5: Modal and popup triggers. Open every modal. Close it with the X button, the overlay click, and the Escape key. Make sure the background doesn't scroll while the modal is open. This one breaks on mobile more often than you'd think.
Test 6: CMS dynamic content. If you're using Webflow CMS, verify every collection list renders all items. Check that conditional visibility rules work — if a CMS field is empty, does the component hide properly or does it leave a blank gap?
Test 7: Search functionality. If the site has search, test it with real queries. Test with typos. Test with zero results and make sure there's a decent empty state, not just a blank page.
Test 8: E-commerce flow. If applicable, run through the full purchase journey: add to cart, update quantity, remove item, checkout, payment, confirmation email. Test with a real payment method in test mode.
When we built the Sisu Clinic site — 85+ pages, 30+ CMS collections — QA took 5 full days. We found 12 broken CMS references that would have shown empty cards on key service pages. The only reason we caught them is because we checked every single collection item, not just the first three.
"It works on Chrome" is not QA. Chrome is maybe 65% of your traffic. The rest is Safari, Firefox, Edge, and mobile browsers that all interpret CSS slightly differently.
Test 9: Chrome (desktop). Your baseline. If it doesn't work here, nothing else matters.
Test 10: Firefox (desktop). Firefox handles custom fonts and flexbox gap properties differently. Check your typography and any complex layouts.
Test 11: Safari (desktop). This is the big one. Safari flexbox rendering breaks on roughly 40% of the builds we QA. Specific issues: gap property in older Safari versions, backdrop-filter rendering, smooth scroll behavior, and video autoplay restrictions. If you only test one extra browser, make it Safari.
Test 12: Edge (desktop). Usually fine if Chrome works, but worth a quick pass — especially if your client's team uses it internally.
Test 13: Safari on iOS. Mobile Safari has its own quirks beyond desktop Safari. Fixed positioning behaves differently, 100vh doesn't mean what you think it means (the address bar messes with it), and input zoom on forms with font-size under 16px is a classic gotcha.
Test 14: Chrome on Android. Different rendering engine than iOS browsers. Test your responsive layouts, form inputs, and any scroll-based animations.
We use BrowserStack for this. LambdaTest works too. The key is testing on real browser engines, not just resizing your Chrome window and calling it a day.
Webflow's Designer gives you breakpoints at 991px, 767px, and 478px. That's a starting point, not the finish line. Real devices don't line up neatly with those numbers.
Test 15: Test at 320px. The iPhone SE still exists. Older Android devices too. If your layout breaks at 320px wide, real people will see it.
Test 16: Test at 375px. Standard iPhone width. This is where most of your mobile traffic lives.
Test 17: Test at 768px. iPad portrait. Tablet layouts are where things get weird — too wide for mobile styles, too narrow for desktop. Give this extra attention.
Test 18: Test at 1024px. iPad landscape and small laptops. Check that your desktop layout doesn't cramp up here.
Test 19: Test at 1440px and 1920px+. Large monitors. Make sure your content doesn't stretch into an unreadable single line across the full width, and that max-widths are set properly.
Test 20: Test on published staging, not just in the Designer. This is the one that catches people off guard. Custom code — embeds, scripts, animations — only runs when the site is actually published. The Designer preview won't show you if your custom code breaks the layout. Always test on your staging URL.
When we launched the Column Tax site, we found 3 mobile layout breaks that were completely invisible in the Webflow Designer. They only showed up on the published staging domain because a custom embed was injecting CSS that overrode our responsive styles. If we hadn't tested on staging with real devices, those would have gone live.
This section is less about bugs and more about "does this site actually make sense to someone who's never seen it before?"
Test 21: The 5-second test. Open the homepage as if you've never seen it. Can you tell what the company does, who it's for, and what you should do next — within 5 seconds? If not, the hero section needs work.
Test 22: The 3-click test. Can a visitor get to any important page in 3 clicks or fewer from the homepage? If your pricing page is buried behind a dropdown inside another dropdown, that's a problem.
Test 23: Load states, empty states, error states. What happens when a page takes a second to load? What does the search results page look like with zero results? What does the form show if someone submits without filling in required fields?
Test 24: CTA logic check. Follow every CTA on the site. Does each one lead somewhere that makes sense? A "Learn More" button on a features section should go to the features page, not the homepage.
Test 25: Keyboard navigation. Tab through the entire page. Can you reach every interactive element? Can you activate buttons with Enter? Can you close modals with Escape?
A slow site kills conversions. Google also factors Core Web Vitals into rankings. This isn't optional.
Test 26: Run PageSpeed Insights. Target 90+ on mobile, 95+ on desktop. Mobile is the harder score to hit and the more important one.
Test 27: Check Core Web Vitals.
Test 28: Image optimization. Every image should be WebP format. Images should be sized appropriately — don't upload a 4000px wide image for a 400px thumbnail. Enable lazy loading on below-the-fold images. Keep hero images under 200KB if possible.
Test 29: Font loading. Preload your critical fonts. Use font-display: swap so text is visible immediately while fonts load. Limit yourself to 2-3 font families max.
Test 30: Remove unused code. Audit your custom code embeds. Remove any CSS or JavaScript that isn't actively doing something. Check for leftover tracking scripts from tools you're no longer using.
Test 31: Run a Lighthouse audit. Beyond PageSpeed, Lighthouse gives you a performance breakdown showing exactly what's slowing things down. Fix the top 3 items it flags.
Across our builds, we typically land at an LCP of 1.8-2.4 seconds and CLS of 0.02-0.05. Those numbers don't happen by accident — they come from optimizing images, fonts, and code during QA, not after launch.
You can build the most beautiful Webflow site in the world. If the SEO basics are wrong, nobody's going to find it. We've written a full guide on SEO-safe Webflow migration if you're moving from another platform, but these checks apply to every launch.
Test 32: Meta titles and descriptions. Every page needs a unique meta title (under 60 characters) and meta description (under 155 characters). Each one should include the target keyword for that page.
Test 33: One H1 per page. Exactly one. Not zero, not three. Check your heading hierarchy — H2s under H1, H3s under H2s, no skipping levels.
Test 34: Alt text on all images. Every image needs descriptive alt text. Not "image1.png." Something like "Dashboard showing real-time revenue metrics for SaaS companies."
Test 35: Open Graph and Twitter Card tags. When someone shares your page on LinkedIn, Slack, or Twitter, what does it look like? Set OG title, OG description, and OG image for at least the homepage, key landing pages, and blog posts.
Test 36: Canonical URLs. Each page should have a canonical URL pointing to itself. Webflow sets these automatically, but double-check — especially on CMS pages.
Test 37: Sitemap accuracy. Webflow auto-generates a sitemap. Make sure it includes all the pages you want indexed and excludes any pages set to noindex.
Test 38: Schema markup. Add structured data where it makes sense — Organization schema on the homepage, Article schema on blog posts, FAQ schema on FAQ sections. Test with Google's Rich Results Test.
Accessibility isn't a nice-to-have. It's a legal requirement in many jurisdictions, it improves SEO, and it means everyone can actually use the site you built.
Test 39: Color contrast ratios. WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text. Use WebAIM's Contrast Checker.
Test 40: Descriptive alt text. Screen readers read alt text aloud. "Image" tells a blind user nothing. "Team of engineers reviewing code on a shared screen" tells them what's happening.
Test 41: Keyboard navigation on interactive elements. Every button, link, form field, dropdown, tab, accordion, and modal must be reachable and operable via keyboard alone.
Test 42: ARIA labels on custom components. Custom interactive elements need proper ARIA attributes so assistive technologies understand what they are.
Test 43: Lighthouse accessibility audit. Run it and target 90+. Fix everything it flags before moving on.
Most B2B Webflow sites connect to at least 3-5 external tools. Each one is a potential point of failure.
Test 44: GA4 events firing. Don't just check that the GA4 tag is installed. Open Google Tag Assistant, navigate through the site, and verify that pageview events fire on every page.
Test 45: Google Search Console verified. Verify site ownership in GSC before launch. Submit the sitemap.
Test 46: CRM integration end-to-end. Submit a test lead through every form. Check that it arrives in the CRM with correct field mapping.
Test 47: Marketing tools and custom scripts. HubSpot tracking, Mailchimp popups, Intercom chat widgets, Hotjar recordings, any custom JavaScript — test each one. Check the browser console for errors.
When we launched the Vividly site, there were 12 separate integrations to verify — a pricing quiz, an ROI calculator, multiple contact forms, analytics, and marketing automation tools. We created a spreadsheet just for integration testing and checked each one off with screenshots. It took an extra day, but every integration worked perfectly on launch day.
You've tested everything above. Now it's the final sweep before you flip the DNS switch.
Full site crawl. Run Screaming Frog across the entire staging site. It catches broken links, missing meta tags, redirect chains, and orphan pages that manual testing misses.
robots.txt allows indexing. Check that your robots.txt file isn't blocking search engines. Easy to forget if you had a Disallow: / during development.
Favicon and social sharing images. Upload a proper favicon. Set a default OG image for pages that don't have their own.
301 redirects. If you're migrating from an existing site, every old URL needs a 301 redirect to its new equivalent. We have a full guide on this: SEO-Safe Webflow Migration.
DNS configuration. Have your DNS records ready before launch day. DNS propagation can take up to 48 hours, so plan accordingly.
Backup plan. What if something goes wrong after launch? Have a rollback plan. Keep the old site accessible for at least 72 hours after launch.
For a simple marketing site (10-15 pages, no CMS, minimal integrations), 1-2 days. For a mid-complexity B2B site (30-50 pages, CMS, 3-5 integrations), 3-5 days. For a large site with heavy CMS usage and lots of integrations (like our Sisu Clinic build), 5-7 days. Don't rush it.
Our standard toolkit: BrowserStack (cross-browser testing), Google PageSpeed Insights (performance), Lighthouse (accessibility + performance), Screaming Frog (site crawl), Google Tag Assistant (analytics verification), WebAIM Contrast Checker (accessibility), Google Rich Results Test (schema validation), and Facebook Sharing Debugger (social preview).
From our 50+ builds, the top five: (1) Custom code that works in preview but breaks on staging because of load order issues. (2) Safari-specific flexbox and CSS grid bugs. (3) Mobile tap targets that are too small — buttons and links under 48px. (4) Missing or duplicate meta titles across CMS collection pages. (5) Form submissions that reach Webflow's inbox but never sync to the CRM because of incorrect field mapping.
Always on staging first. Webflow gives you a staging URL where custom code and integrations behave differently from the Designer preview. Once staging passes all 47 tests, publish to production and do one final verification pass there.
For smaller sites, the developer who built it can run QA — but they should use this checklist systematically rather than just clicking around. For larger sites, we always have someone other than the builder do QA. Fresh eyes catch things the builder has gone blind to. At Digi Hotshot, our PM runs through the full checklist independently from the developer, and the client gets a structured review period on top of that.
If you'd rather have a team that's done this 50+ times handle it, get a free website audit and we'll show you exactly what your current site needs before a relaunch.
We're a Webflow Premium Partner — we build, we QA, and we make sure nothing breaks on launch day.
Last Updated:
April 21, 2026
Book a 30-minute discovery call. We'll discuss your current challenges and show you exactly how we can help.
Your competitors aren't stuck in developer queues. They're launching campaigns, testing messages, and capturing market share while you're waiting for simple updates.
Eliminate the bottlenecks. Give your marketing team the infrastructure they deserve—fast, autonomous, built to scale.
