Questions to ask about performance, access, and ownership

The questions to ask a web design agency are mostly about performance, access, and ownership. Taste shows up in the portfolio. The questions below show up in the second meeting, and they decide whether the launch remains yours after the studio is gone.

Ask them before the proposal, while changing your mind is still cheap. A studio that answers in specifics is easier to trust than a studio that answers with a mood. You are listening for names, files, and thresholds.

Who writes, and who builds

Ask who will design the work and who will write the production code. Then ask whether those are the people you have met. A small studio's advantage is that design and build sit together. That advantage disappears if the call is with a seller and the files are with a bench you will never meet.

Ask who writes the sentences. Interface copy, errors, and the homepage offer are design decisions. If a separate writer is assumed, say whether you have one. If the studio writes, ask to see a page where the words do as much work as the layout.

Ask how design and engineering share a decision. A Figma file that the code never quite matches is a split studio wearing one logo. The practical version of the question: when type, motion, or real content changes the design, do you change it in the browser and record the decision, or does the file stay frozen while the site drifts?

What you will own

Ask for the list of things that will be in your name on the day you pay the last invoice.

The repository. The domain. The hosting account. The analytics property. The content logins. The brand files, in a place your team can open without filing a ticket. If any of these stay with the studio, you have hired a dependency. Continuing help is welcome. Sole access is not.

Ask about the license on fonts, photography, and any library that carries a fee. "You own the site" is incomplete if a typeface expires or a photo was never licensed for the web. The answer you want is a list, not a reassurance.

Ask what the handoff contains besides a login. A content map, a short note on how to change a headline, and the place docs live. Hanabi's client portal is one concrete version of that place: brand files, docs, and project updates after delivery. Whatever the tool, you should be able to find the logo and the latest decision without searching a chat.

The sibling question is the long version of this section. What you should own after a studio engagement goes through the repository, the domain, the analytics, and the content logins as a set.

How the site stays fast

Ask which performance bar the studio designs toward, and ask for the definitions rather than a score in a deck.

Google publishes the thresholds as Core Web Vitals. A good Largest Contentful Paint is within 2.5 seconds. A good Interaction to Next Paint is within 200 milliseconds. A good Cumulative Layout Shift is under 0.1. Those are the numbers to put in the question. "Will it be fast?" invites a yes. "How will you watch LCP, INP, and CLS, and what will you cut if a page misses them?" invites a method.

Ask what usually threatens the bar on a site like yours. Heavy hero media, a font that blocks the first paint, a layout that jumps when late content arrives, a third-party script added for a tool nobody reviews. A studio that can name the likely threat has already done this work. A studio that promises a perfect score on every page is selling a number it does not control, because content and scripts change.

Ask for a staging URL where you can look at the page on a phone, on ordinary wifi. A lab report is useful. The phone in your hand is the check you will trust.

What happens when someone needs less motion

Ask how motion treats a person who has asked the system to reduce it. The W3C's Web Content Accessibility Guidelines are the public reference for a page that people can actually use: text alternatives, keyboard access, contrast, and interaction that does not depend on a single sense. Reduced motion sits in that family of care. A serious answer describes two versions of a move. The intended motion, for people who want it. A still or instant version, when the person has set a preference for less motion.

Ask to see that preference respected on a staging page, not only described. Decorative loops that ignore the setting are a craft failure even when they are on-brand. The question also reveals whether accessibility is a final checklist or a condition of done. You are not asking the studio to certify the site. You are asking whether contrast, focus, names, and motion preferences are reviewed before launch.

Access while the work is happening

Ask how you will see the work before it is finished. A staging link, a shared design file, a weekly review. You should be able to open the in-progress site yourself. A studio that only presents in a call controls your view of the schedule.

Ask who on your side is expected to approve, and how fast. This question is partly for you. If you cannot name the approver, the studio's dates are fiction. A good studio will ask you the same thing. Welcome that.

Ask where decisions will be written. One channel, a note after each review, a date that moves in public. Performance, access, and ownership all fail quietly when the decision lives in a private message.

Ask what happens in the week after launch, even if you expect to stop. Who watches the first real orders or the first real form submissions? Who can roll back a DNS change? A studio that has an answer has done a launch before. The answer should name a person and a window of time, and it should leave you able to act if that person is away. Ownership is incomplete if the only person who can reverse the launch is someone you no longer have on contract.

If the answers are specific and you want to test them against your project, book an intro call with Hanabi. Bring the questions. A useful call produces fit, a rough shape of the work, and a clear sense of what you will own.