---
title: "Help me check my website: a plan for an afternoon · Proxy Mail QA"
description: "A step-by-step plan for checking a whole website: as a visitor, on a phone, its forms and emails, speed, accessibility, search and security."
url: https://proxymail.qa/solve/help-me-check-my-website
---

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

# Help me check my website

You can check most websites properly in an afternoon. Work through these in order: the first steps find the problems that cost you visitors, the later ones the problems that cost you search traffic or trust.

Updated 5 November 2026

> **Our recommendation, up front.** We make Proxy Mail QA, so we’re not neutral. This is a plan for checking a whole website, and most of it doesn’t need Proxy Mail QA at all. We recommend it for the steps that depend on an email: signing up, signing in with a code or link, resetting a password, invites, and the confirmations your forms send. For speed, accessibility, links, search and security, we name free tools that aren’t ours. Proxy Mail QA doesn’t judge design or wording, and doesn’t receive SMS.

## 1\. Use it like a visitor (15 minutes)

On your phone first, then a laptop, go through every page as someone who’s never seen the site:

- Can you tell in five seconds what the site is for and what to do next?
- Does every button and link do what it says?
- Does anything look broken, overlap, or sit under the phone’s keyboard?
- Is anything slow enough that you’d give up?

Write down everything, however small. This finds more than any tool.

## 2\. Every form

For each form (contact, newsletter, sign-up, booking, checkout):

- Submit it empty, then with a mistake. Each error should appear at the field, in words.
- Submit it properly. The page should say what happens next.
- If it sends an email (a confirmation, a receipt, a “we’ll be in touch”), check it arrives, reads well and its links work.

Use a new [Proxy Mail QA](https://app.proxymail.qa/?mode=signup) test address for each form, so you can tell which email came from where and none of it reaches your own inbox. Checking marketing emails and unsubscribing as well is possible with Marketing and offer emails switched on in [Labs](https://proxymail.qa/labs).

## 3\. Accounts, if your site has them

This is where Proxy Mail QA does most of its work:

1. **Sign up** with a new test address. With [Proxy Mail QA for Chrome](https://proxymail.qa/chrome-extension), one click fills the email, name, username, date of birth and password, and the verification code shows in the page when it arrives.
2. **Verify**, then check you’re signed in.
3. **Sign out and sign in again.** The extension offers the test account and its saved password.
4. **Reset the password**, and check the old one stops working.
5. **Change the email address**, if your site allows it, and check both the old and new addresses are told.
6. **Read each email once in full** in the app: the sender, the subject, every link. A link to `localhost` on a staging site is flagged.

## 4\. Speed

Run Lighthouse (Chrome DevTools → Lighthouse, on mobile) on your home page and the two pages that matter most, such as pricing and sign-up. Fix the largest items first; they’re usually images. PageSpeed Insights adds real visitors’ data once you have traffic.

## 5\. Accessibility

- Run axe DevTools or WAVE on the same pages.
- Use each page with the keyboard alone: Tab through it, and check you can always see where you are.
- Try a form with a screen reader (VoiceOver on a Mac or iPhone, NVDA on Windows).

Automated tools find some problems, not all. The keyboard and screen reader find the rest.

## 6\. Links and pages

- Run a link checker (the W3C Link Checker, or a crawler such as Screaming Frog) and fix broken links.
- Visit a page that doesn’t exist. Your 404 page should help people back.

## 7\. Search

- Each page has its own title and description.
- Your site is in Google Search Console, with a sitemap submitted.
- Pages you don’t want found (staging, admin) aren’t indexed.

## 8\. Security basics

- Every page loads over HTTPS. Qualys SSL Labs checks the set-up, and Security Headers checks the headers.
- No secret keys in the page’s source or JavaScript.
- Admin pages need a sign-in.
- `npm audit` or Dependabot, if your site has packages.

This isn’t a security test. If your site handles payments or personal data, get one done properly.

## 9\. Trust and legal

- A privacy policy and terms that match what the site actually does.
- A way to contact you.
- A cookie notice, if you use cookies that need one where your visitors are.

## 10\. After launch

- An uptime monitor (UptimeRobot, Better Stack) to tell you when the site is down.
- Error tracking (Sentry), so you see what broke before someone emails you.

## Which steps Proxy Mail QA helps with

| Step                                                | Proxy Mail QA?                                                                       |
| --------------------------------------------------- | ------------------------------------------------------------------------------------ |
| 1\. Use it like a visitor                           | No                                                                                   |
| 2\. Every form                                      | Yes, for the emails they send                                                        |
| 3\. Accounts                                        | Yes: test addresses, the codes and links, saved test passwords, checks on each email |
| 4\. Speed, 5\. Accessibility, 6\. Links, 7\. Search | No                                                                                   |
| 8\. Security basics                                 | No. It checks how your emails are signed (SPF, DKIM, DMARC), not your site           |
| 9\. Trust and legal, 10\. After launch              | No                                                                                   |

## Ask your agent to do it

If you build with Qoder, connect Proxy Mail QA from the [Qoder Marketplace](https://qoder.com/en/marketplace/connector?id=proxymail-qa) (or install its plugin, which adds eight skills, among them **account-email-audit**), then ask:

Prompt

```text
Check my site at https://staging.acme.dev. Start a Proxy Mail QA run.
1. Trigger every account email the site sends (sign-up verification and its resend,
   password reset, sign-in code or link, invite, email change) with new test
   addresses, check each with check_email, and list what to fix.
2. Submit the contact form with a new test address and check the confirmation email.
3. Run Lighthouse on mobile for the home, pricing and sign-up pages.
4. Check every internal link.
Finish the run and give me one list, most serious first: things that are broken, then
confusing, then slow.

```

## What to fix first

1. **Broken**: someone can’t sign up, the email doesn’t arrive, a form loses what was typed, a page errors.
2. **Confusing**: people can’t tell what to do next, or an error doesn’t say how to fix it.
3. **Slow**: pages that take more than a few seconds on a phone.
4. **Everything else.**

For the toolkit in one place, see [Tools to help build and check my website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website).

## 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-help-me-check-my-website)

## 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 sign-up page by handA checklist for your browser and phone, in the order that finds the most problems.](https://proxymail.qa/solve/how-to-review-my-sign-up-page)
- [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)
- [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)