A homepage design exported as one long PNG looks like a poster, and clients review it like one. They comment on colors and photos, and rarely ask what a visitor would do next. Put the same design in a browser window, with an address bar and tabs, and the conversation changes. Now it’s a website, and people react to it as visitors.

This guide covers how to present website designs so you get feedback on the site itself, on desktop and mobile, and how to keep that feedback organized as the pages add up.

Know which stage you’re reviewing

Website feedback happens at two very different stages, and each needs its own setup.

• Design review happens before anything is built. You’re agreeing on layout, hierarchy, content and look, using static page designs.

• Build review happens on a staging site. You’re checking that links work, forms submit and nothing breaks between screen sizes.

Mixing them causes trouble. A client who sees a static design in a browser may try to click it. A client reviewing a staging site may start redesigning the hero. Say clearly which stage this is and what kind of feedback you need.

Present pages in a browser frame

Context helps clients judge proportions. In a browser window, a big hero headline looks like what it is. On a white canvas, the same headline can look tiny or enormous depending on how far the image is zoomed out. A browser frame also gives you tabs, which make a multi-page design easy to move through.

Always show mobile next to desktop

For many sites, more visitors arrive on a phone than on a laptop, yet mobile designs are often reviewed last, if at all. Show each page’s mobile design next to its desktop version, in a phone frame at real proportions. Clients catch things that only show up side by side: a section missing on mobile, a button pushed three screens down, a menu that hides the most important page.

Walk the client through the pages in order

Present pages in the order a visitor would see them, starting with the page most people land on. For a full site, that might be home, then a product page, then pricing, then contact. A one-line note on each page explaining its job, such as “this page convinces someone to book a demo”, gives the client a lens for their feedback.

Ask about goals, not taste

“What do you think?” gets you opinions. These questions get you feedback you can act on:

• What would a first-time visitor understand from the part of the page above the fold?

• Is it clear what we want them to do next?

• Is anything here a claim we can’t back up?

• Is any important content missing, or in the wrong order?

• Do the pages agree with each other on names, prices and promises?

Keep content feedback apart from design feedback

Plenty of website projects stall because the copy isn’t final. If the client is rewriting headlines during the design review, the layout gets judged against text that will change. Where you can, agree on the page copy in a document first, then review the design with real text. If some copy is still moving, mark it as placeholder so the client doesn’t spend their review on it.

Answering the feedback every web designer hears

“Can we fit more above the fold?” Usually the real worry is that the main message isn’t clear fast enough. Ask what visitors should see first, then make that clearer instead of cramming more in.

“Make the logo bigger.” Often a sign the page doesn’t feel like the brand yet. Ask what feels off. The fix may be color or imagery, not the logo.

“It feels empty.” White space reads differently in a browser than on an artboard. If the client saw the design as a flat image, show it in a browser frame at real size before changing anything.

How website design review works in Honter

Honter’s web design view puts your page designs in a Safari-style browser window, with a tab for every page. Upload full-page images or push frames from Figma, and Honter sorts each design by width: under 600 px is mobile, 600 to 899 px is tablet and 900 px or wider is desktop. It names the pages and pairs each desktop page with its mobile version, and you can change any of it before you share.

• Pages with both versions show side by side, with mobile in a phone frame.

• Clients can zoom, switch to a device preview or open a clean live preview with no window chrome.

• On a phone, clients see one page at a time, and the mobile version loads first.

• AI reviewers read the page images before the client does and give extra weight to what sits above the fold.

Honter is built for the design stage. If you need comments on a live or staging URL, a live-site annotation tool is the better fit. Our comparisons with Markup.io and Pastel explain where each tool fits.