Who owns the website when it is finished?

You do, completely. The domain is registered in your name, hosting sits in your account, the code lives in a repository you control, and any payment provider account is opened in your business name. Credentials are handed to you as they are created rather than at the end, so you are never locked out of your own site.

How do you handle our customers' data under UK GDPR?

Your customer data is governed by UK GDPR and the Data Protection Act 2018, and sending it to a developer in Pakistan is a restricted transfer. That is resolved by a pre-signed DPA with a completed UK International Data Transfer Addendum, published on this site and pre-signed before you send an enquiry — not drafted after you ask about it.

What payment methods can my Derby checkout accept?

For United Kingdom: Stripe, GoCardless for Direct Debit, and Klarna or Clearpay where basket sizes justify it. The right combination depends on your average basket and your customers, and picking wrong is expensive — the payment method a buyer expects but cannot find is one of the most common reasons a checkout is abandoned at the final step.

How long does a Derby project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

What hours will you be available to us in Derby?

My standard day lands at 05:00–14:00 your time — about 5 hours of genuine overlap with a normal Derby working day. That is enough for one reliable daily window rather than constant back-and-forth, so Derby projects run on written updates plus one scheduled call a week.

Can you fix my existing site rather than rebuild it?

Often, yes, and it is usually the cheaper answer. Speed problems, a broken mobile layout, a form that silently fails or missing structured data are all fixable on the site you already have. I will tell you which of the two you need after looking, and a rebuild only gets recommended when the fix would cost more than starting again.

Do you provide ongoing maintenance after launch?

Thirty days of snag fixes are included after launch at no extra cost — anything that does not work as specified gets fixed. Beyond that there are monthly plans for updates, backups, monitoring and small changes. They are optional and cancellable; a site handed over properly does not require a retainer to keep running.

Midlands · United Kingdom

Website speed and performance optimisation in Derby

A Lighthouse score on a developer laptop with fibre broadband is not a measurement of your site — it is a measurement of the laptop. The work here is judged on field data from real visitors on real phones, which is also the data Google actually uses. For Derby businesses, quoted in GBP from $80, typically live in 4 days.

What website speed and performance optimisation includes for a Derby business

Fixed scope, agreed in writing before development starts. From $80, typically live in 4 days.

Field-data baseline from Chrome UX Report where your traffic supports it, plus throttled lab testing where it does not
Largest Contentful Paint work: the actual LCP element identified, then preloaded, resized and served in a modern format
Interaction to Next Paint work, which usually means shipping less JavaScript rather than reordering it
Cumulative Layout Shift eliminated: dimensions on media, reserved space for embeds, metric-matched font fallbacks
Render path fixed — critical CSS, deferred non-essential script, and third-party tags audited for what they cost
Image pipeline: AVIF and WebP with correct srcset, and lazy loading applied below the fold only
Caching and compression configured at the server, including long-lived immutable assets
A before-and-after report with the numbers and the method, so you can reproduce it rather than trust it

The terms for a British client

Starting price	From $80, quoted and invoiced in GBP
Typical timeline	4 days once content is supplied
Tax position	VAT at 20% once you are registered — my invoices are outside the scope of UK VAT and you account for them under the reverse charge
Data protection	UK GDPR and the Data Protection Act 2018 — resolved by a pre-signed DPA with a completed UK International Data Transfer Addendum
Payment rails available	Stripe, GoCardless for Direct Debit, and Klarna or Clearpay where basket sizes justify it
My day in Derby time	05:00–14:00 — about 5 hours of overlap

Why this matters for United Kingdom specifically

UK local search is the most saturated in the English-speaking world, so a merely competent site does not win the job — the quote form does. Every UK build I ship is specified around the enquiry step first and the homepage second.

Why Derby sites are built to be edited by you

A site you cannot update is a site that decays. Prices go stale, staff leave, the opening hours are wrong for six months. So the parts of a Derby build that change often — text, images, prices, opening hours, team members — are editable by you without touching code or paying me.

That is a design decision with a cost: it takes longer to build an editable block than a hard-coded one. It is worth it because the alternative is a maintenance dependency that benefits me and not you, and a developer whose income depends on you being unable to change your own opening hours is not aligned with your interests.

Healthcare and clinics in Derby

Clinics carry a compliance weight most businesses do not. Appointment forms collect health information, which is a special category under UK GDPR, and it cannot be emailed to a generic inbox or written to a plain-text log. That constraint has to shape the build rather than be bolted onto it afterwards.

Beyond compliance the deciding factor is reassurance: practitioner names, registrations a patient can verify, honest pricing, and what actually happens at a first appointment. Anxiety is why people delay booking, and a site that reduces it outperforms one that merely looks modern.

A mobile layout nobody tested on a real phone

Desktop-first builds fail in predictable places: a navigation menu that cannot be closed, a table forcing the whole page sideways, tap targets too close together, and a sticky banner sitting over the button. Each one is invisible on a laptop and each one loses customers.

Most visitors to a Derby small business site arrive on a phone, so I design at phone width first and widen from there. That ordering is not a stylistic preference — it is the only way the small screen gets the attention the majority of your traffic deserves.

What I am not claiming about Derby

I have no office, postal address or phone number in Derby
I cannot meet you in person, and if that is a requirement you should hire locally
I am not claiming existing clients in Derby specifically — my live work is listed on the work page and you can check it
Nothing on this page is a guarantee of search rankings, which no developer can honestly offer