A site made of code instead of a system. No login, no updates, nothing that can be hacked. For sites that change rarely this is the fastest and safest option.
A content system brings a database, a login area and monthly updates. That makes sense when things change often. On a site with six pages touched twice a year it is pure overhead.
The same site as pure code, delivered as finished files. It loads in a fraction of a second, has no login area anyone could attack and works exactly the same in five years.
You cannot change texts yourself without asking us. For many that is a drawback and for some an advantage, because nothing goes wrong unnoticed. Anyone changing something monthly is better served by a CMS.
LADEZEIT // UNTER 1 S
With no database and no plugins only what you see remains. That is not optimisation, it is simply little to begin with, which is why it holds up when nobody is watching any more.
SICHERHEIT // KEIN LOGIN
There is no login area, no database and no third party plugins. That removes the three most common routes by which small websites get taken over.
WARTUNG // FAST KEINE
There is nothing that needs monthly updating. The running costs are hosting and a domain. Changes we make on request and bill by effort.
If you run a blog or want to. Then you need an area where someone can write without us, and that is exactly what a content system does well.
If several people maintain content independently. As soon as two want to change something at the same time, asking us is the bottleneck, and we become the problem rather than the solution.
And if you sell products. A shop needs stock, orders and payments, which is precisely the database we leave out here. Our e-commerce pages cover that.
Reference values from our projects without a content system, not a guarantee
After these four answers we tell you which approach fits, even when it is the one we earn less on.
From 2.500€ for a compact site, so within the same range as one with a content system. The difference is not the price but the running costs and who makes changes.
Texts and images not without us, correct. For many businesses that is no loss because they change something once or twice a year anyway. Anyone wanting to do it more often is better served by a content system, and then we build one.
Hosting and a domain, nothing else. There are no licences, no plugin subscriptions and no monthly maintenance because there is nothing to update. Changes we bill by effort when they come up.
Yes, but it is a project of its own and not a switch. So we clarify beforehand whether a blog or an editorial team is foreseeable. If so we build with a system straight away, because that costs less than building twice.
Technically it is the opposite. Static sites are why the fastest websites on the internet are fast. Old fashioned would be accepting a database, a login area and monthly updates for a site with six pages.