How Website Testing Works: A Step-by-Step Guide

Website and app testing is the most demanding of the common paid research formats, and generally the best compensated per session. You are not giving an opinion about a design; you are producing a usable recording of a real person attempting real tasks, narrating their reasoning out loud. Understanding what reviewers accept is the whole difference between approved tests and rejected ones.

What a test session actually looks like

1. 1

   1. Invitation and screener

   You receive a test invitation with an estimated length. A short screener checks device, region, and whether you match the target user — for example someone who has booked travel online recently.

2. 2

   2. Technical check

   You confirm screen recording permission and microphone access. Audio is where most rejections originate, so test it before you accept work.

3. 3

   3. Task scenarios

   You are given tasks one at a time: find a product, complete a signup, locate a policy, compare two plans. You attempt them on the live site or prototype.

4. 4

   4. Thinking aloud

   You narrate continuously — what you expect, what you are looking for, what confused you, what you would do next. Silence is the single most common quality failure.

5. 5

   5. Follow-up questions

   Written or spoken questions at the end, often asking for a rating plus an explanation.

6. 6

   6. Submission and review

   The recording uploads and is reviewed for completeness and audio quality. Rejected tests are usually unpaid, though some platforms allow a redo.

7. 7

   7. Payment

   Paid per approved test, on the platform's stated schedule.

Moderated vs unmoderated

Equipment and setup

• A computer or laptop for desktop tests; a tablet or mobile phone for mobile tests
• A microphone that records clearly — a basic headset beats built-in laptop mics
• A quiet room with no background TV, traffic, or family conversation
• A stable internet connection, ideally wired or close to the router
• Any platform-required recorder or browser extension, installed and tested in advance
• Screen free of private tabs, notifications, and personal information before recording

How to produce a test that gets approved

Why tests get rejected

• Inaudible or missing audio
• Long silences with no explanation of what you are doing
• Tasks skipped without comment
• Session far shorter than the stated length
• Recording failure caused by an untested setup
• Answers that describe your preferences instead of the experience of the tasks

Availability and earnings expectations

Usability tests often carry a better activity rate than short surveys because the work is harder and the eligible pool is smaller. That does not make it a predictable income: tests require particular devices, regions, and user profiles, and available slots fill within minutes. Platforms publish their own per-test compensation and payment timing in participant documentation — read the current version rather than a figure quoted second-hand. To judge whether it is worth your time, calculate the effective hourly rate including screening and setup: Total Earnings ÷ Total Time Spent × 60.