how to choose a web designer in parma: seven checks and the questions to ask
business · 2026-10-17 · 6 min
choosing a web designer is not a taste test. the portfolio matters, but it tells you what someone can make, not how they work. the decisions that hurt later are made before the first pixel: who owns the domain, who can edit the site, what "fast" means in numbers, what happens when the site breaks in march.
i work as a web designer and developer in parma, italia. this is the list i would use if i were hiring someone, and the questions i would ask before signing.
1. open the portfolio on a phone
not the screenshot. the real site, on a real phone, on a normal connection. tap the menu. send the form. scroll to the footer. a portfolio of beautiful images that were never shipped is a portfolio of images. ask which of those sites the designer built, not only designed, and which ones are still online.
2. ask for a performance budget, in numbers
"fast" is not a specification. ask for the numbers the finished site should hit: largest contentful paint, interaction to next paint, cumulative layout shift, measured on a phone. a designer who has never measured their own site cannot promise yours will be measured. if the answer is a score out of 100 with no explanation, ask which metric that score represents and on what device.
3. ask how accessibility is checked
not "we care about accessibility". ask what they check: keyboard navigation, contrast, labels on form fields, alt text, focus states, heading order. ask whether it is tested with a keyboard and a screen reader, or only with an automated tool. automated tools catch maybe a third of the problems; the rest needs a person. accessibility is also an seo and usability investment, not a compliance tax.
4. ask who owns the domain and the accounts
the domain, the hosting, the analytics, the search console, the repository: they should be in your name, or at least transferable in one afternoon. ask what happens if the collaboration ends. a site you cannot move is not an asset, it is a subscription with extra steps. this is the single most expensive mistake in the list, and it is invisible until the relationship sours.
5. ask how content and seo are handled
a site is not done when the layout is approved. ask who writes the text, who chooses the photos, who writes the titles and descriptions, who sets the redirects, who submits the sitemap. "seo included" means nothing until it is a list. the honest list is: crawlable pages, unique titles and descriptions, canonical urls, redirects, sitemap, mobile usability, search console. nobody can guarantee a position, and anyone who does is selling something else.
6. ask what will be measured after launch
a site that is not measured is a guess with a domain. ask which events will be tracked, who reads them, and when. one counter plus one conversion event is enough to start. a monthly email with three numbers is better than a dashboard nobody opens. if the answer is "we will see", the project has no definition of success.
7. ask what maintenance costs, in writing
updates, backups, security patches, a plugin that breaks, a form that stops sending. ask for the monthly or yearly number before you sign, and ask what is excluded. a site is a small machine that runs in public; it needs someone responsible for it. the cheapest quote often becomes the most expensive year two.
the questions that reveal the most
- "show me a site you built that you would improve today, and tell me what you would change" — a designer who cannot critique their own work is not evaluating yours either.
- "what would you tell me not to build?" — a partner who never says no is a order taker.
- "who does what, by name?" — "the team" is not a person. you want to know who writes, who designs, who develops, who answers after launch.
- "what happens if i want to leave?" — the answer should be a procedure, not a feeling.
- "what do you need from me, and when?" — content and decisions are the usual delay. a designer who names that upfront is protecting the timeline.
freelancer or agency
a freelancer is usually cheaper, faster to talk to, and directly accountable. the risk is capacity: one person, one holiday, one illness. an agency has more hands and more process, and costs more for the coordination. neither is better in general. the question is the project: a five-page site with a clear scope is a freelancer shape. a project with a design system, three integrations and a launch date that cannot move is an agency shape. what matters is that the person who sold you the project is involved in it, and that the contract names who does what.
the parma, italia part
if you are searching for a web designer in parma, remember that half the results are about parma, ohio. look for italian language, an italian address, a vat number, a phone that answers, and a portfolio of italian clients. "Parma, Italia" in the copy is not keyword stuffing here; it is a disambiguation, and it is a fair thing to expect from someone who claims to work locally.
for the agency version of this checklist, see how to choose a web agency in parma. for the work itself, see realizzazione siti web a parma and ux designer a parma.
faq
how much should a website cost in parma?
there is no single number. a small brochure site is usually in the low thousands, a site with custom design and integrations is in the high thousands, and an e-commerce is its own project. ask what the range includes, not only the total: content, photography, seo setup, maintenance and ownership change the number more than the platform does.
should i choose a freelancer or an agency?
choose the shape that matches the project. a clear, small scope fits a freelancer; a large scope with several specialists and a fixed launch fits an agency. in both cases, ask who will actually do the work and who answers after launch.
what should i ask before signing?
seven things: a real portfolio on a phone, the performance numbers, how accessibility is checked, who owns the domain and accounts, what "seo included" means, what will be measured after launch, and what maintenance costs. if any answer is vague, ask for it in writing.
how long does a website take?
a small site with content ready is usually four to eight weeks. the variable is rarely the design; it is the content, the decisions and the number of people who have to approve them. a designer who gives you a date without asking about content is guessing.