Web development in Newcastle, NSW: the working parts behind your website.

Turning a design into a working site: the pages, the forms, whatever the site connects to, and the setup that decides how fast it loads and how easily it is changed later.

Most small business sites do not need much development at all, and saying so on a page selling it is worth doing. A handful of pages, a contact form and fast loading covers what most Newcastle businesses need.

Development becomes the job when the site has to do something. Take a booking against a real calendar, show stock, price something, sign somebody in, or talk to whatever software the business already runs.

What it covers

• Building the pages. Turning the design into something a browser loads, on every screen size, without breaking on a phone.
• The things that submit. Forms, bookings, payments. Anything where a customer puts information in and expects something back.
• The connections. Your job software, your calendar, your accounting, your email list. This is where the time goes on most real builds.
• How it is hosted and deployed. Where it runs, and how a change gets from somebody's screen to the live site without taking it down.

The build decides how fast the site is, whether it keeps working, and how much a small change costs a year from now. All three are invisible on launch day and all three are what you live with.

A website is judged twice. Once by a customer, in the couple of seconds before the first thing becomes readable. Once by the owner, the first time they ask for a change and find out what it costs.

Speed is also read by Google, so a slow site turns up in two places rather than one. Google publishes what it measures in its core web vitals, and the numbers are the ones a phone on a normal connection actually sees.

The change cost is the part nobody asks about beforehand. A site built out of plugins stacked on plugins can be cheap to launch and expensive to touch, and that bill arrives in year two.

Almost always the pictures, the plugins and the fonts. A site gets slow by accretion rather than by one decision, which is why it feels fine at launch and heavy a year later.

Slowness is rarely one dramatic fault. It is a photograph straight off a camera at ten times the size it displays at, then a plugin, then another plugin, then a font nobody looks at.

Where it comes from

• Pictures at the wrong size. The most common one by a distance. A photograph sized for print, loading on a phone.
• Plugins doing very little. Each one loads its own code on every page, whether that page uses it or not.
• Fonts. Every extra weight is another file to fetch before text can appear.
• Cheap shared hosting. Hundreds of sites on one machine. When one of them is busy, yours is slow.

The fixes are unremarkable and they work: resize the pictures, remove what is not being used, and put the site somewhere that is not overloaded. Most of the gain on a small business site comes from those three.

The code, the domain, the hosting account, and a way to take a copy whenever you want. Anything you cannot take somewhere else is rented, whatever the invoice calls it.

This is the part worth agreeing in writing before anybody starts, because it is cheap to agree at the beginning and expensive to argue about later.

What comes back at the end

• The code. In a place you control, with a copy you can hand to another developer without asking permission.
• The domain. Registered in the business name, tied to your ABN, with the renewal date somewhere you will see it.
• The hosting account. In the business's name, with the logins. Not inside an agency's reseller account.
• A way to take a copy. The whole site and whatever it stores, on demand, without a fee attached to asking.

Register the business name properly while you are at it. business.gov.au is where that happens, and the name you register is the one that belongs on the domain.

Agree what the site has to do and what you get at the end. Build it somewhere nobody can see, test the parts that submit, then launch on a quiet morning and watch it for a fortnight.

1. Write down what it has to do

Not what it should look like. What a visitor does on it, and what has to happen afterwards. Bookings, quotes, payments, or none of those.

2. Agree what you get at the end

The code, the domain, the hosting, and how you take a copy. In writing, before a deposit.

3. Build it where nobody can see it

On an address that is not your live site and is closed to search engines, so half a website never gets indexed.

4. Test everything that submits

Every form, from a phone, with a real address. The most common launch fault we find is a contact form that goes nowhere.

5. Launch on a quiet morning

Not a Friday afternoon. Keep the old site reachable until you are certain, and point every old address at its new one.

6. Watch it for a fortnight

Errors, form submissions arriving, and the pages that used to bring visitors still bringing them. This is when a redirect that was missed shows up.

The content is the slow part on nearly every build. The pages themselves go quickly; waiting for photographs and words is what stretches a job out.

The order it happens in

• What it has to do is agreed. Along with what you get at the end. Nothing is built yet and this part decides the price.
• The build happens out of sight. Pages, forms, and whatever the site connects to. Reviewed on a private address.
• It launches and gets watched. A quiet morning, old addresses pointed at new ones, then a fortnight of checking things arrive.

If a build is running late, the reason is nearly always that the photographs and the words are still coming. That is worth knowing at the start, because it is the one part a business can get ahead of.

Ask what the site is built on, who holds the code, what a small change costs afterwards, and what happens if you leave. The change cost is the question that separates a launch from an arrangement.

We do this work in Newcastle, so we are not neutral. These are the questions we would want asked of us.

• What is it built on? A plain answer another developer would recognise. Something only one agency can touch is a decision worth making on purpose.
• Who holds the code? The business. Ours goes into an account in the client's name from the first day.
• What does a small change cost afterwards? A rate, and roughly how long a typical change takes. This is the bill that arrives in year two.
• What happens if I leave? A copy of everything, without a fee for asking.
• Am I locked in? Ours runs month to month and always has. Any arrangement you cannot leave at the end of a month is worth a second look.

Plenty of Newcastle businesses run perfectly good sites they built themselves on a website builder. The point to bring somebody in is when the site has to do something the builder cannot.