AI can build a working site in minutes, which makes it tempting to publish straight away. But a page that looks right can still have a broken form, a wrong price or a button that does nothing.
Good quality does not need a testing department. It needs a short, repeatable checklist and the habit of asking the AI to fix what you find.
AI output looks finished faster than it is verified. Test the main journeys yourself on a phone, check text and numbers, and review anything involving money or personal data before you publish.
Test like a customer, not like the builder
Pick the two or three things a visitor must be able to do, such as contact you, book, or order. Walk through each one start to finish, on a phone first, then on a computer.
- Submit every form with real-looking and with empty or wrong data.
- Click every button and menu link.
- Try the back button and refreshing the page mid-flow.
Check the content, not just the code
AI can invent details. Verify names, addresses, opening hours, prices, phone numbers and any claims about your business. Read Arabic text aloud or give it to a native reader, since small wording errors are easy to miss.
Look at layout, speed and accessibility
Resize to a small phone screen, check that text is readable and nothing overlaps. Make sure images have descriptions, contrast is comfortable and pages load quickly on a normal mobile connection.
- No horizontal scrolling on mobile.
- Right-to-left pages mirror correctly.
- Images are not oversized or missing.
Fix in small steps and re-test
Report each problem precisely: where it happens, what you did, what you expected. Ask for one fix at a time and re-test the affected journey, since a change in one place can disturb another.
Example prompt to Uttra: "Review my booking page: submit the form with empty, invalid and valid data, fix any validation or message problems, check it on a small phone screen, and list what you changed."