Exitus Agency

Service · Digital & Tech

Fast, multilingual websites

We build static websites: the server hands over pages that are already made instead of assembling them on every visit. They load fast, each language lives at its own address — and therefore gets indexed — and the code does not degrade on its own. What does change over time sits outside the site, and that is what the periodic review is for.

Why static, and what that changes

What makes a site load fast is, above all, not sending the browser what it doesn’t need. A static site is already made before the visit arrives.

A content management system, by contrast, assembles each page the moment someone asks for it, querying a database and running the code of several extensions. That machinery makes complete sense when people publish daily. For a site that changes four times a year, it is weight paid for on every visit.

The practical consequence is not only speed: it is that there is no surface degrading on its own while nobody looks.

What it is built with

HTML, CSS and JavaScript written by hand. No fashionable framework unless the project calls for one: on a corporate site it usually adds weight and an expiry date nobody asked for.

When there are several languages or many pages, a generator of our own builds each page from a single source of content. A correction is made once and appears in all three languages: no version falls behind.

The code lives in a repository with every change recorded — any earlier point can be restored — and it is published on distributed static hosting, with no server to administer.

We use AI tools to produce: they cut the time, not the judgement. What gets published is decided by a person. And design and catalogue still go through the Adobe environment, where the hand still makes the difference.

And depending on what you need, it is not always the same:

  • Corporate site, catalogue or landing page → static, which is what we describe here.
  • Someone publishing daily → a content management system: the one you already use, or a light one.
  • Shop with inventory → a commerce platform. That is not built by hand.
  • Internal tool → a bespoke application, which is a different commission.

If what you need is not what we do best, we will tell you before we start.

One language, one address

Translating the text is not enough. If the other-language versions only appear once a button is pressed, search engines and AI engines never see them: they do not click. It is the most common mistake and the most expensive one, because the translation work is already paid for and nobody reads it.

Each language gets its own address, is served already translated in the code, and hreflang links tell each engine which one to serve to whom. That is what turns a translation into traffic.

Where the hand still makes the difference

Some work no tool does for you. The catalogue, the composition, the typographic judgement: there the craft still decides, and we still work by hand.

AI tools have cut production time a great deal, and you feel that in the schedule and in the price. What they have not cut is the judgement needed to know what deserves to be published.

Maintenance does not disappear: it moves

On a site built with a content management system, maintenance lives in the code. On a static one that work goes away — but it leaves no gap: what needs watching has moved to the perimeter, which is exactly where nobody looks.

That it stays alive. The domain and its certificate, which expire. The contact form, which can stop sending in silence with nobody noticing: people simply stop calling. And who still has access to the site months later.

That they keep finding you. We check, using each engine’s real identifiers, that ChatGPT, Perplexity, Claude and Google can read you. This changes on its own: in August 2026 a hosting provider began blocking them by default, and none of the affected sites had done anything wrong.

That it improves. What needed JavaScript a year ago is three lines of CSS today, and a site built a year ago is built with a year-old toolkit. It is not broken: it is professionally out of date, and the client cannot see that alone.

A tool of ours runs the review; a person reads it. The review monthly, the report quarterly.

Frequently asked questions

What technology do you build sites with?

Static, by default: the server hands over pages that are already made instead of assembling them on every visit. It suits most of the sites we are asked for — corporate sites, catalogues, landing pages — because they load sooner and depend on nothing that updates itself. We have nothing against content management systems: when several people publish daily, or a shop carries thousands of references, they are the right tool and we say so. What we do not do is set up that machinery for a site that changes four times a year.

What if I already have a WordPress site?

We look at it before proposing anything. If it works and serves you, we leave it where it is and work on what does need help — usually making sure search engines and AI engines can read it properly. Rebuilding only makes sense if the change gives you back something measurable.

Can you build a site in several languages?

Yes, with each language at its own address. Translating the text is not enough: if the versions only appear once a button is pressed, search engines never see them and the translation is not working for you.

Who updates the content afterwards?

It depends how we set it up. For content that rarely changes, we handle it and it takes minutes. For content that changes daily, we build the editable part without dragging in the weight of a whole CMS.

Do you provide maintenance?

Yes, but not the kind that patches a system degrading on its own: on a static site that does not exist. We watch what does change while nobody touches it — the domain and its certificate, the contact form that can stop sending in silence, who still has access, and the rules outside. Each month we run the review with a tool of our own and read it ourselves; each quarter you get in writing whether anything changed — we don’t write just to write.

Shall we talk about your site?

Tell us what you have now and what you would like it to do. If what you have already works, we will tell you that too.

Write to us →