客人
0

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.

Create a mobile website test More website usability checks

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.

任务标题
Test a website menu and enquiry path on a phone
工人应该做什么？
  1. Open the linked website on a phone, not a desktop emulator. Record the phone model, operating system and browser. Use normal portrait orientation.
  2. 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.
  3. 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.
  4. 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.
如何证明结果
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.
Create a task from this example

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：任务和奖励

查看已发布的内容以及工人目前的工资。这可以帮助您为自己的任务设定明确的条款。

Create a mobile website test
0活动任务
0可用完工量
没有可用的任务按完成付款

该领域的活动

查看过去 30 天内有多少活跃客户和工作人员以及接受了多少结果。

最后 30 天
0有未完成任务的客户
0接受的结果
0接受工作的工人
还没有足够的数据每个接受结果的平均支出

计算Find out whether your website is easy to use on a phone的预算

设置完成一次的奖励以及您需要的结果数量。您可以将这些值直接带入创建表单中。

价格给你2 USD

该表格会在发布前再次验证您的最终价格和可用余额。

使用此预算创建任务

提前设定结果数量和奖励

对于测试、调查、反馈和数据工作，您可以定义需要多少结果以及为每个接受的报告支付多少费用。

创建微任务了解按结果付费

选择一个现成的例子

打开合适的选项并添加您的链接、说明、完成次数和奖励。

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.

Everyday conditionsThe worker follows a journey on their phone rather than simply viewing a smaller mockup.
The screen at the problem pointA screenshot shows what hides a button or makes the text difficult to read.
Details for your developerThe phone model, system, browser and sequence of actions help reproduce a problem.
A check after the fixRepeating the journey helps show whether the obstacle is gone on the relevant device.

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.

Menus and navigationAsk the worker to open the menu, reach a section and return. Check for a remaining overlay, lost scrolling and unclear close controls.
Forms and the on-screen keyboardHave the worker tap a field and check whether labels, errors and the next button remain visible. Use a test form or stop before submission, without real personal data.
Elements covering the contentLook at banners, chat widgets, sticky headers and notices. Ask about overlaps, horizontal scrolling and controls that are difficult to tap.

Focused tasks for your mobile website

Separate journeys and device requirements when you want comparable reports and a clearer source of each problem.

Check a form on iPhone or AndroidCreate separate tasks with an explicit system and browser requirement. Ask what happens when the keyboard opens and a test form displays a validation error.
Try the updated menuRepeat the journey from the home page to the specified section. Compare earlier reports and check that fixing one problem has not introduced another.

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.

所有任务
还没有匹配的任务

更改选定的操作、类别或搜索查询。新任务会自动出现。

其他任务类型

如果此选项不适合您，请选择其他类别或返回完整任务列表。

在线订购微任务完成创建 DitWork 微任务：定义操作、奖励、结果数量、说明并审查工作人员报告。商业微任务使用 DitWork 微任务检查网站、应用程序、表单、企业列表、文本、调查或自定义场景，并为接受的结果付费。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.微任务按接受的结果付费创建微任务，并根据接受的结果付费：确切的操作数量、固定价格、工作人员报告和受控预算。
网站测试在真实设备上测试表单、页面、导航和用户旅程。应用程序测试检查安装、屏幕、用户旅程和界面清晰度。机器人、游戏和场景测试机器人、游戏动作和简短的分步流程。登记和表格注册、个人资料填写、表单测试以及注册后的操作。内容反馈检查文章、页面、描述、脚本或说明的清晰度。调查与研究简短的调查、访谈、假设检验和结构化回答。

相关微任务方向

比较相关方向以选择正确的场景、证明格式和预期结果。

用于网站和应用程序测试的微任务向 DitWork 工作人员订购网站、表单、应用程序或用户场景检查，并提供报告、屏幕截图并按结果付费。网站用户反馈由真实用户订购网站检查：页面清晰度、表格、流程、移动版本和存在问题的简短报告。用户反馈通过 DitWork 微任务获取用户反馈：网站、产品、内容、表单、应用程序或服务卡检查。在线订购微任务完成创建 DitWork 微任务：定义操作、奖励、结果数量、说明并审查工作人员报告。商业微任务使用 DitWork 微任务检查网站、应用程序、表单、企业列表、文本、调查或自定义场景，并为接受的结果付费。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.

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.