ADVANCED · WEBSITE

Test whether your website helps visitors

A recorded usability test, one measured improvement and a repeat check.

Start step one ↓My learning →Prompt library →
A website displayed on a laptop at a bright wooden desk.

What you need

A working site and a few willing testers. You can use a notebook; analytics software is optional.

These guides are free. Use the free/manual route for practice; optional upgrades are your choice. Account access and app screens can vary.

Words you might not know
Usability test
Watch someone try a real task on your site.
Baseline
The result before you make a change.
Tools that fit this task

Choose one starting tool. You do not need every product here. Check its current plan before starting; these are editorial matches, not measured product rankings.

  • For a visual website builder; check publishing and custom-domain costs.

  • For drafting page copy from your own facts.

0 of 3 steps checked

STEP 1 OF 3Define one visitor task

Choose an action you can observe, such as finding a service or reaching a contact page.

  1. Write the task without naming the link to press. Choose a success condition and a point where the test ends.
  2. Invite up to five willing people to try it individually on a phone. Explain that you are testing the site, not them.
  3. Record success, obstacles and approximate time. Do not prompt them during the task or collect private details in your notes.
Example to follow
Task: Find how to ask about a drawing session
Success: Reach the public contact route
Baseline example: 2 of 5 found it without help
These numbers are fictional practice data.
Go to step 2 ↓
STEP 2 OF 3Change the biggest obstacle

One focused change makes the result easier to interpret.

  1. Group the observed problems. Pick the one that blocked the most people from finishing.
  2. Change one thing, such as the menu label or location of the next-action link. Keep a copy or record of the original.
  3. Check the changed page on phone and desktop. Test links and keyboard focus before publishing.
Example to follow
Observed obstacle: “Let’s talk” was not recognised as Contact.
Change: Rename it “Contact” in the main menu.
Keep the page content the same for this test.
Go to step 3 ↓
STEP 3 OF 3Repeat and decide what to keep

A small test can reveal problems, but it cannot prove that every visitor will behave the same way.

  1. Repeat the same task with new willing testers where possible. Use the same success condition.
  2. Compare successes and obstacles with the baseline. Note if the people or devices differed.
  3. Keep, adjust or undo the change based on the evidence. Put one follow-up test in your calendar. If nobody is available yet, keep your test plan ready and do not invent results.
Example to follow
Review template
Before: __ successes out of __
After: __ successes out of __
What differed: __
Decision and reason: __

That is your three-step guide. Keep practising, or try the next level when you feel ready.

Keep a quick note

Saved only in this browser when storage is available. Clearing browser data removes it.

What next?

Try the same process on your next project. Use the evidence you collect to choose the next small improvement.

Choose another advanced guide →

Official help if your screen looks different

Our examples and practice tasks are original. These references support the platform instructions. Checked 17 October 2026; screens and account features may change.

Photo credits

Workspace and creative photography from Unsplash.

THE OTHER FEW

Find the few things worth knowing.

Explore AI tools, software and technology through official sources, clear trade-offs and practical comparisons, so you can find the few that matter to your task.

Popular searches:

🔥 Fresh Few

Recently added to our catalogue, with a reason to explore each one.

💎 Hidden Gems

Editorial alternatives with a specific reason to consider them.

📊 Popular Categories

More from The Other Few
Personal Few

Build the few tools that work together.

Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.

Stack suggestions are task-fit decisions, not product rankings. Commercial relationships must never change compatibility.
READY

Tell us the outcome.

We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.

Evidence-first: current pricing, feature availability and platform support should be shown only when verified from an appropriate source.
THE OTHER FEW · INTELLIGENCE LAYER

From task to decision.

The shortlist now explains the fit, the trade-offs and what to do next.

PERSONALISED FIT
✦

Task understanding

Translate natural-language goals into task signals before matching products.

GoalUse caseConstraints
◎

Compatibility

Show why a tool fits this search instead of presenting a permanent product score.

PlatformExperiencePriority
↗

Decision path

Move naturally from shortlist to profile, alternatives, compare and saved tools.

ExploreCompareSave
DISCOVERY

Go beyond the shortlist.

Browse editorial collections when you want to explore rather than solve one task.

Fresh FewOnly products with a genuine freshness signal.Explore →
Hidden GemsInteresting products that deserve a closer look.Explore →
Popular CategoriesStart with the job, then narrow to the Few.Browse →
VERIFIED SOURCES · EDITORIAL FIT · NO PAID RANKING
RECOMMENDATION GRAPH

See why the Few connect.

The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.

GRAPH ACTIVE
YOUR TASKgoal + constraintsTASKFITTOOLEVIDENCE intentexperienceplatformpriorityproductalternativesourcefreshness
EXAMPLE DECISION PATH
1 · GoalBuild a website for a small business.
2 · ConstraintsBeginner · web · low-code · ease.
3 · Candidate setReplit · Lovable · Claude — narrowed before presentation.
4 · Trade-offLovable favours simplicity; Replit offers more control; Claude is broader rather than purpose-built for the build.
Compatibility is task-specific. It is not a permanent product rating.

Graph signals

These are the relationships the engine can reason over as the catalogue grows.

Goal / intentConstraintTask fitAlternativeWorkflow overlapEvidenceFreshnessSaved context
Important: the graph does not invent evidence. Unsupported claims remain unsupported until verified.
PERSONAL DECISION LAYER

Make the decision smaller.

Bring your goal, saved tools, workflows and fresh changes together. The Other Few narrows the decision without pretending there is one universal winner.
● Decision context ready
Launch a businessBuild a websiteCreate videosResearch & decide
GoalWaiting
ConstraintsWaiting
Your FewLocal saves
ChangesFreshness ready
Start with the outcome.

We'll turn it into a smaller, clearer decision using the intelligence already built into The Other Few.
Fit is contextual. Editorial judgement, evidence and commercial relationships remain separate.Private on this device.
Intelligence Core
Make the catalogue smarter, not just bigger.
The intelligence layer now treats products, tasks, constraints, alternatives and workflows as connected evidence. Expansion is staged into verification lanes rather than filling the catalogue with unverified entries.
18 core records · verification-first
18Core records
7Categories covered
14Relationship types
0Fabricated records

Connected catalogue

Core products are connected to the tasks and categories they are already structured to serve.

Expansion lanes

These are research lanes, not unpublished product claims. A lane becomes catalogue data only after source verification and taxonomy review.
Editorial rule: catalogue breadth never outranks evidence quality. A product can enter the research queue without entering the public Few.
Intelligence Core

One brain. Every decision.

The catalogue, Finder, Decision Engine, workflows, Your Few and freshness signals now have a shared conceptual layer. The goal is not more results — it is better decisions with fewer tools.
● CORE MODEL READY

Decision graph

The same product can play different roles depending on the user's outcome and constraints.
18core products
7active categories
0saved tools
0watched tools
GoalOutcome
IntentTask
ConstraintsFit limits
ProductsCatalogue
DecisionFew