Astro web design in Australia is still a minority position, and most business owners have never been shown an Astro website. Most agencies build on WordPress because they always have, and the tooling is familiar. We build every Newcastle Web Co site on Astro, a modern way of building websites, because the result is measurably better: 90 or higher out of 100 on Google's mobile speed test (Lighthouse), 100 for accessibility, best practice and SEO, pages under 500 KB, which is light enough to load quickly on a phone, and no JavaScript (the code that makes a page interactive) sent to the visitor's browser unless the page needs it. Here is what that actually means for a business getting a site built.
Astro is a web framework, the set of tools a site is built with, that turns every page into a finished file before the site goes live, so the browser gets a complete page the moment someone asks for it. There is no server putting the page together, no database to look things up in, and no extra software starting up in the browser before the text appears. That is why the scores land where they do, and why the hosting is both cheaper and harder to hack.
What Astro actually is
Astro is a framework built around one idea: send the browser less to do. Your pages are generated once, before the site goes live, and copied to Cloudflare's network of servers. When someone in Merewether opens the site, they are handed a finished page from a server in Sydney. Nothing is put together while they wait.
Most modern frameworks do the opposite. They send a large bundle of JavaScript 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 sends no JavaScript to the visitor by default, and only adds it where something genuinely needs to be interactive, such as a menu that opens.
The practical result is a score of 90 or better on Google's mobile speed test, and 100 on accessibility, best practice and SEO, 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
Every project ships with these, including the $1,800 Starter. Accessibility sits underneath all of them and is built to WCAG 2.1 AA, the international standard for making websites usable by people with disabilities, from the start rather than checked at the end, which matters most for the sectors covered on NDIS website design.
- 90+ on Google's mobile speed test, 100 on the other three, verified at handover
Pages under 500 KB
, light enough to load quickly on a phone, measured on Cloudflare Pages at handoverNo unnecessary JavaScript
, so nothing loads that is not doing a jobFull SEO, AEO and GEO
, meaning schema on every page (the behind-the-scenes code that tells Google what your business is) plus llms.txt and llms-full.txt, plain-text summaries of the site written for AI toolsMobile first design
, tested across every screen size rather than checked once at the endSearch Console and GA4 connected at launch
, Google's free tools that show how people find the site and what they do on it, so you can see what the site is doing from day one
Why static HTML changes your rankings
Googlebot, the program Google uses to read websites, reads your pages to work out what they are about. On a static site, one built as finished pages ahead of time, it reads complete, fully formed content the first time it asks for a page. 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 built in the browser and Google's reader gives up before that finishes, the content never makes it into Google's listings. It is uncommon with good caching, and it is miserable to diagnose when it happens.
Suburb pages are where this compounds. A Growth build usually ships 10 to 30 of them and an Authority build up to 50, each targeting one suburb and service combination. Every word on every one is read the first time Google visits, 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. Much of the speed comes from finished files sitting physically near the people opening them.
There is no server running code each time someone opens a page, no database, and no admin login on the server to attack: even the CMS on our builds signs in through a separate service. That removes almost every way in that hackers use on a typical WordPress site, and it is why maintenance on an Astro site means applying security updates to the software it is built with, rather than cleaning up after a break-in. Hosting, the security certificate (SSL) that puts the padlock in the browser bar, uptime monitoring that checks the site stays online, and those updates are all covered by the Maintain plan at $49 a month, detailed on our hosting and support page.
Three custom builds, 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. Three to five pages, custom-built for your business on Astro, already optimised for performance and structure, with a design of its own made for your business. It looks professional, it loads fast, and it is fully SEO ready. Three weeks.
The Growth and The Authority. Designed and built from scratch for your business, or started from one of our starting designs, built with your name, your photos and your copy, and no one else gets that design. More pages, and the suburb pages on top. That is the difference you are paying for.
Both run on Astro. Both hit 90 or better on a phone and 100 on the other three. The difference is scope: how many pages and suburb pages you need, and how much design work goes into them. The packages page puts both side by side with the prices.
When a custom Astro build is not the right fit
Worth saying plainly, because a page that only lists advantages is a page nobody believes.
First, what Astro can do, because it is often undersold. Most pages are built ahead of time, but a site is not limited to them. Astro sends JavaScript wherever a page needs it, so a page can pull in live information, such as stock levels or open appointment times, and embed the booking tools businesses already use, such as Cliniko, ServiceM8, Calendly or Fresha. It can also build a page on the server at the moment someone opens it, running on Cloudflare, when that page has to be different for each visitor. This site is built on Astro, and the AI receptionist on it books appointments straight into Google Calendar.
The real limit is scope and cost, not the framework. A large online shop with thousands of products, a checkout, stock control and payments, or a members' area with accounts, logins and billing, is a software project in its own right. Platforms such as Shopify have already built and tested those parts, and paying for one is usually far cheaper than having them built from nothing, on Astro or anything else. Embedding a booking tool is ordinary website work; a full store or member system is a different job with a different budget.
Publishing works differently, not less. Every content change rebuilds the site and puts the new version live, which takes about a minute. On our builds you can change your own text and photos at any hour in the CMS that comes with every site, or send the change to us under your support plan.
We would rather tell you that before the quote than after the invoice. If your project sits on the wrong side of that 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, behind-the-scenes code that labels each question and answer for Google, which it reads when filling its AI Overviews and featured snippets. It also includes LocalBusiness schema, which tells Google what your business is and where it works, llms.txt and llms-full.txt, plain-text summaries of the site for AI tools, and a robots.txt file, the instructions a site gives to the programs that visit it, that lets the AI tools' readers in: GPTBot, PerplexityBot, ClaudeBot and Google-Extended.
Most local agencies write a meta title, the page title Google shows in its results, and call that SEO. We build in all three: traditional SEO for Google's normal 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 web development 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 8 November 2026.











