Most businesses that hire the wrong web developer do not find out until the project is over.
The site gets delivered. It looks like what was promised. And then, slowly, the problems surface — it loads too slowly on mobile, it cannot be found on Google, the developer is unreachable, and the files are locked inside a platform only they control.
By then, the budget is spent and starting over means paying twice.
At ELANBRIWEB, the projects we are most often asked to fix were not failed by bad design. They were failed by the wrong hire. And in almost every case, the red flags were there from the first conversation — they just went unnoticed because most clients do not know what to look for.
Here is what to look for.
Red Flag 1: They Show You Beautiful Work but Cannot Show You Performance Data
A strong portfolio is expected. It is the minimum requirement, not a differentiator.
What separates a developer who builds sites that look good from one who builds sites that work is measurable. Load time. Mobile performance. Core Web Vitals. These are numbers — and any developer serious about their craft can show them.
When you ask for PageSpeed Insights scores on recent projects and the answer is vague, defensive, or met with a subject change — that is your answer.
What to look for instead: a developer who leads with performance data before you even ask. On mobile, scores above 85 are the standard. A developer who cannot consistently hit that number is building sites that cost you visitors before a single word is read.
Red Flag 2: They Said Yes to Everything Without Asking a Single Question
A web developer who takes a brief and immediately starts talking about delivery timelines and pricing has skipped the most important part of the project: understanding what the site actually needs to do.
Every business is different. The questions a developer should ask before quoting anything include: who are your customers, what action should the site drive, what does success look like in six months, and what have you already tried that did not work?
A developer who asks none of this will deliver a site built for a generic business — not yours.
What to look for instead: someone who pushes back, asks uncomfortable questions, and takes time to understand the business before proposing anything. A discovery phase is not a delay. It is the difference between a site built around your actual goals and one built around a template.
Red Flag 3: The Quote Is All-In but Nothing Is Itemised
A single lump-sum price with no breakdown is not a quote. It is a number chosen to win the project.
What that number includes — and more importantly, excludes — is where the real cost of a web project lives. Hosting setup. Domain configuration. Email accounts. Revisions after delivery. Post-launch support. Content updates. These are all things that can be “not included” without ever being mentioned upfront.
What to look for instead: a quote that specifies exactly what is covered. Design, development, content integration, testing, launch, and post-launch support should each be addressed explicitly. If a line item is missing, ask directly. The answer will tell you whether the developer is being transparent or selling a number.
Red Flag 4: You Will Not Own Your Own Website
This is the most damaging outcome of a bad hire, and it happens more than most business owners expect.
Some developers build on proprietary platforms — tools they control — which means the site cannot be transferred, maintained, or even accessed without them. Others keep the hosting credentials, the domain login, or the source files. The business thinks they own a website. They actually own a dependency.
What to look for instead: full access to everything, delivered at launch. Hosting credentials. Domain registrar login. Source files. Back-office access. A website is a business asset — it should be yours completely, with no strings attached to the person who built it.
At ELANBRIWEB, every project is handed over with complete access and a plain-language guide for managing it independently. If a developer cannot commit to the same, the question is why.
Red Flag 5: Support After Launch Is Vague or Not Mentioned
The conversation about what happens after delivery should happen before you sign anything. Most clients forget to ask. Most developers are happy not to bring it up.
A site that launches without a defined support structure is a site that will eventually break — a plugin update, a server issue, a form that stops sending — with no clear path to getting it fixed. And by then, the developer may be unavailable, unresponsive, or suddenly very expensive.
What to look for instead: a specific answer to these questions before the project starts. What is covered after launch and for how long? What is the response time if something breaks? Is there a retainer option for ongoing changes? These are not unreasonable questions. A developer who cannot answer them clearly is one who has not thought through what happens after they collect payment.
The Five Questions to Ask Before You Hire Anyone
These are the questions that separate a developer who delivers from one who disappears.
- Can you show me PageSpeed Insights scores from your last three projects — on mobile?
- What questions do you need answered before you can give me an accurate quote?
- What exactly is not included in this price?
- Who owns the hosting, domain, and source files after delivery?
- What is your process if something breaks one month after launch?
A developer with nothing to hide will answer every one of these directly. Hesitation, deflection, or irritation at being asked are not personality traits — they are information.
Hiring a web developer is not just a creative decision. It is a business one. The right hire builds something that works and hands it over completely. The wrong hire delivers something that looks fine until it does not.
If you want a direct conversation before committing to anything, talk to ELANBRIWEB — no pitch, no pressure, just honest answers to your questions.
