Home  /  Blog

Signs Your Web Designer Is Out of Their Depth

The Short Answer: The web designer red flags worth acting on are never about taste. They show up when you ask what the site must hit, who owns the accounts, and what happens in month seven. A designer who cannot name a measurable target for load speed, or who cannot explain your handover in one sentence, is out of their depth regardless of how good the mockup looks.

Most lists of web designer red flags are lists of bad manners. Slow replies, no contract, a portfolio of three sites. Those are real, and they are also the easy ones, because anyone can spot them before paying a cent.

The expensive flags are quieter. They belong to designers who reply quickly, present beautifully, and are pleasant to work with, right up to the point where the site has to do something. A booking form that stores names. A page that has to load on a mobile connection in a Cheras carpark. A rebuild that has to keep the rankings you already hold.

So this piece is organised around one test rather than a checklist of behaviours: can the person answer a question that has a number in it? Design taste is subjective, and arguing about it wastes everyone’s afternoon. Load times, ownership, data obligations and rollback plans are not. A designer who is out of their depth will change the subject when you reach them.

We build websites ourselves, so read the criteria below as the product on offer here. If they clear your current designer, keep them. That is a good outcome and it costs you nothing.

The video below covers the same ground from a buyer’s side, and it is a fair primer before the sections that follow.

Red Flags to Watch for When Hiring a Website Designer

Source video: Red Flags to Watch for When Hiring a Website Designer on YouTube

PART 1 · DIAGNOSE

Out of Their Depth Is Not the Same as Bad at Design

IN BRIEFDepth is the ability to carry a site after launch, not the ability to make one look good. Separate the two before you judge anyone. A designer with strong taste and no engineering habits will still deliver a handsome website design project that quietly fails in month seven.

Two different jobs get sold under one word. The first is composition: layout, type, colour, the thing you approve in a mockup. The second is engineering and stewardship, meaning performance, structure, data handling and the dull maintenance that keeps a site alive. Plenty of capable people do the first and have never been asked to do the second.

That matters because the flags you are hunting differ by job:

  • Taste failures show up immediately. You look at the mockup and dislike it. Cheap to fix, obvious to spot, rarely fatal.
  • Depth failures show up late. The site is approved, launched and admired, then loads badly on 4G, breaks when edited, or loses half its Google positions after a rebuild.
  • Only the second kind costs you money twice. Once for the build, once for the rescue.

So stop grading the portfolio on beauty. Grade it on whether the person can tell you what happened to each site afterwards. If every answer is about the launch and none is about month six, you have your first real signal.

Bottom Line: Judge designers on what they can still explain about a site a year after handover. Taste shows in five minutes; depth only shows in the follow-up.

Not sure whether the problem is taste or capability?

A one-hour review usually settles it, and the answer decides whether you coach or replace. Start with the questions to ask a web designer

PART 2 · DIAGNOSE

The Answers That Reveal Depth in One Meeting

IN BRIEFAsk four questions with numbers or names in them: the speed target, the one action the site must produce, who holds the accounts, and what breaks if you edit a page yourself. Vague answers to any of these are the web designer red flags that predict trouble, and the pattern shows up again in how a portfolio is presented.

You do not need technical knowledge to run this test. You need to notice whether the reply contains something checkable, or whether it contains reassurance.

Ask this A deep answer sounds like A shallow answer sounds like
What speed will it hit on mobile? Names a metric, a number, and how it will be measured on real visits “It will be fast, we optimise everything”
What one action must the site produce? Names it — a WhatsApp enquiry, a booking — and designs backwards from it “It will represent your brand professionally”
Whose name is on the domain and hosting? Yours, with the designer holding access only “We manage all that for you, don’t worry”
What happens if my staff edit a page? Shows you what is safe to touch and what is locked “Just send changes to us and we’ll do it”

The last one deserves attention. “Send it to us” is sometimes genuine service and sometimes a build too fragile to let you near. Ask which, plainly. A confident designer shows you the editable areas in two minutes.

Bottom Line: Depth reveals itself in specifics. Four questions with checkable answers separate a competent supplier from a pleasant one faster than any portfolio review.

BENCHMARK BRIEFING 1 OF 4

What Numbers Should a Finished Website Hit?

IN BRIEFGoogle publishes the thresholds, so nobody has to guess: 2.5 seconds for largest contentful paint, 200 milliseconds for interaction to next paint, 0.1 for layout shift — measured at the 75th percentile of real page loads. A designer who cannot discuss these has never been held to a website speed target.

Core Web Vitals Pass Thresholds, 2026
Google’s published good-experience thresholds for each Core Web Vital metric, the aspect of experience each one measures, and the measurement rule that decides a pass.
Metric Measures Good threshold How it is judged
Largest Contentful Paint Loading 2.5 seconds or less 75th percentile of page loads
Interaction to Next Paint Interactivity 200 milliseconds or less 75th percentile of page loads
Cumulative Layout Shift Visual stability 0.1 or less 75th percentile of page loads
All three together Overall assessment Every metric in the good band Split by mobile and desktop

Aggregated by IZI Digital Marketing from Google’s Web Vitals documentation on web.dev.

Two details in that table do the diagnostic work. The 75th percentile means a score from a fast office laptop proves nothing, because the test is real visits from real phones. The device split means a desktop pass can hide a mobile failure, which is the usual shape of the problem here.

Bottom Line: These numbers are published and free to check. Put them in the brief and the argument about whether the site is fast enough ends before it starts.

PART 3 · DIAGNOSE

Red Flags Hiding in How the Quote Is Written

IN BRIEFA quotation reveals depth because scope is where inexperience hides. Look for page counts without page purposes, “SEO included” with nothing named, and no line for revisions, training or migration. Reading two quotes side by side is faster than any interview — the method is in comparing web design quotations.

Shallow quotes describe deliverables. Deep quotes describe decisions and boundaries. The tells:

  • Pages counted, never defined. “10 pages” says nothing about what each page must achieve. A designer who cannot name the purpose of page seven has not thought about the structure yet.
  • “SEO included” as a single line. Ask what is included. Title tags and a sitemap is a fair answer. Silence, or a promise about rankings, is not.
  • No revision limit. Unlimited revisions sound generous and usually mean the project has no definition of done. Both sides suffer.
  • Nothing about content. Somebody has to write the words and take the photos. If the quote is silent, the assumption is you, and the launch will slip.
  • Migration treated as an afterthought. Replacing a site is a different job from building one, because you have positions to protect.

None of these proves incompetence on its own. Three together, on a quote for a site that has to carry revenue, is a pattern worth acting on.

Consultant’s Note: With a vague quote, ask for it to be re-issued with three lines added: what happens to your existing URLs, who writes the copy, and what the revision limit is. How the designer reacts tells you more than the revised document does. Someone used to being held to scope will welcome it. Someone who reads it as distrust has probably never had to be.
Bottom Line: Read the quote for what it leaves out. Missing lines on migration, content and revisions predict the arguments you will have in month three.

BENCHMARK BRIEFING 2 OF 4

How Many Malaysian Businesses Already Have a Website?

IN BRIEFWeb presence among Malaysian establishments reached 72.7 per cent in 2023, up from 71.4 per cent a year earlier. Most projects are now replacements, not first builds — which is precisely the job that punishes a shallow designer, as the agency versus builder comparison sets out.

Malaysian Establishments: ICT Adoption, 2022–2023
Share of Malaysian business establishments using computers, holding internet access and maintaining a web presence in 2022 and 2023, with the year-on-year change in percentage points.
Indicator 2023 level 2023 2022
Used computers
96.6% 95.9%
Had internet access
94.0% 93.3%
Maintained a web presence
72.7% 71.4%

Aggregated by IZI Digital Marketing from the DOSM Malaysia Digital Economy 2025 release.

Roughly seven in ten establishments already publish something. The typical brief is no longer “make us a website”. It is “replace this one without losing what it earns”, which is why migration planning is now the sharpest test of depth.

Bottom Line: Replacement projects carry inherited value. Ask any designer what they will do with your existing URLs before you discuss what the new site will look like.

PART 4 · DESIGN

Coach, Supervise or Replace: Deciding What to Do Next

IN BRIEFSpotting the flags is the easy half. Deciding what to do about them is where owners freeze. Coach a designer whose gap is knowledge, supervise one whose gap is process, and replace only when trust or ownership is the problem. The shortlist logic sits in our guide to website design companies in Malaysia.

Sunk cost makes this harder than it needs to be. The useful question is not “was I wrong to hire them”. It is “can the gap be closed inside this project, at a cost I would accept if I were starting today”.

DECISION BOX · WHAT TO DO ABOUT THE GAP

Option Fits when Your effort Main risk
Coach and specify Design good, no targets set Low — one brief Gaps return post-launch
Supervise with a reviewer Build halfway, mostly sound Medium — checkpoints Slower delivery
Replace the supplier Accounts withheld, trust gone High — full restart Losing assets on exit

Verdict: Coach when the gap is knowledge and the work is good, and supervise when the build is already half done. Replace only when ownership or honesty is the issue — those two gaps never close with a better brief.

Bottom Line: Most depth gaps are specification gaps and close cheaply. Withheld accounts are the exception, and worth walking away over.

BENCHMARK BRIEFING 3 OF 4

What the Law Now Expects of Your Enquiry Form

IN BRIEFAny form that collects a name and a phone number makes you a data controller under Malaysia’s amended data protection law. The Commissioner has published instruments on breach notification, data protection officers and design obligations — a designer unaware of all three is building your compliance risk into the layout.

Data Obligations Touching Website Builds
Published Malaysian personal data protection instruments that bear directly on website design decisions, and the build decision each one affects.
Published instrument What it governs Build decision it affects
Personal Data Protection (Amendment) Act 2024 Renames data users as data controllers and widens duties Who is accountable for form data
Guidelines on Data Breach Notification Reporting a breach to the Commissioner Logging, backups, who is alerted
Guidelines on Appointment of a Data Protection Officer Naming a responsible officer Contact details shown on site
Data Protection by Design Guideline Building protection in from the start Which fields are collected at all
A Quick Guide to Privacy Notice What the notice must tell people Notice wording and placement

Aggregated by IZI Digital Marketing from instruments published by the Personal Data Protection Commissioner (JPDP).

The practical version is short. Collect fewer fields, write a privacy notice a customer can actually read, and know where enquiries are stored and who can reach them. A designer who has never raised any of this is not careless on purpose. They have simply never worked on a build where somebody asked.

Bottom Line: Every field on your form is a duty you accept. Ask why each one exists, and delete the ones nobody in your team ever reads.

Want your current build checked against these three briefings?

We review speed, ownership and form data in one sitting and tell you plainly which gaps matter. See how our website design work is scoped

PART 5 · DEPLOY

How to Test a Web Designer’s Depth Before You Sign

IN BRIEFRun a paid trial task instead of a longer interview. Four steps, about a week, at a fraction of the build cost. The same sequence works whether you are hiring a studio, a freelancer or the person who already quoted for your redesign.

How to test a web designer before you hire them

The point is to watch the person work on something small and real, where inexperience shows up in days rather than months.

  1. Ask for one live example with numbers. A site they built, its current mobile speed reading, and what they did about it. One example with real figures beats a gallery of twelve.
  2. Buy a small paid task. Pay for one page or one fix at their normal rate. You are buying evidence, not a favour, so treat the price as research.
  3. Watch the handover of that task. Did you receive access, a note on what changed, and a way to undo it? That habit either exists or it does not.
  4. Ask what they would refuse to do. Depth shows up as boundaries — a designer who has never declined a client request has never been in a position where they should have.

If step two feels like an unnecessary cost, weigh it against a rebuild in month nine. A week of paid evidence is the cheapest research available on this decision.

Bottom Line: Buy a small piece of work before you buy a website. Behaviour under a real deadline is the only reliable evidence of depth.

BENCHMARK BRIEFING 4 OF 4

Which Red Flags Can Still Be Reversed?

IN BRIEFNot every red flag deserves the same response. Cosmetic and copy problems are cheap to reverse; structure, lost URLs and withheld accounts are not. The model below sorts them by when they surface and how hard they are to undo, which is the practical basis for the coach-or-replace call above.

Red-Flag Reversal Difficulty (Illustrative)
Illustrative model sorting common web design red flags by the project stage at which they usually surface and the relative difficulty of reversing each one.
Red flag Usually surfaces Reversal difficulty Band
Weak layout or typography Mockup stage
Cheap
Template copy left in place Pre-launch review
Cheap
Fails mobile speed thresholds Weeks after launch
Moderate
Page structure nobody can extend Second content update
Hard
Old URLs dropped in a rebuild Weeks after launch
Hard
Domain or hosting held in their name When you try to leave
Hard

Illustrative model by IZI Digital Marketing, built on Google’s published Core Web Vitals thresholds and standard web project stages.

The pattern is worth naming. The flags that are cheap to reverse are the ones you can see; the expensive ones are administrative. That is backwards from where most owners put their worry.

Bottom Line: Spend your attention on ownership and structure, not colour choices. The reversible problems stay reversible next month; the others will not.

PART 6 · DRIVE

The Exit Plan You Should Have From Day One

IN BRIEFFour things must sit in your company name from the start: the domain, the hosting account, the analytics property and the site backups. Suppliers get access, never ownership — the full list is in our note on what you should receive at handover.

An exit plan is not distrust. It is what lets you keep a good designer for years without the relationship becoming a dependency, and it removes the worst outcome from the coach-or-replace decision.

  • Register the domain yourself. Your company as registrant, your email as contact. Give the designer access if it helps.
  • Hold the hosting account. Managed hosting billed through a supplier is fine; the account being in their name is not.
  • Own the analytics property. Historical data is the only record of whether anything worked, and it does not transfer easily.
  • Take a copy of the backups. One recent export stored somewhere you control turns a dispute into an inconvenience.

Set those four up in an afternoon at the start of a project, and most of the web designer red flags in this article stop being existential. They become ordinary supplier problems, which is what they should have been.

Bottom Line: Ownership converts a hard problem into a manageable one. Sort the four accounts before the first invoice, not after the first argument.

FAQ

Frequently Asked Questions

1. What are the clearest web designer red flags before you pay anything?

Vagueness where a number belongs. It depends on the project size, but on any site meant to earn enquiries, three answers matter: the speed target, the action the site must produce, and who holds your accounts. A designer who cannot give all three has told you enough already.

2. Is a cheap quotation always a red flag?

No — low price is a scope signal, not a competence signal. It depends what has been left out: a modest quote with a defined page purpose and a clear revision limit is often better value than an expensive one with neither. Read the exclusions before the total.

3. My designer will not give me admin access. Is that normal?

Withholding access to your own domain, hosting or analytics is not normal. It depends slightly on the platform, since some managed builds genuinely restrict editing, but account ownership should always be yours with access granted to them.

4. Should I fire a designer who missed the mobile speed thresholds?

Usually not on the first miss. It depends whether a target was ever set: if nobody wrote down the numbers, that is a specification failure and a written brief fixes it. Repeated misses after a clear target is a different conversation.

5. How do I check whether my current website is actually slow?

Test it yourself on Google’s own tools, on a phone rather than a laptop. It depends on your traffic mix, so look at field data from real visits where available, and compare each reading against the published 2.5-second, 200-millisecond and 0.1 thresholds.

THE VERDICT

Judging Depth Without Becoming a Technical Expert

You do not need to learn web development to run this assessment. You need four questions with checkable answers, a quote read for what it omits, and four accounts in your own company name. That combination catches almost every designer who is out of their depth, early enough that coaching is still an option.

It also protects the good ones. A capable designer welcomes a brief with numbers in it, because a specified project is one they can be judged fairly on. If your supplier reacts well to the requests here, you have your answer, and it is a reassuring one.

Where a second opinion helps is the middle case: the build that is neither clearly fine nor clearly broken. That review is what IZI Digital Marketing does before any website design engagement begins. Sometimes the honest outcome is that your designer is fine and the traffic problem belongs to a search partner instead. We will say so.

Want an honest read on whether your designer is out of their depth?

Book a free Blueprint consultation. We’ll check your build against the speed thresholds, the ownership list and your form data, then tell you plainly whether to coach, supervise or replace. You leave with the written brief either way.

Book my free consultation

Have a campaign in mind? Let's talk.