Measured speed
LCP, INP and server response time, measured in milliseconds for every page, on mobile and desktop, before launch. Not a laboratory score from a single test.
CodeZeep
Websites, online stores and software with measured performance
We build them from scratch and maintain them long term. Every page is tested down to the millisecond, every intervention is documented in a clear monthly report, and the premium tools we work with are included in the price. Everything we claim comes with a number you can verify yourself.
Where to start
Four directions, depending on where you are
Each direction has its own pages, covering what the work includes and how it is measured. If it is not clear which one you need, write to us and we will tell you after looking at what you have now.
WordPress Maintenance
A monthly subscription in which we measure, down to the millisecond, every page, every request and every setting that affects speed, security or search position. You get a clear report: the numbers, the changes and the reasoning behind them.
Security, performance, search, upkeepFor Start-ups
Your first presence online, built on an architecture that supports growth. Website, store, app and the design system behind them, made so that in two years you extend rather than start again.
Website, online store, app, designFor Marketing
Traffic that turns into customers rather than into charts. Branding, landing pages, content strategy for search and email, each with a number before and a number after every change.
Branding, landing pages, SEO, emailFor Companies
Software shaped around your actual process. Custom applications, integrations between the systems you already run, and automation that takes repetitive work out of people's days.
Software, integrations, automation, maintenance
How we work
Four commitments we make on every project
We measure before and after. Anything we claim about speed, conversion or rankings comes with the figure from before and the figure from after, taken under identical conditions: load times expressed in milliseconds, per page, on mobile and on desktop. You can verify each value yourself with public tools. You will not get a screenshot of a green dial and the conclusion that everything is fine.
We work with premium, licensed technology. Wherever the difference in results is measurable, we use paid commercial tools rather than the free tiers: for the caching layer, image processing, the security suite and the testing infrastructure. The licences are included in the price, and every tool is chosen on comparative measurements and replaced when something demonstrably better appears.
We tell you when you do not need it. Often the right conclusion is that you do not need an app, that an existing platform solves your problem more cheaply than custom software, or that there is no point running campaigns over a site that loses half its visitors while loading. We say so before the contract, even when it means a smaller project for us.
You can leave with everything, at any point. Code, hosting, domain, accounts, documentation. The code is written so somebody else can pick it up, and the test we apply to ourselves is how long an outside developer would need to understand the project. A supplier whose continuity rests on nobody else understanding their code is not a partner, it is a risk.
More about how we work and what we refuse to do, on the About us page.
Included in every project
What we put in without anyone asking
Security by construction
Correct permissions, protected forms, components up to date, backup configured and tested before day one.
SEO foundation
Structure, clean addresses, structured data, indexing. Added later, these cost several times more.
Accessibility
Contrast verified numerically, keyboard navigation, labelled forms. Roughly one visitor in five needs them.
Mobile tested on real phones
Including old and slow ones, because those are exactly what your customers have. A simulator does not show the keyboard covering the field.
Documentation and handover
With a session in which we actually show you, not a file emailed on invoice day.
Artificial intelligence
What we do with AI and, more importantly, what we do not
It is the biggest change in this trade since the arrival of the mobile phone. We use it seriously, but not in the places where it would hurt you.
Your site has to be readable by AI assistants
A growing share of searches no longer ends in a list of results but in a generated answer. Those systems read document structure, structured data and the clarity of statements, then cite the sources they can verify.
In practice that means a correct heading hierarchy, valid markup describing what you offer and to whom, explicit answers to real questions, and the important information in text rather than locked inside images or scripts. We build this into every page we deliver, and under Google Optimization we verify it monthly.
We use it as a tool, not as a replacement
It helps us analyse large volumes of data, generate options we then evaluate, and spot patterns in an error log or a search report. It makes us faster at the mechanical part.
What we do not do is ship what comes straight out of it. Every technical decision and every published line passes through somebody who owns the result. The difference shows: generated text sounds plausible and contains nothing that could not have been generated for your competitor too.
Generated content and Google
Generated text is not forbidden, but published at volume with no real contribution it is exactly what Google has been trying to filter out for years. The risk is not theoretical: sites built that way have lost almost all their traffic overnight.
We use it as a skeleton and an accelerator, never as the finished product. What you publish has to contain something that could not have been generated: your experience, your numbers, your cases.
Your data does not go anywhere
We do not put your database, your proprietary code or your customers' data into an external service to get a faster answer. It is a line we do not cross, however much easier it would make our work.
If you want us to build something with AI inside your product, we discuss separately where the data ends up, what is retained and what you tell your users about it. That is a compliance conversation, not only a technical one.
Frequently asked questions
Do you work with small companies?
Yes. Most of what we do is for companies between five and fifty people. What we ask for is not a particular size but one person who can make decisions, because otherwise the project stalls waiting for approvals no matter how well it is going technically.
How does a collaboration start?
With a half hour conversation in which we find out what you want to solve. At the end we tell you whether it makes sense to work together, roughly what it means in budget and time, and quite often the cheaper option you had not considered. It is not a sales presentation.
Will I be locked in?
No. You get access to everything from the start: code, hosting, domain, accounts. The code is written so somebody else can take it over, and documentation exists precisely so that handover takes days rather than months. We stay because it is worth it, not because you have no way out.
Do you really turn down projects?
Yes, and it usually sounds like this: somebody asks for a mobile app, and it emerges from the conversation that their customers would open it twice a year. In that case the app costs ten times more than a good mobile site, and on top of that every customer has to be persuaded to install it. We say so and build the smaller thing. We would rather have a small project that works than a large one the client regrets in year two and we have in our portfolio.
Tell us what you need to solve
A short conversation usually settles whether it makes sense to work together and roughly what it means in budget and time. No sales presentation.