Architecture
adhd-autism.net
A solution-architecture summary — how the system is designed, and why. Verified from the source code.
- Type of system
- Information website (with interactive self-tests)
- Users
- People researching ADHD and autism
- Hosting
- United Kingdom
- Main stack
- Lightweight front end (no accounts, no database)
- Status
- Live
- Built for
- Client — Plexus Psychiatry's education funnel
The problem
People spend years wondering whether they have ADHD or autism. Most ‘free tests’ hide the result behind an email, then push straight to a paid assessment. Plexus needed the opposite: a genuinely useful, no-sign-up resource that earns trust first — sometimes by telling people they probably don't need a clinic at all.
How it fits together
Users
People researching symptoms
Front end
Fast content site + self-tests (scored in the browser)
External services
- Onward link to Plexus Psychiatry
Tech stack
Front end
- A fast, no-sign-up content site
- Self-tests scored in the browser — no account, no email
Backend
- None required — the tests need no server to score
Database
- None — no personal data is collected
Hosting
- United Kingdom
Key design decisions
Show the result without asking for an email
Why: Trust first. The usual ‘free test → give us your email’ is the opposite of trust for a clinic that wants informed patients.
Trade-off: Fewer captured emails, far more goodwill.
Name the free NHS route next to the paid one
Why: Honesty converts better for a clinic that wants patients who've had a straight answer.
Trade-off: It sends some people away — by design.
No accounts, no sign-up
Why: Speed and privacy: there's nothing to log into and nothing to store.
Trade-off: No personalisation or saved history.
Security & data protection
- Hosted in the United Kingdom, over TLS.
- No accounts, no sign-up, and no personal data collected by the self-tests — results are worked out in the browser.
Built to hold up
- Performance
- A fast, largely static content site; the self-tests run entirely client-side.
- Availability
- Static-style content is simple to keep online behind nginx.
- Scalability
- No accounts or database means traffic scales trivially.
Results
- PageSpeed (mobile): 94 / 100, largest content painted in 3.2s.
What we'd do next
- Publish an anonymous, aggregate view of which questions people ask most, to steer the articles.
- Add a short privacy note making the ‘nothing leaves your browser’ promise explicit.