Website Design Feedback Examples: Turn Vague Comments into Useful Requests

“Make it cleaner.” “I don’t like the hero.” “Can the button pop more?” These comments express a reaction, but leave the designer guessing about the cause and desired outcome. Clear feedback points to a location, describes the observed problem and explains the user or business impact.

A four-part feedback formula

Try this structure: Where is the issue? What do you observe? Why does it matter? What decision or change should happen next?

You can ask a question instead of prescribing a solution. “Could we make the primary action easier to distinguish from the secondary link?” is more useful than a broad request to “make it pop.”

Examples for common review comments

• Instead of: “The homepage feels confusing.” Try: “On the first screen, I cannot tell whether the service is for homeowners or property managers. Could the headline name the primary audience?”
• Instead of: “The button is wrong.” Try: “The main button says ‘Learn more,’ but the goal in our brief is to book a consultation. Could we use a label that sets that expectation?”
• Instead of: “The mobile page is broken.” Try: “At the mobile frame, the phone number wraps between the area code and remaining digits. Can we keep the number together?”
• Instead of: “Use a better photo.” Try: “The current image shows a large corporate team, while this service is delivered by one consultant. Could we use an image that reflects the actual experience?”
• Instead of: “Move this up.” Try: “Visitors need to see the delivery areas before choosing a service. Could we show the coverage information before the package comparison?”
• Instead of: “The font is too small.” Try: “The paragraph under the pricing cards is difficult for me to read at this presentation size. Could we compare a larger body-text size in the next version?”
• Instead of: “I don’t like the colors.” Try: “The orange accent is not in our approved brand palette. Please check the palette in the brief before we sign off.”

Label the type of feedback

Use a simple category to keep a review actionable:

• Correction: A fact, name or supplied content is inaccurate.
• Usability concern: A visitor may not understand or find something.
• Brand concern: The design conflicts with an agreed brand rule.
• Preference: A personal choice that may need a discussion about goals.
• New request: A feature or change outside the reviewed scope.

These labels do not decide whether a comment is accepted. They make the conversation more precise and help reveal which comments need a decision from the project owner.

Make feedback easy to locate

Name the page and section. If your review tool supports comments pinned to a location, use them for visual details. If you are sending a list, number each item and refer to a visible heading or element. Avoid describing location only by color or vague phrases such as “over there.”

Swelik supports comments on shared previews when the owner has enabled review features. For more prompts to help shape a review, see website design feedback questions.

When a comment needs a conversation

Some feedback reveals a disagreement about the goal rather than a small design issue. If stakeholders want different audiences, messages or primary actions, pause the visual edits and confirm the decision owner. Otherwise, the designer may spend time polishing a direction the team has not agreed on.

More examples for a realistic review

• Navigation: “I expected to find delivery information under ‘Services,’ but it is under ‘Resources.’ Could we test a label that matches the words customers use?”
• Trust: “The page mentions ten years of experience but does not show who provides the service. Could we add the approved team or credential information near this claim?”
• Content: “The pricing card says ‘from $500’ while the brief lists a $500 setup fee plus monthly support. Can we clarify what the starting price includes?”
• Accessibility: “The selected tab is identified only by a color change in the mockup. Could we also show a shape, underline or text state, then confirm the implementation exposes the selected state?”
• Imagery: “This crop cuts off the product label that the copy references. Could we use a crop that keeps the label visible on both desktop and mobile?”

Prioritize feedback instead of sending an unranked list

Mark each comment as blocking, important or optional. A blocking issue prevents the agreed goal from being evaluated, such as a missing key page or incorrect business detail. An important issue affects clarity or brand fit. An optional note is a preference that can be considered if time allows. Agree on what these labels mean with your team; they are a triage aid, not a universal standard.

Combine duplicates and separate observations that need different decisions. If three reviewers say that they cannot identify the main offer, present that as one issue with all relevant context rather than three independent requests for different headline changes.

Close the loop

After the designer responds, check that each accepted comment has an outcome: changed, intentionally unchanged with a reason, or deferred. Do not assume that a comment was missed simply because the visual solution differs from your first suggestion. The designer may have addressed the underlying problem another way. Ask for clarification when the goal is still unmet.

A precise comment protects the working relationship as well as the design. It replaces personal judgment about a person’s taste with a shared discussion about the page, the audience and the agreed brief.

Frequently asked questions

Should every comment include a solution?

No. Explain the evidence and intended outcome. The designer can recommend a solution.

How much feedback is too much?

There is no universal number. Keep comments relevant to the current stage, combine duplicates and separate new scope from requested refinements.