---
title: "How to review my sign-up page: a checklist you can do by hand · Proxy Mail QA"
description: "A sign-up page review you can do by hand in your browser: the form, errors, phones, the verification email and what happens after."
url: https://proxymail.qa/solve/how-to-review-my-sign-up-page
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# How to review my sign-up page: a checklist you can do by hand

A sign-up page review is worth doing slowly, once, before you hand it to anyone. This is the order that finds the most problems for the least effort.

Updated 5 November 2026

> **Our recommendation, up front.** We make Proxy Mail QA, so we’re not neutral. In this checklist we recommend it for two steps: filling the form with a fresh test account in one click, with Proxy Mail QA for Chrome, and getting the verification code or link without using your own inbox. Most of the checklist needs no product at all, just your browser, a phone and a few free tools we name along the way. Proxy Mail QA doesn’t judge your design, wording, accessibility or speed.

## 1\. Before you start

- **Use a staging or local copy**, not your live site, so test accounts don’t end up among your real users.
- **Use a new email address for every attempt.** Signing up twice with the same address tests the “already registered” path, not the sign-up. Your own Gmail with a plus tag works for one or two tries, but the emails mix with your personal mail and some apps refuse plus tags.
- **Have the password rules to hand**, from the code or the auth service’s settings, so you can check what the page says against what it does.

## 2\. Look before you type

- Is every field needed? Each extra one costs sign-ups. Ask why the phone number or company name is there.
- Does every field have a visible label, not only placeholder text that disappears when you type?
- Are the password rules shown before someone types, not only after they get it wrong?
- Is there a link to sign in for people who already have an account, and to your terms and privacy policy?
- Is it clear what happens next: “We’ll email you a code”?

## 3\. Fill it in once, the way a new customer would

With [Proxy Mail QA for Chrome](https://proxymail.qa/chrome-extension) (free, for Chrome, Edge, Brave and Arc):

1. Open your sign-up page, click the extension in the toolbar and choose **Turn on for this site**. Chrome asks for access to that one site; it runs nowhere else.
2. Click the Proxy Mail QA button in the email field and choose to fill with a new test account. It fills email and confirm email, first and last or full name, username, date of birth and the password and its confirmation, with a password that fits the field’s length and pattern rules. Company, phone and other fields are left for you to type.
3. Submit. The extension asks whether to save the password to the test address, so you can sign in as that account later.
4. When the email arrives, the code appears in a card on the page, with **Fill** and **Copy**. A verify link gets **Open**, in a new tab.

Without the extension, create an address at [app.proxymail.qa](https://app.proxymail.qa/?mode=signup) and copy it in; the code or link shows on its row when the email lands. To try it first, there’s a [practice sign-up page](https://app.proxymail.qa/demo?page=signup).

## 4\. Break it on purpose

Each of these should give a clear error at the field, in words, without clearing what was typed:

- Submit with everything empty.
- An email with no @, or two.
- A confirm email or password that doesn’t match.
- A password that breaks the rules. The extension’s card offers **Edge-case password** with a list marked “Should be rejected”, made to fit your field’s own limits.
- A name such as `O'Brien`, `José` or `李`, which should be accepted. The card’s **Edge-case first name** has more, including HTML such as `<b>Jane</b>`, which should be shown as plain text.
- An address that’s already registered. Decide whether the page should say so, or say “Check your email” either way so nobody can find out who has an account.
- Double-click the submit button. You should get one account and one email.

Check the errors are announced, not only coloured red, and that the cursor goes to the first one.

## 5\. Read the email

Open the test address in the app and read the whole email once:

- Is the sender name your product, and the subject clear?
- Does every link go to the site you’re testing? A link to `localhost` on a staging site is flagged on the address’s row. [How to fix it](https://proxymail.qa/solve/localhost-links).
- If it says how long the code or link lasts, is that true?
- Does it read well on a phone?

Then use the code or link and check you end up signed in.

## 6\. After sign-up

- Sign out and sign in again. On a sign-in form the extension offers your test accounts, the ones used on that site first, and fills the email with its saved password.
- Reset the password, and check the old one stops working.
- Note what you found on the test address, so it stays with that account for whoever looks next.

## 7\. On a phone, and without a mouse

- Open the page on a real phone, or in your browser’s device mode. Does the email field bring up the keyboard with @? Is anything cut off or hidden behind the keyboard?
- Fill the whole form with the keyboard alone: Tab through it, tick boxes with Space, submit with Enter.
- Run Lighthouse (built into Chrome DevTools) and axe DevTools or WAVE for accessibility problems, and try the form with a screen reader such as VoiceOver or NVDA.
- Check fields have `autocomplete` attributes (`email`, `new-password`, `given-name`), so password managers and browsers fill them properly.

## What Proxy Mail QA doesn’t cover

- How the page looks, reads and converts. That’s your judgement, or your users’.
- Accessibility, speed and SEO: use the tools in step 7.
- SMS codes and social sign-in: it receives email only.
- Fields only your app has, such as “How did you hear about us?”: you type those yourself.

Once the page passes by hand, you can have an agent repeat these checks on every change: see [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review).

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-how-to-review-my-sign-up-page)

## Related guides

- [Test sign-up and email verificationA fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.](https://proxymail.qa/solve/email-verification-testing)
- [Test OTP and one-time login codesCodes pulled out of the email with a Copy button and a countdown when the email says how long they last.](https://proxymail.qa/solve/otp-code-testing)
- [Test magic links and passwordless sign-inSingle-use links that are never opened or prefetched on our side, so they still work when you click them.](https://proxymail.qa/solve/magic-link-testing)
- [Test password reset emailsRequest, receive and use reset links, and keep the new password saved next to the test account.](https://proxymail.qa/solve/password-reset-testing)
- [Stop sharing one Gmail inbox for QAPrivate, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.](https://proxymail.qa/solve/shared-test-inbox)
- [Take QA notes by voice with Wispr FlowDictate what each test account is for, its state and what you found, straight into its notes, in seconds.](https://proxymail.qa/solve/voice-notes-wispr-flow)
- [Verification link points to localhost:3000Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.](https://proxymail.qa/solve/localhost-links)
- [Common Supabase sign-up and login problemsEmails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.](https://proxymail.qa/solve/supabase-auth-problems)
- [Common Firebase sign-up and login problemsMissing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.](https://proxymail.qa/solve/firebase-auth-problems)
- [Sign-up and login problems in vibe-coded appsThe login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.](https://proxymail.qa/solve/vibe-coded-login-problems)
- [Test sign-up emails in PlaywrightA complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.](https://proxymail.qa/solve/playwright-email-tests)
- [Test sign-up emails in CypressA complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.](https://proxymail.qa/solve/cypress-email-tests)
- [Test sign-up emails with pytestA complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.](https://proxymail.qa/solve/pytest-email-tests)
- [Test coupon codes and welcome offersThe coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.](https://proxymail.qa/solve/coupon-code-testing)
- [Test unsubscribe links and one-click unsubscribeThe unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.](https://proxymail.qa/solve/unsubscribe-testing)
- [Test that a welcome offer can't be claimed twiceVersions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.](https://proxymail.qa/solve/welcome-offer-abuse)
- [AI sign-up page reviewLet an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.](https://proxymail.qa/solve/ai-sign-up-page-review)
- [AI registration page reviewAn agent tries every field with values made for it, then finishes the registration through the email.](https://proxymail.qa/solve/ai-registration-page-review)
- [Review a simple sign-up form12 checks for a form with an email, a password and perhaps a name.](https://proxymail.qa/solve/review-a-simple-sign-up-form)
- [Review a multi-page sign-up formOne test account across every screen, and the verification email wherever it comes.](https://proxymail.qa/solve/review-a-multi-page-sign-up-form)
- [Review a financial sign-up formThe emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.](https://proxymail.qa/solve/review-a-financial-website-sign-up-form)
- [An email address for testing registrationA new, real address for every registration try, with the code or link ready to use.](https://proxymail.qa/solve/email-for-checking-my-registration-form)
- [An email address for testing sign-inTest accounts with saved passwords and an inbox for codes, magic links and resets.](https://proxymail.qa/solve/email-for-checking-my-sign-in-form)
- [How long should a password be?NIST's numbers for password length and rules, and test passwords to check yours.](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be)
- [No error for a password that breaks the rulesThe eight usual causes of a silent password field, and how to tell which one it is.](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors)
- [Help me check my websiteA whole-site check in an afternoon, in the order that finds the costliest problems first.](https://proxymail.qa/solve/help-me-check-my-website)
- [Tools to build and check a websiteA toolkit by area, most of it free and none of it ours, except for account emails.](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website)
- [What tools do I need for a website?The full list, then which parts a simple site can skip.](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website)

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)