Quick answer: Website QA before launch means testing the live site like a real visitor on every major browser and device: clicking every menu, slider, tab and form, checking layout from small phones to wide screens, verifying accessibility and reduced motion, and confirming performance, links, metadata and tracking. Anything found is fixed and re-tested before launch.
Design reviews catch what looks wrong. QA catches what breaks. Most launch-day embarrassments (a menu that won’t close on iPhone, a form that never sends, a page that scrolls sideways) are found in minutes by someone who actually uses the site the way visitors do.
Which browsers and devices should you test?
At minimum: Chrome, Safari, Firefox and Edge on desktop; Safari on iPhone (including a small model) and Chrome on Android; a tablet in portrait and landscape. Test at real widths, not only the design’s breakpoints.
What should be clicked and checked?
- Navigation, dropdowns and the mobile menu (open, close, keyboard).
- Sliders, tabs, accordions and anything with JavaScript.
- Every form: validation, success message, where the data lands and the notification email.
- Links: no broken links, no empty
#, external links opening correctly. - Media: images load, videos play muted and inline on mobile, no broken embeds.
How do you check accessibility?
- Keyboard-only navigation with visible focus.
- Color contrast, alt text and form labels.
- Headings in a logical order and one H1 per page.
prefers-reduced-motionrespected: content visible, no forced animation.- An automated scan (such as axe) plus a manual pass. See accessibility (WCAG).
What about performance and SEO?
Run Lighthouse on mobile and desktop for every template, check Core Web Vitals targets, and verify titles, descriptions, canonicals, schema, sitemap and redirects. Our SEO and AEO launch checklist covers this part in detail.
How Yungle runs QA
We test every site in real browsers with automated scripts that scroll, click and record errors, then do a manual pass on real devices. Every page has to reach 90+ in Lighthouse for performance, accessibility and best practices before it ships. QA is part of every Root project and continues monthly in Growth.
Frequently asked questions
How long does QA take? For a typical marketing site, a thorough pass takes a day or two, plus time to fix and re-test.
Should QA happen only at the end? No. Test components as they’re built; the final pass then finds far less.
