Scope
You and I agree on the pages, what each one has to do and what content exists for it. On a static site the page list is the estimate.
Static websites
Static websites, hand-built with no CMS underneath.
Some sites do not need WordPress. When the content changes a few times a year and nobody on your side wants to log in and edit it, a hand-built site is faster, safer and cheaper to keep alive. No database, no plugins, no admin login to break into.
Built differently
Not every website needs a content management system.
WordPress exists so people can publish. If nobody on your side is ever going to publish, you are maintaining a database, an admin login and a plugin stack for a site whose text changes twice a year.
A static site is the same pages, written by hand and served as plain files. Nothing is assembled on the fly, so there is very little to load and very little that can go wrong. It keeps working while nobody touches it.
The trade is worth saying out loud: you do not edit it yourself. Content changes come to me and I publish them. For most businesses that is already how it works, only now they are not paying to maintain a dashboard nobody opens.
Overbuilt
A theme and a page builder for a site whose text changes twice a year. You maintain all of it anyway.
Left to rot
A WordPress site nobody updates. Every month it drifts further out of date and closer to being an emergency.
Built as files
Plain pages, served directly. No plugins to update, no login to attack, and nothing that quietly breaks a year from now.
After launch
What keeping a static site alive actually involves.
There are no updates to install and no plugins to patch, so the ongoing work is different. It is the server, the certificate, the backups, and making sure form messages still arrive.
What's included
What a static build actually includes.
The pages are written by hand, but everything around them is held to the same standard as any other site I build.
Hand-written HTML and CSS
Every page written for your content instead of assembled from a template. Semantic structure, so search engines and screen readers both read it properly.
Images prepared properly
Photos are resized and converted to modern formats at several widths, with real dimensions in the markup, so a phone does not download a desktop-sized photo.
Contact forms that deliver
Forms are handled on the server and sent over authenticated mail with spam filtering, and they still submit with JavaScript switched off.
Indexable by design
Titles, descriptions, a sitemap, and a catalog that exists in the HTML itself rather than being drawn in later by scripts.
Kept online and certified
The site runs on infrastructure I manage, with the certificate issued and renewed for you and a backup kept off the server.
Content changes done for you
You send the text or the photographs and I publish them. No dashboard to learn and nothing to break by accident.
Pages
Hand-written HTML
Styles
CSS, no framework
Scripts
Vanilla JavaScript
Forms
Server-side, authenticated mail
Database
None
Performance
Fast because there is almost nothing to send.
A static page is not optimized after the fact. It is small to begin with, and staying small is the whole discipline.
Payload
Almost nothing to load
No framework, no plugin scripts, no builder stylesheet. The browser is handed the page and the page is all there is.
Images
Sized for the layout
Converted and generated at several widths, with the real dimensions written into the markup so the layout never jumps while they load.
Fonts
Loaded without blocking
Cut down to the characters the site actually uses, and never allowed to hold up the first paint.
Caching
Set once, correctly
Files are served with long cache headers and renamed whenever they change, so returning visitors download nothing twice.
How I work
How a static build runs.
Content first, because on a site like this the content is the build.
Content
Text and photographs are gathered before anything is built. This is the step that decides the date, and the one that is always underestimated.
Design
Layouts are drawn and approved before a line of production HTML is written.
Build
The approved pages are written by hand, images are processed and forms are wired up on a staging address you can open and check.
Launch
The domain is pointed, the certificate issued, the sitemap submitted, and redirects put in place if this replaces an older site.
After
I keep it online, keep the certificate valid, keep a backup off the server, and publish your changes when you send them.
Why Jaha Web
Why this instead of WordPress.
Nothing to patch
No plugin stack means no weekly update, no compatibility break and no plugin vulnerability waiting to be patched.
No login to break into
No login page and no database. The way small sites usually get hacked simply does not exist here.
It stays as you left it
A static site does not drift. What launched is what is there next year, unless you ask for a change.
Keeping it alive
What it costs to keep it online.
Hosting and upkeep are billed once a year, because a site like this needs little attention in between. The build itself, and anything added to it later, is quoted from what it involves.
Online
€400 a year
The site stays online, backed up and watched, on my server.
- Runs on my server, with the certificate issued and renewed
- Daily backup taken and kept off the server
- Checked continuously that the site answers, not once a month by hand
- Contact form delivery tested regularly, so it does not fail quietly
- Content changes billed at 50 EUR an hour
Online and changes
Quoted
Everything above, plus your content changes handled through the year.
- Everything in Online
- Your text and photographs published as you send them, usually the same day
- Send as much as you like in one go, it counts as one round
- New catalog entries added as the work grows
- A reply the same working day
Built to order
Quoted one-off
The site is custom, so things can be added to it long after launch.
- A small upload panel, so you can put gallery photographs up yourself
- Calculators and configurators that work the way you quote
- Extra pages as the work grows, catalog entries included
- Built once and priced once, not rented
- Yours once it is paid for, whether or not you stay on a plan
There is no separate hosting bill. The server is part of keeping the site alive, not a product bought on the side. A new section or a whole new catalog is a build, and is quoted as one.
Frequently asked
Before I start.
The questions people actually ask once they hear the site will not have a dashboard.
Can I edit the text myself?
No, and that is the trade. Changes come to me and I publish them, usually the same day. If editing pages yourself matters to you, you want WordPress, and I build those too.
What if I need a shop or a blog later?
Then this is the wrong choice, and I will say so before you pay for it. A catalog that changes a few times a year is fine as files. A shop is not.
How long does it take?
From about three weeks once the content is settled. The writing and the photographs almost always decide the date, not the build.
Is it worse for Google?
No. Search engines read plain HTML better than anything else. A static catalog sits fully in the source, which is more than can be said for a lot of builder-made pages that draw their content with scripts.
What happens if you disappear?
You get the files. Plain HTML, CSS and images, which any developer can pick up. There is no database export to negotiate and no proprietary format to unpick.
Do the contact forms actually work?
Yes. They are handled on the server and sent over authenticated mail with spam filtering, so they are far less likely to end up in spam. They still submit with JavaScript turned off.
Can it be moved to WordPress later?
Yes. The content is clean semantic HTML, so it converts without a rewrite. That is a normal job, not a rescue.
Who keeps it online?
Usually I do, on the same infrastructure as every other site I look after, with the certificate and the backups handled. If you would rather stay where you are, that works too.