Roast My Site: Turn Blunt Feedback Into Useful Work
A useful website roast should leave you with a short list of things to investigate or fix, not just a bruised ego. Bluntness is a delivery style. The value is a precise observation connected to the visitor's task.
Key Takeaways
- Separate what the reviewer observed from what they inferred.
- Ask for evidence and a testable next action.
- Treat expert critique as a source of hypotheses.
- Measure outcomes after the repair; a roast does not promise higher conversions.
Ask for more than “this looks bad”
Good feedback names the page, state and problem. “The hero is confusing” is a start, but not enough to act on.
Here is an illustrative critique:
| Part | Useful feedback |
|---|---|
| Observation | The headline says “Move forward” and the visible screen does not name the product |
| Evidence | The reviewer cannot identify what is sold without scrolling |
| Interpretation | A first-time visitor may face the same uncertainty |
| Proposed change | Name the product, intended user and outcome near the primary action |
| Check | Ask unfamiliar people to describe the offer before explaining it |
The interpretation remains a hypothesis until checked. A reviewer is not your whole audience.
Keep the review tied to one task
Tell the reviewer who is arriving, where they came from and what they should do. A campaign landing page and an existing-customer support page need different judgments.
Supply real constraints: a third-party booking engine, a required approval step, an asset license or a product feature that is not yet live. Otherwise the critique may recommend something attractive but impossible.
The five landing-page elements provide a useful structure for a first-visit review. User-intent mapping helps when several tasks share one site.
Separate failures from preferences
A form that loses entries is a reproducible failure. A color the reviewer dislikes is a preference unless it creates a demonstrated problem, such as insufficient contrast.
WCAG understanding guidance provides criteria for accessibility checks. Core Web Vitals requires performance measurement. Neither can be replaced by “the site feels modern.”
Record the severity and effort separately. A small broken action may deserve attention before a large visual refresh.
Turn the critique into a repair list
For each accepted issue, assign an owner, a proposed change and an acceptance condition. Keep disputed assumptions visible. After the repair, repeat the relevant task and check that a new problem has not appeared elsewhere.
For conversion claims, establish a baseline and a suitable comparison. An expert review can identify likely friction; it cannot promise a revenue effect.
Our Roast My Page service is one way to get an outside view. Inspect the current scope and deliverables there. The earlier article's “20% of companies” statistic and promised conversion outcome were unsupported and have been removed.
Have a product idea?
Designed, built, and shipped in about 5 days.