Some websites are tested by how fast they load. Others are tested by whether a parent who lands on them at two in the morning, after a fight with a fifteen-year-old, feels that someone understands them. Hila Azrad’s site is the second kind, and this is the case study of how such a site gets built.
What you will learn from this post
- How to build a site for a service professional whose clients choose them for who they are, not for price
- Three content layers that turned a brochure site into a site parents come back to
- Exactly what the client asked for, including two requests that look like the opposite of convention
- What was actually measured, including the number we would rather not write
- What is still open, and what it teaches about a site for any counselor, therapist or lecturer
Who this post is for: counselors, therapists, lecturers and professionals whose site is a calling card rather than a shop, who want to understand what separates a site that merely “exists” from one that works. And anyone curious how a real process with a real client looks, detours included.
Who the client is
Hila Azrad is a parenting coach and a specialist in at-risk teenagers. The sentence she opens every conversation with, and the homepage too, is: “Behind every behaviour there is a story.” She works with parents of teenagers who are drifting away, with parents of young children, with schools and communities, and offers an emergency call for parents in crisis.
Before she came to us, Hila had tried to build the site herself on Wix. She found it far more work than she expected, kept putting it off day after day, and eventually came to us to build something whole: a site that sounded like her, with room for the knowledge she gathers every day, and a way for a parent to get an answer without calling.
The first decision: a center brand, not a personal one
Midway through the work, Hila arrived with a decision that shaped everything else: the business would not be branded only as “Hila Azrad” but as a center, Oaf HaChol | The Parenting Center, led by her. The logic: the phoenix is a fresh start. Exactly what happens to parents who reach her after trying everything.
For a website that means: the logo, the brand name on all 49 pages, the schemas search engines and AI read (Organization, Person, WebSite), the titles and descriptions, all line up to one name. We did it in a day, because on a site built in code the name sits in one place and spreads from there to every page.
The design: luxurious, light, and in the typeface Hila chose
At the start we proposed a soft pastel palette. Hila rejected it: she wanted formal, elegant, luxurious, and “squarer” fonts. The final colours are hers, from the existing branding: deep fuchsia and gold on a cream ground. Headings are set in Karantina, a narrow, dramatic Hebrew display face she chose herself out of seven directions we showed her, and body text in Assistant, a face that reads comfortably without glasses.
That last point is not cosmetic. Hila’s audience is parents aged 40 to 55, and many of them do not see well without glasses. So the project rule: never shrink a font to make something fit. Shrink the image. And text on the cream ground got AAA contrast, beyond what the law requires.
On top of that came the effects that separate a site from a template: smooth scrolling, a gentle parallax in the hero, reveal on scroll, and a services section whose cards stack on top of one another. All of them off for anyone who asked their browser for reduced motion.
Three content layers that did not exist before
This is the real difference between the old site and the new one. Beyond the eight service pages (emergency call, personal guidance, at-risk youth, early childhood, screens, the language of safety, lectures and the lecture catalog), three places were built that a parent returns to:
1. A knowledge center by topic. Ten topics, each its own page with its own address. In the first version it was a single page with a filter, and Hila sent a screen recording: “I can’t see that it’s sorting down there.” She was right. A page per topic is clearer for a parent and better for Google, which gets a focused page instead of a list that changes on click.
2. Parents ask: 74 real questions. Questions parents actually asked Hila, each with a short, practical answer: safety, screens, boundaries, leaving religion, social difficulties, highly sensitive children. And one requirement from Hila that looks like the opposite of every designer’s instinct: the questions are shown in a deliberate jumble, not by topic. Her explanation: a parent looking for an answer about screens passes a question about boundaries on the way, and discovers it is theirs too. Free-text search was rejected for the same reason. It is the page we love most on the site, and we did not design it.
3. A personal journal. Fifteen first-person entries, outside the professional hat, with personal photos. A separate axis from the articles, on purpose: the knowledge center is “what to do”, the journal is “who I am”. A parent deciding whether to call reads the second.
How Hila’s content reaches the site, and why the numbers here will keep growing
Hila writes. So it reaches the site without anyone copying and pasting, we built her a process: she fills in a Google Form built to a template we prepared (title, category, article body) and drops a cover image into a shared Drive folder, and a script turns it into a live post automatically. That is why the numbers in this post, 74 questions, 15 journal entries, 49 pages, are accurate as of when we wrote it: every form she submits adds an article, without either of us touching code.
And every article gets a safety layer too: text that passes through several hands on its way to a site can get corrupted silently, a word drops, punctuation shifts, and nobody notices until the client reads herself on the site and feels it is not her. So a verification script compares every post against the source word for word before it goes live.
Once, when the personal journal and the parent-questions page launched, Hila sent the text over WhatsApp instead of the form. Even then we did not settle for reading it twice: a script compared 373 paragraphs (the 15 journal entries and the 74 questions) against the original chat export, character by character, and all of them came out identical. And one rule holds either way, form or WhatsApp: we do not add punctuation to a client’s text. Her voice, including her rhythm and her commas, is the product.
The assistant that answers in her name
The site has a digital assistant that answers parents from the site’s own content, points them to the right article or service, and collects a name and phone number when someone wants Hila to call back. Two things matter in the implementation:
- The model choice was tested, not assumed. We ran the same conversations on the small, cheap model (Haiku) and on Sonnet 5. The small one returned broken Hebrew. The large one was clean, followed the rules, and even answered more briefly. The large one was chosen, and the cost per conversation stayed at a few agorot.
- The list of articles the assistant knows is derived from the site, not typed by hand. A manual list goes stale within two weeks and the assistant starts sending parents to broken links.
And the rule that accompanies every assistant we build: it promises no times, gives no discounts, and never says “sent” if it did not send. We expanded on that in an AI rep that answers customers and collects enquiries.
The things you do not see
- A Shabbat gate. The site closes on Shabbat and holidays, by Haifa times, and shows a respectful holding page. Hila keeps Shabbat, and so does her site.
- Accessibility: zero findings in an automated scan of 25 pages, with fixes found along the way, such as a skip link hidden behind another layer. And we say here what we always say: a clean scanner score covers part of the standard; the rest is checked by hand before signing an accessibility statement.
- A cookie banner that actually blocks. There is no Facebook pixel on the site, but there is a Facebook embed that tracks like one, and it loads only after consent.
- A parents’ community with a signup that goes straight into Hila’s mailing system, with consent recorded (time, address, browser) as the law requires.
- Google’s “preferred source” button, which lets a reader mark the site as a preferred source in Google’s AI results.
What was measured, including the number we would rather not write
We ran PageSpeed Insights on the homepage on 25 August 2026, three spaced runs, and took the median:
| Metric | Result |
|---|---|
| Performance, desktop | 100 |
| Performance, mobile | 81 |
| Accessibility | 100 |
| SEO | 100 |
| Pages on the site | 49 |
Update from the same day: mobile rose from 61 to 81. The homepage carries a large hero image, effects, a Facebook embed and a digital assistant, and on a mobile network that showed. We published this post with the number 61 in the morning, because a case study that hides the gap is worth nothing, and ran a performance pass the same day. It demonstrates exactly the point we meant to make in the first place: a site built in code is not fast by itself, it is fast when the work is done, and in other projects we already did it to the end. Here it got done the same day.
⚠️ A note on numbers: a PageSpeed score is a lab measurement and moves between runs. A single run is not a measurement.
What is still open
The site is live, and Hila works with it every day. The open list, as it is:
- Content for the knowledge center: 8 of the 10 topics are still waiting for their first article. The pages exist, stay out of the index until they have content, and switch on by themselves when it arrives.
- A manual accessibility check before signing the statement.
- Agent readiness: the files we wrote about in the Agent Readiness series are not on this site yet. A day of work.
What it teaches about a site for any service professional
Not every business needs 74 questions and a personal journal. But every counselor, therapist, lecturer or lawyer needs the structure behind them:
- A voice. The site should sound like the person, not like “professional solutions at the highest level”. The client’s text, in the client’s punctuation.
- Knowledge that accumulates. A place you can add to every week without a developer, which Google and AI tools read as focused pages.
- An answer without a phone call. Real frequently asked questions, and an assistant that answers from them when the person is not available.
- The things you do not see: accessibility, cookie consent, a Shabbat gate if it is part of the identity. They do not sell, but they are what prevents a problem.
That is exactly what goes into a full brochure website with us, and it is what Hila got.
In summary
Oaf HaChol is a 49-page site for a parenting counselor, built in Astro in July 2026: eight service pages, a knowledge center in ten topics, 74 parent questions in a deliberate jumble, a personal journal, an AI assistant that answers in Hila’s name, a Shabbat gate, and zero accessibility findings. Her text went up character for character, and the new brand spread to every page in a day.
And what is not finished: eight topics waiting for an article, and a manual accessibility check. Mobile speed, published at 61 that morning, was addressed the same day and now stands at 81. We wrote that too, because a case study is not an advertisement. It is a description of work, including the part still ahead of us.