Web Design4 December 2025 · 7 min read

Custom Astro web design: why every build we ship runs on Astro

Astro builds the whole page before anyone visits it, which is why the numbers are what they are. Here is what that means for a Newcastle business getting a site built, in plain terms.

By Newcastle Web Co, Cameron Park NSW 2285

Scroll
Illustration of a web designer on a Newcastle rooftop at sunset beside a laptop showing a green page speed gauge and a glowing Astro rocket emblem

Astro web design in Australia is still a minority position. Most agencies build on WordPress because they always have, and the tooling is familiar. We build every Newcastle Web Co site on Astro because the output is measurably better: 95 or higher on Google Lighthouse, load times under 2.5 seconds, and no JavaScript shipped to the browser that the page does not need. Here is what that actually means for a business getting a site built.

Short answer

Astro is a web framework that builds every page into finished HTML at deploy time, so the browser gets a complete page on the first request. No server assembling anything, no database query, no framework booting up before text appears. That is why the numbers land where they do, and why the hosting is both cheaper and harder to attack.

What Astro actually is

Astro is a framework built around one idea: send the browser less to do. Your pages are generated once, at build time, and pushed to Cloudflare's network. When someone in Merewether opens the site, they are handed a finished document from a server in Sydney. Nothing is assembled on demand.

Most modern frameworks do the opposite. They ship a large JavaScript bundle and build the page inside the browser after it arrives, which is fine on a fast laptop and noticeably less fine on a five year old phone with two bars of reception. Astro defaults to zero client side JavaScript and only adds it where something genuinely needs to be interactive.

The practical result is a Lighthouse score of 95 or better with no tuning. That is the starting point of every build we do, not something we chase at the end.

What every build ships with

These are not targets. They are the output of every project, including the $1,800 Starter.

  • 95+ Google Lighthouse, verified at handover
  • Load times under 2.5 seconds, measured on Cloudflare Pages from Australian locations
  • No unnecessary JavaScript, so nothing loads that is not doing a job
  • Full SEO, AEO and GEO, meaning schema on every page plus llms.txt and llms-full.txt
  • Mobile first design, tested across every screen size rather than checked once at the end
  • Search Console and GA4 connected at launch, so you can see what the site is doing from day one

Why static HTML changes your rankings

Googlebot reads your pages to work out what they are about. On a static site it reads complete, fully formed content on the very first request. Nothing sits behind a script that has to run first, so nothing gets missed.

A WordPress site running a JavaScript heavy page builder does not always behave that way. If content is rendered in the browser and the crawler gives up before that finishes, the content is not indexed. It is uncommon with good caching, and it is miserable to diagnose when it happens.

Suburb pages are where this compounds. A Growth build ships 30 of them and an Authority build ships 50, each targeting one suburb and service combination. Every word on every one is read on the first crawl, every time. Our local SEO guide explains why that page count does more for local search than anything else you can buy.

Cloudflare Pages, and why every site lives there

Cloudflare runs data centres in over 300 cities. A visitor in Hamilton loading a site hosted on Cloudflare Pages is served from the closest one, which is Sydney. The load times are not the result of clever optimisation, they are the result of putting finished files physically near the people opening them.

There is no server executing code on each request, no database, and no admin login page. That removes almost the entire attack surface a traditional CMS carries around, and it is why maintenance on an Astro site is framework patching through the build pipeline rather than incident response. Hosting, SSL, uptime monitoring and that patching are all covered by the Maintain plan at $50 a month, detailed on our hosting and support page.

Custom build or proven base, and the honest difference

Not every build we do is the same, and we would rather say so plainly than let a price imply something it should not.

The Starter, $1,800. A proven professional base, already optimised for performance and structure, adapted to your brand with your copy and content on top. It is not drawn from scratch and we do not claim it is. It looks professional, it loads fast, and it is fully SEO ready. Three weeks.

The Growth and The Authority. Designed and coded from scratch. Every component is built for your business, with nothing shared with any other site we have made. That is the difference you are paying for.

Both run on Astro. Both hit 95 or better. The question is whether you need a professional site working quickly, or one that is entirely your own from the first pixel. The packages page puts both side by side with the prices.

What Astro is not good at

Worth saying plainly, because a page that only lists advantages is a page nobody believes.

Astro is a static site generator, so anything that has to change per visitor, per login or per second is not its natural job. A large ecommerce catalogue with live stock levels, a membership area with accounts and billing, a booking system with real time availability: all of those want a server doing work on each request, and there are better tools for that than a framework built to avoid it.

The second limit is publishing volume. Content changes go through a build and a deploy rather than a browser login. That is a good trade for a service business publishing a few times a month, and a bad one for a newsroom publishing twice a day. On our builds those changes are made by us and covered by your support plan, which is fine at two edits a month on Maintain or four blog posts a month on Scale, and the wrong shape entirely if you want to post something at midnight yourself.

We would rather tell you that before the quote than after the invoice. If your project sits on the wrong side of either line, we will say so and point you at what actually fits. The WordPress vs Astro comparison works through where that line falls in more detail.

AEO and GEO are in the build, not on top of it

Every site we ship includes FAQPage schema, which is the structured data Google reads when populating AI Overviews and featured snippets. It also includes LocalBusiness JSON-LD, llms.txt and llms-full.txt for AI crawlers, and a robots.txt that allows GPTBot, PerplexityBot, ClaudeBot and Google-Extended through.

Most local agencies add a meta title and call that SEO. We ship the full three channel stack, traditional SEO for Google's organic results, AEO for its AI answers, and GEO for ChatGPT and Perplexity, on every project at every tier.

The full build detail is on the website design page. If you would rather just ask whether Astro suits what you are trying to do, start a conversation and we will tell you honestly, including when the answer is that you need something else.

Written by Newcastle Web Co, web design & seo in Cameron Park NSW 2285. Last updated 19 August 2026.

Web Design questionsStraight answers. No nonsense.

What people ask about this.

Astro is a web framework that generates finished static HTML at build time, so a visitor's browser receives a complete page on the first request instead of waiting for a server to assemble one. The result is faster loading, higher Lighthouse scores and simpler, more secure hosting. Newcastle Web Co builds every client website on Astro and deploys it to Cloudflare Pages.

For most local service businesses, yes. Astro produces faster pages, a far smaller attack surface and SEO ready output by default. A correctly built Astro site scores 95 or better on Lighthouse with no additional optimisation work. WordPress can reach similar numbers, but it takes plugin configuration and continuing maintenance to hold them.

The Starter package, three to five pages on a proven professional base, takes three weeks from sign off to launch. The Growth and Authority timelines are confirmed at the consult, because they depend on page count, how much of the design is being drawn from scratch, and whether we are writing the copy or working from yours.

Every build, including the $1,800 Starter, ships with a 95 or better Google Lighthouse score, sub-2.5-second load times, keyword research and on page SEO, LocalBusiness and FAQPage schema, AEO structured FAQ sections, GEO entity signals with llms.txt, mobile first design tested across every screen size, and Google Search Console and GA4 connected at launch.

Keep readingAll posts
Newcastle Web CoSee how we build.See how we build.

Fixed prices, no templates, and we keep running the site after it launches.

← All work