Find out whether your website is easy to use on a phone
It works on your screen. A visitor's phone may tell a different story.A menu covers a button, the keyboard hides a field, or a popup prevents progress. Small obstacles can make someone leave even when they like your offer. Give workers a short mobile website journey and ask them to show the screen when they encounter difficulty. Testing on ordinary phones can reveal issues that are easy to miss in a mockup or browser emulator, helping you make the resource more usable for new visitors.
A ready-to-edit microtask brief
This is an editable draft, not a published task. Add your resource link, adjust the conditions, and choose the reward and number of completions.
- Task title
- Test a website menu and enquiry path on a phone
- What should the worker do?
- Open the linked website on a phone, not a desktop emulator. Record the phone model, operating system and browser. Use normal portrait orientation.
- Open the menu and find the section specified by the customer. Close the menu, scroll the page and check whether banners, chat or a sticky header cover the text.
- Open the enquiry form, tap a field and check whether the field and button remain visible with the keyboard open. On the live website, do not submit the form or enter real personal data.
- Describe whether you completed the journey. For any difficulty, name the page and the preceding action, and attach a screenshot. If everything worked, list what you checked and show the final screen.
- How to prove the result
- Include the phone model, system and browser, the steps checked, and a screenshot of the final screen or problem. Hide notifications and personal data. Comments must relate to the specified journey; a report with no errors is acceptable.
Decide what to fix in the mobile version
Group reports by page, action and device. Prioritise situations where someone cannot reach a section, read the terms or continue filling in a form. Give the developer steps and screenshots, not just a phone model. After a fix, repeat the affected journey in similar conditions and on another device. Do not diagnose website speed from one person's impression: loading performance needs separate technical measurements.
Workers are paid for testing and reporting, not for purchases or favourable opinions. Their feedback can reveal problems, but cannot guarantee more sales or higher search rankings. A small group of paid testers does not replace research with your target audience.
Find out whether your website is easy to use on a phone: tasks and rewards
See what has already been posted and what workers are currently paid. This can help you set clear terms for your own task.
Activity in this area
See how many clients and workers were active and how many results were accepted during the last 30 days.
0customers with open tasks
0accepted results
0workers with accepted work
Not enough data yetaverage payout per accepted result
Calculate the budget for Find out whether your website is easy to use on a phone
Set the reward for one completion and the number of results you need. You can carry these values directly into the creation form.
Set the number of results and reward in advance
For testing, surveys, feedback, and data work, you can define how many results you need and how much you will pay for each accepted report.
Choose a ready example
Open a suitable option and add your link, instructions, number of completions, and reward.
Test a website scenario
Navigation, form, registration, mobile version or customer journey.
Collect customer feedback
First impression, offer clarity, trust and reasons for abandoning the action.
Test a mobile application
Installation, launch, main scenario, errors and a screenshot report.
Run a survey
Short questionnaire, hypothesis validation, option selection or audience opinion.
Verify data
Links, spreadsheet rows, listings, public information and discrepancy checks.
Create a custom microtask
Any small task with clear steps and a result that can be reviewed.
What testing on phones can tell you
Find awkward buttons, obscured forms and mobile menu problems. Use DitWork microtasks to check your mobile website with people on their phones.
Related checks for improving your resource
Choose a nearby problem to investigate next. Each guide includes an editable brief, reporting requirements and ideas for turning observations into changes.
Help visitors find what they came for Find out whether visitors can locate a product, service or useful information. Test your website menu, search and filters with an editable DitWork microtask brief. See your online store through a shopper's eyes Find out what gets in the way of a purchase. Use DitWork microtasks to test product search, product pages, the shopping cart and checkout with users. Find out what stops visitors enquiring on your landing page See your landing page through a new visitor's eyes. Collect feedback on the opening screen, trust and the enquiry journey with DitWork microtasks. Help first-time users find their way around your app Check first launch, registration and the path to a useful app feature. Collect clear first-time user reports with DitWork microtasks.
Start with the actions people visit your site to complete
A responsive image does not automatically make a website usable. The question is whether someone can find what they need and finish their journey on a phone.
Focused tasks for your mobile website
Separate journeys and device requirements when you want comparable reports and a clearer source of each problem.
Tasks from the website testing category
The general list shows how customers describe tests. Not every task below is for phones; use the brief above for your own mobile website.
No matching tasks yet
Change the selected action, category, or search query. New tasks appear automatically.
Other task types
If this option is not right for you, choose another category or return to the full task list.
Order microtask completion onlineCreate DitWork microtasks: define the action, reward, number of results, instructions and review worker reports.Microtasks for businessUse DitWork microtasks to check a website, app, form, business listing, text, survey or custom scenario with payment for accepted results.Launch your project with microtasksShow a new website, app, or service to its first users before the big launch. Collect genuine impressions, test essential actions, and fix what gets in the way of discovering the project.Promote your project with microtasksHelp people discover your website, app, community, or product. Create clear tasks, receive meaningful actions and honest feedback, and pay only for accepted results.Revive your project with microtasksGive a website, app, community, or service a second life. Discover what feels outdated, why people leave, and which changes can make the project interesting again.Microtasks with payment per accepted resultCreate microtasks with payment per accepted result: exact action quantity, fixed price, worker report and controlled budget.
Website testingTest forms, pages, navigation, and user journeys on real devices.App testingCheck installation, screens, user journeys, and interface clarity.Bots, games, and scenariosTesting bots, game actions, and short step-by-step flows.Registrations and formsRegistration, profile completion, form testing, and actions after signup.Content feedbackReview the clarity of an article, page, description, script, or instruction.Surveys and researchShort surveys, interviews, hypothesis checks, and structured responses.
Questions about mobile website testing
Why use a phone when there is an emulator?
An emulator is useful for quick layout checks. A real phone also reveals interactions with the keyboard, browser bars, touch controls and device settings. The two approaches complement each other.
Can I specify a system or browser?
State the requirements in the title and instructions and ask for device details in the report. Use separate tasks for different systems. Suitable worker availability and completion speed cannot be guaranteed in advance.
Is this a complete responsiveness and speed audit?
No. A microtask checks a selected user journey. Full screen coverage, accessibility, performance and security require a separate technical audit. Reports can help identify where that audit is most needed.
