01
Websites and web platforms
From editorial sites to applications with routing, logic and accounts behind them. Astro where content leads, Next.js where the interface does, Go and Postgres where the data does.
Services 03 Digital Experiences
A website that takes fifteen seconds to show its first sentence has already lost the visitor it was built for, whatever it looks like. We design and build sites and platforms to a standard we publish and re-measure: Lighthouse 95 or better on every public route, accessibility 100, layout that does not shift, and testing on the phones your audience actually holds.
Our own site is the shortest version of the argument. The old one was a purchased theme: 11,965 KiB on the homepage, main content arriving at 4.7 seconds, accessibility 85. This one weighs 242 KiB, reaches main content in 1.8 seconds, and scores 100 for accessibility. Forty-nine times lighter, same business, same story.
None of that came from a plugin. It comes from a stack that ships almost no JavaScript, fonts self-hosted and preloaded only where they appear above the fold, motion that never hides the largest text while it loads, and every route measured before anyone calls it finished. The method is not exotic. It is just applied every time.
Digital experiences that do not just look good. They work.
The diagnosis
Almost always the platform underneath, almost never the content on top.
It looks fine on your laptop and is unusable on a phone in the field.
Several seconds pass before a visitor can read a single sentence.
Editing a page means asking whoever built it.
The homepage is one enormous image and seven font families.
You pay monthly for plugins that exist to fix the theme.
You cannot say what any of it produced last quarter.
What we build
01
From editorial sites to applications with routing, logic and accounts behind them. Astro where content leads, Next.js where the interface does, Go and Postgres where the data does.
02
Structure, flows and a component system built from your brand tokens, so page two costs less than page one and everything still matches at page thirty.
03
Payload budgets per route, image pipelines, self-hosted preloaded fonts, and motion that never delays the largest text. Speed treated as a build constraint rather than a plugin.
04
Keyboard paths, contrast measured rather than eyeballed, alt text everywhere, and reduced-motion states that still carry the full meaning. We target 100 and record the score with the date.
05
A measured verdict on the site you have: what it weighs, how long it makes people wait, what it fails, and what is worth rebuilding rather than patching.
06
Photography and video integrated properly, a CMS your team can actually run, training, and a support window so the site keeps improving after launch.
Proof
Delivered
InPlace Creates
The old inplacecreates.com scored 65 for performance and 85 for accessibility, weighed 11,965 KiB on the homepage and took 4.7 seconds to reach main content. This site scores 99 to 100 on every public route, 100 for accessibility, weighs 242 KiB, and reaches main content in 1.8 seconds with no layout shift. Forty-nine times lighter, on the same story. Every figure is dated in our audit record and re-run before it is quoted.
Prototype and proposal
A children’s foundation
Measured against their live site: performance score 50 to 97, largest contentful paint 13.9 seconds to 2.4 seconds, page weight 34.5MB to under 0.4MB.
Delivered
HKM Construction
A two-column project grid opening into named case studies, each with location and years, with measured scroll motion and a palette restrained enough to let the architecture lead.
Delivered
EPC Aviation
Built to route three audiences fast: institutions toward a booked consultation, pilots toward training near them, and partners toward the equipment. Bilingual in English and German for the European partner network.
Delivered
Nkishon Mission Foundation
An editorial site for a missions foundation working among the Samburu, with sponsorship and campaign pathways woven through the journey rather than parked behind one donate button.
Delivered
Kikao Pride and KCiti Homes
A website for Kikao Pride, an engineering company, and one for KCiti Homes. Both delivered.
How we work
We measure the current site before discussing the new one: weight, wait, accessibility failures, and what visitors actually do on it. The brief writes itself once the numbers are on the table.
Sitemap, page purposes, and the one action each page exists to produce. Buttons navigate to real pages; nothing scrolls you down the page and calls it a journey.
Design tokens taken from your brand, components built once and reused, reviewed on a real device early. Feedback lands on the actual thing rather than a picture of it.
A payload budget per route, images through a pipeline, fonts self-hosted and preloaded, motion transform-only so the largest text is never hidden while it loads.
Desktop settle state, hard-refresh behaviour, and a 390 by 844 portrait pass, because desktop hero compositions do not survive a phone crop. Console clean, no horizontal overflow.
Lighthouse on every public route, recorded with the date. Then CMS training, documentation and a support window, and a re-measure any time the numbers get quoted.
Working together
Fixed fee
A measured verdict on the site you have: performance, accessibility, structure and conversion, delivered in writing with a prioritised list of what to fix and what to rebuild. Credited against a build if you proceed.
Fixed fee, phased payments
The full project: structure, design, build, content integration, audit and handover, scoped against agreed pages rather than an open-ended hourly count.
Monthly retainer
Content updates, new pages and sections as the business changes, and the performance and accessibility numbers held where we left them.
No cookie-cutter packages. The audit is the honest way in: it costs a fraction of a rebuild, and sometimes it tells you not to rebuild.
We only build what removes real work.
Questions
Usually something else. Most sites we are asked to fix are a theme plus a stack of plugins, and the weight of that combination is the problem we are being hired to solve. Where a client genuinely needs WordPress we will say so. Where they do not, we build something lighter that their team can still edit.
Yes. We set up editing for the parts that genuinely change, and train your team on it. What we do not hand over is a page builder that lets anyone quietly undo the performance you paid for.
The technical half is built in: real metadata, structured data where it earns its place, a sitemap, semantic markup, and speed, which is itself a ranking factor. The half that depends on publishing consistently is yours, and we will say that plainly rather than sell it as a package.
We deploy to modern hosting in your name where you want that, so the site and the domain stay yours. We can manage it under a retainer, but you are never locked to us to keep the site up.
They stay high unless something undoes them, which is why we hand over a site with a payload budget rather than an unbounded page builder. We re-measure on request, and we record the date beside every number we quote.
Send us the URL. We will run the same audit we run on our own site and tell you what it weighs, how long it makes people wait, and what it fails, before anyone talks about a rebuild.