Top End Care · 2026
An NDIS provider site that is honest about registration and loads in one second
A custom Astro build for a Darwin disability support provider: eight service pages, plain answers for families new to the NDIS, and Lighthouse scores of 98 to 100 on the live site.
- Web App
- Performance
- SEO
- Astro
- Tailwind CSS
- TypeScript
- Cloudflare
- 98 to 100
- Mobile Lighthouse performance
- 1.0s
- Mobile Speed Index
- 8
- Service pages, one template
Challenge
Top End Care supports people with disability across Darwin, Palmerston, and the Top End, but its NDIS registration was still in progress. Families choosing a provider are making one of the most personal purchases of their lives, often on a phone, often while overwhelmed. The site had to earn trust quickly, say truthfully who the provider can support today, and make the next step easy.
Approach
We built a fully static Astro site on Cloudflare with every word of copy held in one content folder, separate from the templates. The registration status lives in a single setting that drives the copy site-wide, so nothing claims what is not yet true and one change updates every page when approval arrives. Eight services each get their own page, a "New to the NDIS" guide answers the questions families actually ask, and technical SEO, structured data, and an llms.txt file for AI assistants shipped as part of the build.
Outcome
The live site scores 100 for accessibility and best practices on every page we tested, with mobile performance between 98 and 100 and a Speed Index of about one second. Enquiries go straight to the provider’s inbox, every page has its own branded link preview, and a custom audit fails the build if the design system or the content rules are broken.
Choosing a disability support provider is not a casual decision. The person reading the site may be a parent, a carer, or a participant managing their own plan, and they are looking for evidence that the provider is reliable, local, and straight with them. A slow page or a vague promise costs the enquiry.
Top End Care had a harder version of that problem. Its NDIS registration was still in progress, which meant the site could not simply copy the confident language of established providers. It had to be useful and honest at the same time.
Honest copy, controlled from one place
Registration status is a single object in the content layer. Every page that mentions it, from the About story to the FAQs to the structured data search engines read, draws on that one setting. The site says plainly that Top End Care currently supports self-managed, plan-managed, and private-pay participants, and no engine can summarise the business as registered when it is not.
Services that registration gates in practice were left off rather than promised and then unfulfilled. When approval comes through, switching the status and filling in the number updates the whole site without hunting through templates.
Built for the person on a phone
The site ships as plain static pages with no client framework. On the live site, mobile performance scores run from 98 to 100 across all eleven pages tested, and accessibility and best practices score 100. Text colours were chosen against documented contrast ratios, buttons are at least 44 pixels tall, and all motion switches off for visitors who ask for reduced motion.
Getting from a 96 to a consistent 98 to 100 took specific, measurable work: trimming the heading font from 86 KB to 38 KB, building the stylesheet into each page so it no longer blocks first paint, showing on-screen content immediately instead of waiting for a scroll script, and setting year-long caching for fonts and build files. Mobile Speed Index fell from as high as 4.7 seconds to about one second.
Findable by search engines and AI assistants
Every page carries its own title, description, and canonical address, and the whole site shares one linked structured-data graph describing the business, its address, its service regions, and its eight services. A generated llms.txt gives AI assistants the key facts first: registration status, who can be supported now, regions, and contact details. Each page also gets a branded 1200 by 630 preview card, cropped at build time, so a link shared on Facebook, LinkedIn, WhatsApp, or Slack looks like it came from a real organisation.
A design system that enforces itself
The content, the components, and the design tokens are separated, and npm run audit
checks all three: only the type scale sets font sizes, only the spacing scale sets gaps,
every colour resolves to a token, every image has alt text, and no copy hides inside a
template. If a future edit breaks a rule, the check fails before the change goes live.
That is what lets the team update the site themselves without slowly eroding it.