Website user acceptance testing is the owner's final check that the site works as agreed before sign-off. In about 30 minutes, test it on your own phone, submit every form, place a test order, click every button and link, read every page for errors and check contact details. Report issues in one list, then sign off in writing.
Key Takeaways
- Acceptance testing checks the site against the agreed scope, from a customer's point of view.
- Test on your own phone first, then a computer.
- Submit every form and place a real test order or booking.
- Read every page for wrong prices, numbers and addresses.
- Report issues in one numbered list, and sign off in writing once fixed.
What Is Website User Acceptance Testing?
Developers test as they build, but the owner knows the business best: the right prices, the correct phone number, how customers actually behave. Website user acceptance testing, often shortened to UAT, is the stage where you check that the site does what was agreed before you sign it off and make the final payment. It does not need technical skills. It needs about half an hour, your phone and a checklist.
Testing is the last step in the hiring journey that begins with selecting a web development company. It complements our full website launch checklist.
What Is in the 30-Minute Check?
| Minutes | Check | What to look for |
|---|---|---|
| 0 to 8 | Phone layout | Every page on your own phone: readable text, tappable buttons, no sideways scrolling |
| 8 to 13 | Forms | Submit each form; confirm the email arrives and the visitor sees a thank-you message |
| 13 to 18 | WhatsApp and calls | Tap every WhatsApp and phone button; check the number and pre-filled message |
| 18 to 23 | Payments or bookings | Place a test order or booking with each payment method; check confirmations |
| 23 to 27 | Content | Read prices, addresses, hours, names and spelling on every page |
| 27 to 30 | Speed and links | Open pages on mobile data; click menu items and footer links |
Why Start on a Phone?
Most of your visitors will use phones, often mid-range Android models on mobile data. Test on your own phone using mobile data rather than office Wi-Fi to see what customers see. Rotate the screen, try the menu, and check that pop-ups can be closed easily.
How Do You Test Forms and Orders Properly?
Use realistic details. For forms, check where the email goes, whether it reaches the inbox rather than spam, and whether the person filling it in gets a confirmation. For stores, place an order with each payment method, including cash on delivery, and check order emails, stock reduction and the admin view. Ask the developer how to cancel test orders afterwards. Our guide to emails going to spam helps if notifications are missing.
What Content Errors Are Most Common?
- Old or placeholder prices.
- Wrong phone numbers, especially one digit off.
- Placeholder text such as "Lorem ipsum" left on inner pages.
- Outdated hours, including Friday or Ramadan timings.
- Staff or services that no longer exist.
- Broken or missing images.
How Should You Report Issues?
Make one numbered list with the page, the device, what you expected and what happened, plus a screenshot. Mark each issue as blocking (must fix before launch) or minor. Send the list once, not piece by piece. Items that were never in scope are change requests, not defects; our change requests guide explains the difference.
When Should You Sign Off?
Sign off in writing once blocking issues are fixed and you have rechecked them. At handover, confirm you have all logins, that the domain and hosting are in your name and that you have a backup. Our handover checklist lists everything to collect. Sign-off usually triggers the final milestone payment, after which, in our projects, the code becomes yours.
What If You Are Testing From Abroad?
Overseas owners should also ask someone in the target market to test, because speed, payment methods and phone formats differ. Share a short checklist and ask for screenshots.
What About Test Data?
Use your own details or clearly fake ones for tests, never real customers' data. Ask the developer to remove test orders and form entries before launch.
How We Handle Acceptance
Every project we deliver, from Rs 40,500, includes an acceptance checklist and a fix round before final payment. See our contact page.
Frequently Asked Questions
- web.dev — Core Web Vitals
- W3C WAI — Easy checks: a first review of web accessibility
- Google Search Central — Mobile site and mobile-first indexing
How we researched this: The 30-minute checklist and reporting method are editorial; timings are a guide. Code ownership after final payment is an approved business fact about our projects. Our prices come from the published list.
About to sign off a new website?
Message us on WhatsApp for a fixed quote, or see our published pricing first.