Fast AI powered sites for New Zealand visitors

Speed matters more than most teams expect. A page that appears quickly feels trustworthy, and a site that answers from a nearby server saves visitors a noticeable wait. For New Zealand audiences, the distance to a server on the other side of the Pacific is real physics, and the fix is a short checklist. This post covers how to host an AI powered site for Kiwi visitors with good speed and a sensible setup.

Serve static content from the edge

The largest share of a site's weight is usually static: scripts, styles, images and prerendered pages. Put these on a content delivery network so a visitor in Dunedin or Tauranga receives them from a nearby point of presence. Build the pages ahead of time where possible. A prerendered page needs no model call at all, which makes it fast and cheap.

Keep model calls off the critical path

An AI feature should enhance a page that already works. A few patterns help:

• Render first, enhance second. Show the full page, then load the assistant widget after the main content.
• Stream responses. Streaming lets the first words appear within moments, which feels faster than waiting for a full answer.
• Cache repeat answers. Questions like "what are your opening hours" repeat constantly. Store the answer and skip the model.
• Choose the smaller model first. A compact model often handles routine tasks well, and you can reserve a larger one for harder requests.

A quick streaming example

const res = await fetch("/api/chat", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ message }),
});
const reader = res.body.getReader();
const decoder = new TextDecoder();
for (;;) {
  const { done, value } = await reader.read();
  if (done) break;
  output.textContent += decoder.decode(value);
}

Your backend can forward to any OpenAI compatible endpoint, including the app.nz gateway, and pass the stream straight through.

Use a .nz address

A .nz domain tells local visitors they are dealing with a New Zealand business, and it keeps your brand clear in search results for local queries. app.nz site hosting includes subdomains, so a project can go live at a name you choose on app.nz while you decide on a custom domain.

Measure with real tools

Open your page in Chrome DevTools or run Lighthouse and watch three numbers: Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint. Aim for the "good" thresholds Google publishes for each. Give every image a width and height, lazy load anything below the fold, and load fonts with font-display: swap. Test on a mid range phone with a mobile connection, since that reflects many visitors.

Deploy from git

Keeping the site in a repository gives you history, review and easy rollback. With app.nz, you can host the repository and publish the site from the same place, which keeps your build, your code and your live URL together. Tag a release before a big change, so reverting is a single command.

Checklist

1. Prerender or statically build every page that can be.
2. Load AI features after the main content and stream their output.
3. Cache common answers.
4. Use a .nz name or an app.nz subdomain.
5. Check Core Web Vitals on a phone before each release.

Ready to try it? Create a project in the site builder, push your repository, and see your page live in minutes.