Review the homepage for any visual issues: broken images, layout problems, overlapping elements, or unreadable text.
Check that all navigation menu links are visible, clickable, and correctly labeled.
Navigate to the Contact page (via the navigation menu or any visible link/button).
Confirm the Contact page loads correctly and displays all expected content (contact form, email address, phone number, social links, map, etc.).
If a contact form is present, fill it in with test/dummy details and attempt to submit it. Note whether validation messages appear for missing or incorrect fields.
Check the form submission response (success message, error message, or redirect).
Note any broken links, console errors, or unexpected behavior encountered throughout the journey.
Please report on:
Any visual or layout bugs on the homepage or contact page.
Navigation issues or broken links.
Contact form usability, validation, and submission behavior.
Overall page load speed and responsiveness on your device/browser.
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 512 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $10.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://www.optimalways.com/
Test the journey from the Optimalways homepage through to the contact page. Follow these steps:
1. Open https://www.optimalways.com and confirm the homepage loads correctly and within a reasonable time.
2. Review the homepage for any visual issues: broken images, layout problems, overlapping elements, or unreadable text.
3. Check that all navigation menu links are visible, clickable, and correctly labeled.
4. Navigate to the Contact page (via the navigation menu or any visible link/button).
5. Confirm the Contact page loads correctly and displays all expected content (contact form, email address, phone number, social links, map, etc.).
6. If a contact form is present, fill it in with test/dummy details and attempt to submit it. Note whether validation messages appear for missing or incorrect fields.
7. Check the form submission response (success message, error message, or redirect).
8. Note any broken links, console errors, or unexpected behavior encountered throughout the journey.
Please report on:
- Any visual or layout bugs on the homepage or contact page.
- Navigation issues or broken links.
- Contact form usability, validation, and submission behavior.
- Overall page load speed and responsiveness on your device/browser.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot. Speak your findings aloud while recording whenever you can: narration is strongly encouraged and makes your report far more useful, but it is not required and a quiet recording will still be reviewed on its merits.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
•
Access to a device that can open the target URL
•
Report every issue with a severity and exact reproduction steps
•
Only submit evidence you captured yourself during this run