Guide
How to get honest feedback on your website
Asking "what do you think of my site?" gets polite, useless answers. Better feedback comes from the right people, a specific question, and a method that fits whether you have traffic yet. Here are six common methods, what each is good for, and what each misses.
How do I get feedback on my website?
Match the method to your stage. Before you have traffic, give people from your audience a specific task: in person, in a community, or with simulated visitors that use the site. Once you have traffic, session replay and heatmaps show what real visitors do, and a short on-site survey asks them why. For decisions that matter, watch real people from your audience try the site.
Why most website feedback is useless
The people easiest to ask, friends, colleagues and other founders, know too much and want to be kind. Open questions get opinions about colours. And feedback from people who are not your customers is advice about a different business. Good feedback needs the right reader, a concrete task, and some way to tell a pattern from one person's taste.
- Six methods compared: who gives the feedback, what it needs, what it misses.
- How to ask so people tell you what is wrong, not what is nice.
- Which methods need traffic, and which work before launch.
- How to tell a pattern from one person's preference.
Friends, colleagues and other founders
Free and fast, and good for typos, broken links and obvious confusion. The problem is that they know what you do, and they are on your side. They will rarely tell you that the main heading means nothing to them.
Get more out of them by giving a task instead of asking for an opinion: "Find out how much this costs", or "Tell me in one sentence what this company does". Then stay quiet and watch.
Communities
Founder forums, subreddits, and Slack or Discord groups for your niche can give blunt, outside feedback, and some have threads set aside for it. Read each community's rules on self-promotion first, and ask a specific question.
The catch is who answers. Community members are often builders and marketers rather than your customers, so their feedback leans toward craft: design polish, copywriting rules. Useful, but not the same as a buyer's reaction.
Session replay and heatmaps
Tools in this category record what real visitors do on your site: how far they scroll, where they click, where they hesitate. Hotjar, now part of Contentsquare, is a well-known example. They show real behavior at scale, and they are the best way to find where people struggle once you have traffic.
They need traffic, they show what people did rather than why, and someone has to watch the recordings. Pair them with a question asked at the right moment.
On-site surveys and feedback widgets
A one-question survey on exit or after an action, such as "What almost stopped you from signing up?", gets real reasons from real visitors. Few people answer, and the ones who do are self selected, but the answers are often specific enough to act on.
Ask one question at a time, at the moment it matters, and read every answer rather than charting them.
User tests with real people
Watching people from your audience try your site, moderated on a call or unmoderated through a research platform, is the strongest evidence of where real people get confused. Platforms such as UserTesting, Maze, Lyssna and Useberry recruit participants or let you bring your own.
It costs money and time to recruit, run and watch. It is the right tool for decisions that are expensive to get wrong, after cheaper methods have cleared the obvious problems.
Simulated visitors that use the site
Simulated visitors give outside feedback with no traffic and no recruiting. In a Mimiq run, visitors matched to your audience open your live site in real browsers, try a task such as signing up, and show what broke and where they left and why. The problems come back ranked by how many visitors hit them, with each visitor's reasons, and you can ask any visitor a question.
They leave where a visitor would, so you get the problems friends will not point out. They are also simulated: they are not your customers, they are weaker for niche experts and lived experience, and they do not predict how many people will convert. Use them to find what to fix and what to ask real people.
How to ask for feedback that helps
Give a task, not a request for opinions. "What would you do next on this page?" or "Where would you find the price?" produces evidence. "Do you like it?" produces politeness.
Ask what they make of it at first glance before anything else, because that disappears once people look around. Then ask what would make them leave, and what would make them trust it.
Look for patterns. One person disliking your colours is taste. Several people missing the price is a finding. Fix what repeats, starting with what sits on the first screen.
Six ways to get website feedback
| Method | Who gives it | Needs traffic? | Best for | Watch out for |
|---|---|---|---|---|
| Friends and colleagues | People who know you | No | Typos and obvious confusion | Politeness; they know too much |
| Communities | Other builders and marketers | No | Blunt outside opinions | They are rarely your customers |
| Session replay and heatmaps | Your real visitors, recorded | Yes | Where real visitors struggle | Shows what, not why; takes time to watch |
| On-site surveys | Your real visitors, asked | Yes | Real reasons at the right moment | Few answers, self selected |
| User tests with real people | Recruited participants or your users | No | The strongest evidence of confusion | Cost and time to recruit and review |
| Simulated visitors | Simulated people matched to your audience | No | What breaks and where visitors leave when they try the site, and why, repeatable | Simulated actions that are not real customer behavior; no conversion prediction |
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
Questions
Where can I get free feedback on my website?
From friends who match your audience, communities with feedback threads, and free plans of feedback tools. In Mimiq: Your first test is free: sign in with Google or email and it starts right away. A free account includes 50 credits, no card.
How many opinions do I need?
Enough to see what repeats. When the same problem comes up from several people who match your audience, it is worth fixing. A single opinion is worth a look, not a rewrite.
Should I ask people what they would change?
Ask what confused them or what would stop them, rather than what they would change. People are good at noticing problems and less reliable at designing solutions.
Is feedback from simulated visitors real feedback?
It is real output from simulated people. It is not feedback from real visitors. It is useful for finding likely problems quickly, and anything important should be confirmed with real visitors.
What should I fix first?
The problem raised by the most people, on the first screen, that blocks the main action. That is usually the main heading, the price or the button.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google or email and it starts right away. Last checked 2026-11-01.