Build -
We ran QA on our own site: 7 issues found, 7 fixed
We tested famingu.com the way we test client work. Nothing was critical, but all 7 issues were real, and all 7 were fixed the same day.
We put famingu.com through a black-box QA pass, on desktop and on a phone-sized screen: 35 pages, the browser console, network calls, search tags, and all 60 combinations of the System Builder on the home page. Most of it passed. Seven things did not.
Two were words, not code. Our "How we work" section told visitors to use a contact form that does not exist, and the WhatsApp demo card said "chat" when the demo only has tap-to-ask buttons. Both now describe what is really there.
One hid in the catch-all option. In the System Builder, picking "Others" made the pre-filled WhatsApp message say "I run your business". The other eleven business types read fine. Fixing it turned up a second slip of the same kind in the lead follow-up demo, where "Other" produced "your other business".
The rest were about using the site. The booking calendar sat below our contact details, so the page said "pick a time" without showing one; it now comes first. Several links were too small to tap comfortably on a phone; they now have a proper tap height. A demo form had no length limits; now it does. And the site was missing a set of standard browser security headers; they are in place, with the strictest one running in warn-only mode first.
What we are keeping: copy is part of quality, the "Other" option is where bugs hide, and fixing one bug is often how you find the next.
Written by Rushi Prajapati