Vienna, Austria

← Notes

Published

A website that stays fast after launch

A business website has one job before it has ten: load quickly, explain the offer, and make it obvious what to do next. Everything else is optional. Most stacks forget that the week after launch.

A page builder, three tracking scripts, a chat widget, and a gallery plugin later, the site that felt fine on your office Wi‑Fi is slow on a tram in Vienna. The client did not ask for that. The stack did it by default.

Why Astro

I build client sites in Astro because the default is HTML, not a JavaScript app pretending to be a brochure. You ship the page. Interactivity is added only where it earns its keep: a language switch, a form, a mobile menu.

That is not a fashion choice. It is the difference between a site that stays fast when you edit a heading, and a site that needs a developer to stay fast.

For coaches and small teams, the useful extras are still there: a CMS so they can change copy, a form that actually arrives, hosting that does not become a second job. The difference is what is not loaded on every visit.

What handover should look like

A finished site is not a folder of secrets. It is:

  • A URL that opens in under a second on a phone
  • Pages a search engine can read without executing a pile of scripts
  • A way to edit text without breaking layout
  • A contact path that goes to a person, not a black hole

SEO starts there. Keywords on a slow page do not help. Clear titles, a real description, a sitemap, and pages that say what you do in plain language do.

The automation behind it

The same build can connect the form to the tools you already use. That is a separate decision. First the site has to be something you are willing to send to a new contact. If it is not, no agent in the background will fix it.

If you have a site that used to be quick and now is not, the first question is not “which AI.” It is: what is the site actually doing for the business, and what can we delete.