Fast because it is simple
A static site is a set of finished files. There is no database to query when a visitor arrives, no plugin to patch and no page builder adding weight to every page. The page is already built, so it loads quickly on a mobile connection, and there is far less that can break or be attacked. That is why we build this way, and why this very site is built this way.
Speed is not a vanity. Google measures real-user page experience through Core Web Vitals, and a slow first screen loses people before they read a word. We measure our own pages in a lab, label the figures as lab figures and keep the first screen light, with the main text readable even if scripts are blocked.
Built before you pay
For one product page, we build first. You see it on our domain, click through it and decide. If you keep it, it moves to your domain with the source the same day. If you do not, you owe nothing. That is not a promotion. It is how we make the work visible before you spend, and it keeps us honest about how good the page is.
Larger sites follow the same rule in a different shape: you see a working version before it is finished, you approve each stage and the quote is fixed. Domain and hosting fees are paid by you to the provider directly. Photography and ongoing content are not included, as the list above says.
What the site is for
A site earns its keep by doing one job: taking a visitor from an ad, a search or a link to an enquiry or an order. That is why each page we plan has one offer and one next step. The Meta and Google campaigns we run send traffic to such pages, and the SEO work makes sure the pages can be found and understood by search engines and AI assistants.
After launch, a site needs a little care: a changed price, a new photograph, a renewed domain. The website care plan covers that for sites we built. For anything more specific, a custom tool such as a calculator can sit inside or beside the site. We promise the build, the checks and the handover. We do not promise what the site will earn.
A closing word on content. A fast, tidy site with thin or vague text still disappoints, so we spend as much time on the words as on the code. We ask what a visitor needs to know to decide, in the order they need it, and we leave out what they do not. Pages are read on phones, in a hurry, so every section earns its place or goes.
