Home

the United States

Freelance Web Developer for US Businesses & E-commerce

In the US market, two costs tend to sit unnoticed on a site until they bite: pages that are slow enough to lose the sale, and an inaccessible interface that turns into a demand letter. Both are measurable, and both are fixable without a redesign.

Straight answer

I have not shipped for a client based in the United States yet — my work so far has been for businesses in the UAE, New Zealand, the Netherlands, Malta and Pakistan. What I can show you is 9 years of the same problems solved for companies that look like yours, and live sites you can check for yourself.

Core Web Vitals, with the numbers to show for it

Performance work only counts if it is measured. I start from field data and a Lighthouse baseline, find what is actually holding up the largest paint or shifting the layout, fix that, and show the before and after. Usually it is images, blocking fonts, and a bundle carrying code nothing on the page uses — not a rewrite.

ADA and WCAG exposure

Web accessibility lawsuits against US businesses run into the thousands every year, and the common triggers are dull ones: unlabelled form fields, images with no alternative text, a checkout that cannot be completed with a keyboard. These are the cheapest problems in the entire build to prevent and among the most expensive to ignore.

Stores that stay fast as the catalogue grows

A WooCommerce store is quick on launch day with forty products and slow a year later with four hundred. The difference is decided by how the catalogue, images and queries were set up at the start. I build for the size the store is going to be, not the size it is on the day it ships.

Working hours

My later hours overlap the US East Coast morning, so there is a live window each day for calls and quick decisions rather than a full-day round trip on every question.

How it runs

From first call to handover

  1. A call about the problemNot about what you want built — about what is not working now. Half the time the thing a client asks for is not the thing that fixes it, and that is worth finding out before anyone quotes.
  2. Written scope and a fixed quoteYou get the scope in writing: what is included, what is not, the milestones, and the price. Nothing starts until that is agreed, so there is no moving target later.
  3. Build in milestones, on a live staging linkYou get a staging URL from the first week and watch it fill in, rather than waiting in the dark for a big reveal. Problems surface while they are still cheap to change.
  4. A proper review roundYou go through it, list what is wrong, and I fix it. Feedback is expected — it is part of the build, not an inconvenience at the end of it.
  5. Handover you actually ownCode, access, a walkthrough of how to edit things, and documentation for anything non-obvious. No lock-in: you can hand it to another developer tomorrow and they will know where they are.

Ways to work together

Pick whichever fits the work

Price depends on scope, so it comes after the first call rather than off a menu.

Fixed-price project

A defined build with a clear finish line

  • One agreed price, set before work starts
  • Milestones with a payment against each
  • Scope in writing, changes quoted separately
  • Best when you know roughly what you need

Hourly

Work that cannot be scoped up front

  • Joining an existing codebase
  • Debugging, audits and one-off fixes
  • Exploratory work where the shape is unclear
  • Time logged and reported, no minimum block

Monthly retainer

A site that needs someone on it every month

  • A set block of hours each month
  • Priority over ad-hoc requests
  • Updates, fixes and small features
  • Someone who already knows the codebase

Closest examples

Live sites you can check yourself

Every one of these is in production. Click through and judge it.

Premium Meats

Premium Meats

Custom WordPress build with AOS scroll animations

WordPressCustom TemplatesAOS
PillPharm

PillPharm

Online pharmacy platform

Next.jsReactTailwind CSS
Obvec

Obvec

Modern fabric e-commerce storefront

Next.jsReactTailwind CSS

Before you ask

Common questions

Can you fix a site that is already slow rather than rebuilding it?

Usually, yes — and that is normally the right call. I start with field data and a Lighthouse baseline, find what is actually holding up the largest paint, and fix that. A rebuild is a last resort, not the opening move.

How do you handle ADA accessibility risk?

By building to WCAG 2.1 AA so the common triggers are simply not there: labelled form fields, alternative text, a checkout completable by keyboard. I am a developer, not your lawyer — I can reduce the exposure, not certify you against a claim.

How long does a build take?

A straightforward marketing site is usually a few weeks; a store or an application with real logic behind it is longer. The honest answer is that it depends on how ready the content is — the delay on most projects is waiting for copy and images, not the code.

What do you need from me to start?

Whatever you already have: existing site, brand assets, content, and a clear sense of what the site has to make happen. If the content is not written yet, say so at the start — it changes the timeline more than any technical decision.

Do you handle hosting and domains?

I set up and deploy to hosting, and I will recommend what suits the project. The accounts stay in your name and you keep the billing, so you are never locked out of your own infrastructure.

Can my team update the site without calling you?

That is the goal on every build. WordPress work is set up so editors can change content without touching layout, and for custom builds I hand over documentation for whatever is not self-evident.

What happens after launch?

You get a period after launch for fixing anything that turns out to be broken — that is part of the build, not extra. After that, ongoing work is either ad-hoc hourly or a monthly retainer, whichever fits how much you actually need.

What if I do not like what you have built?

You will have seen it on staging from the first week, so it should never be a surprise at the end. Review rounds are built into the process, and structural feedback is much cheaper early — which is exactly why you get the link early.

Tell me what you need built

Describe the problem and I will tell you what it actually takes to solve it — including when the answer is that you do not need me.

Start a conversation →