Sample report

Ciclo Norte: bike rental in Valencia

Study
Full study
Sessions
36 (6 profiles × 3 tasks × 2 formats)
Formats
Desktop 1440px · Mobile 390px
Tasks
Find the price for 2 days · Book a bike for Saturday · Find where to pick it up

First impression

Five seconds on the home page, then: what is this, who is it for, what would you click first?

“Bikes in Valencia… a shop? Tours? I’d tap the big photo but it doesn’t do anything.”

No context · mobile

“Rental, I think. I want the price. I’d click Bikes.”

In a hurry · desktop

“I can read Ciclo Norte and the photo. The grey text under it is too faint.”

Reduced vision · mobile

4 of 6 profiles understood it is a rental. 2 thought it was a shop or a tour company.

The 3 worst problems

  1. 1 / 3 High Affected: 29 of 36 sessions

    Nobody finds the rental prices

    Expected
    “Prices will be on the bike pages.”
    What happened
    Profiles opened Bikes, scrolled each card and left. Prices only exist on the “Rates” page linked in the footer.
    Smallest fix
    Show “from €12/day” on every bike card and rename the footer link “Rates” to “Prices”.
    Before
    City bikeSee details
    After
    City bikefrom €12/dayBook
  2. 2 / 3 High Affected: 14 of 18 mobile sessions

    The date picker hides the “Book” button on mobile

    Expected
    “After choosing Saturday I’ll see a button to confirm.”
    What happened
    The calendar opens full-screen and has no close control. Users tapped outside, lost the dates and started again.
    Smallest fix
    Add a “Done” button at the bottom of the calendar and keep the chosen dates when it closes.
    Before
    Calendar(no way out)
    After
    CalendarDone
  3. 3 / 3 Medium Affected: 11 of 36 sessions

    The pick-up address is only in a map image

    Expected
    “The address will be in Contact.”
    What happened
    Contact shows a static map. The address is not text, so it cannot be read by the reduced-vision profile or copied.
    Smallest fix
    Write the address and opening hours as text above the map and link it to a maps app.
    Before
    [map image]
    After
    C/ Ejemplo 12, ValenciaOpen 9–19h[map]

Problem 1, before and after

Switch between before and after to see the smallest fix.

Before
BikesToursContact
See details
After
BikesToursPrices
from €12/day Book
Example Fictional site, illustrative mockup.

Prioritized findings

FindingImpactEffort
Menu icon has no label; the low-skill profile did not open itMediumLow
“Add helmet” checkbox is 14px and gets missed on imprecise tapsMediumLow
Cookie banner covers the Book button on 390px screensMediumLow
Grey body text fails contrast on the home pageLowLow
Bike sizes use codes (M2, L1) with no height guideLowMedium

Fix prompt

Plain Markdown. Paste it into your coding agent or a ticket. It says what to change, why, how to check it, and what to leave alone.

# Fix 1 of 3: show prices on bike cards

Evidence: 29 of 36 AI agent sessions did not find a price.
Session 07, 00:38-01:25.

## Change
- In the bike card component, show "from {lowest daily price}/day" under the bike name. Read it from the existing rates data.
- Rename the footer link "Rates" to "Prices".

## Check
- Every card on /bikes shows a price at 390px and 1440px.
- Price text contrast is at least 4.5:1.

## Do not touch
Booking logic, the rates themselves, analytics.

Script to confirm with real people

  1. Recruit 3 to 5 people who have rented a bike or plan to. Friends of friends are fine.
  2. Ask them to find the price of a city bike for two days. Do not help. Note where they look first.
  3. Ask them to book for Saturday on their own phone. Watch the calendar step.
  4. Ask where they would pick the bike up. Note whether they find the address.
  5. If 2 or more people hit the same problem, it is confirmed. If nobody does, question the finding.

History

Ship the fix and run the same profiles and tasks again. The history shows which problems are gone, which remain and what the change broke.

  1. Round 1 · 3 May3 worst problems foundBaseline
  2. Re-test · 24 MayPrices and address fixed. The calendar still traps 5 of 18 mobile sessions.2 of 3 fixed

What every report includes

This sample follows the same structure as every report. Each finding links to the moment in the video where it happened, so you can judge it yourself.

  • First impression

    What people think your site is for in the first five seconds, and what they would click first.

    Example“Invoicing software, I think. For accountants?” (it is for freelancers)

  • The 3 worst problems

    Ranked by how many sessions they blocked and how badly. Each with video, screenshots and quotes.

    Example#1 · High · Pricing only in the footer · 4 of 6 sessions

  • Prioritized findings

    Everything else we saw, sorted by impact and effort, so the backlog stays honest.

    ExampleMenu icon has no label · impact medium · effort low

  • Before/after mockups

    A quick picture of the smallest fix, so design and development agree on what changes. On the Full study, Pro and Agency.

    ExampleBefore: “See details”. After: “from €12/day · Book”

  • Fix prompt

    Markdown ready for Claude Code, Codex, Cursor or a human developer: evidence, change, acceptance checks. The top problems on every paid plan; complete on the Full study, Pro and Agency.

    Example# Fix: show prices on the plan cards

  • Script for real people

    A short guide to confirm the findings with three to five real users before you commit to bigger work.

    Example“Ask 3 people to find the Pro price. Don’t help. Note where they look first.”

How a study is run · Real cases

See where people get lost on your site.

Paste your URL. In a few minutes you get the 3 worst problems and one session video.

3 AI agent sessions on your site, the 3 worst problems and a video.