Website hosting
A good home for a site that was built properly
Fast, private, accessible, and honest about what it does. Every site here clears the same bar. Clear it and you have somewhere to live from £120 a year.
The bar
Four things every site here has in common
We are not fussy about how a site is built. Static output from any generator, a headless front end, serverless functions, WordPress, something with a database behind it: all fine. We are fussy about what it does to the person visiting it.
-
Fast
Quick on a phone, not just on your laptop
Above 95 is the number we hold ourselves to and the number we ask of anything we take on. Not one homepage cherry-picked for a screenshot. Every page.
-
Private
Counts views, never people
No third-party trackers, no ad pixels, no fonts phoning home. Any usage counting is anonymous, cookie-free and aggregate-only, the kind the law permits without a banner; anything that would identify a visitor needs explicit consent first, and the default answer is no.
-
Accessible
Works without a mouse, and without sight
Real headings, real labels, honest contrast, focus you can see. Built to WCAG 2.2 AA, so the site holds up for someone using a keyboard, a screen reader or a magnifier.
-
Sound
Nothing left lying around
No keys in the source, no admin panel on a guessable path, no placeholder copy from the template sitting indexed under your name.
Two ways in
How a site ends up here
We built it
Anything we build already meets the bar, because the bar is simply how we build. There is nothing to review and nothing to fix. It goes live on our infrastructure the day it is ready.
You already have one
Send us the URL and we run the full check on it. If it is genuinely well built we will take it on as it stands. If it needs work, that can go through the retainer, be quoted as project work, or you can do the work yourself and resubmit when it is ready.
The check
Eight things, scored the same way every time
-
Pillar 1: Security and data exposure
What is reachable, how easily, and what it would give up.
-
Pillar 2: Credibility and reputation
What a visitor, or a search engine, would conclude about you.
-
Pillar 3: Performance
Page weight, load timing and Core Web Vitals, measured in a real browser.
-
Pillar 4: AI-slop signals
Placeholder copy, template leftovers, text nobody meant to publish.
-
Pillar 5: Site integrity
Broken routes and dead links, the things that quietly stopped working.
-
Pillar 6: SEO and metadata
Whether each page describes itself properly to anything reading it.
-
Pillar 7: Accessibility
Whether the markup holds up for people not using a mouse or a screen.
-
Pillar 8: Forms and functionality
Whether the thing your business relies on actually submits.
The report
We measure it rather than have an opinion about it
A real browser loads the real site. It times the paint, weighs the page, crawls the routes, reads the headers, watches what calls home and when. Out of that comes a list of findings and two scores.
Site score
How good the website is as delivered, across the eight pillars. Security is judged on what is exposed, how easily, leading to what, over how sensitive the data is, rather than a flat pass or fail.
Professional standard
How well it was built. Whether the problems found are things a competent developer, or a check running before release, should have caught long before it went live.
The gates
Two of them, and both are absolute. A site score of 95 or above, and nothing outstanding under security and data exposure. One unresolved security finding fails the site whatever the score says.
We report what we measured, flag what we could not verify, and do not guess at the rest. You get it at onboarding, once a year after that, and after any update we deploy.
Sample output
example-co.ukThree findings outstanding. This one has to be zero, whatever the score says.
Context rather than a gate: how much of this should have been caught before release.
Either gate on its own is enough to fail. The full report names all 39 findings and what clearing each one takes.
A side effect
A well built site uses less energy
Every megabyte a page sends has to be stored and served, pushed across the network, then unpacked and rendered by whatever opens it: a phone, a laptop, a desk machine, a screen reader, a television. Every one of those steps burns electricity, and none of it is free.
The median web page is now around 2.4 MB. Sites built to our bar usually land under 500 KB. Sites we build usually land under 200 KB. Page weight per view is measured in the report, so you will know your own figure rather than ours.
-
0.36 g
Median page, per view
CO2e for one visit to an average 2.4 MB page.
-
0.03 g
A 200 KB page, per view
Same content, built to weigh what it should.
-
92%
Less energy per visit
Around 33 kg of CO2e a year on 100,000 visits.
Digital technology accounts for something like 3.7% of global emissions, roughly on a par with aviation, and page weight is the part of that a web team actually controls. Nobody moves that number alone. It moves because a lot of people decide to ship less.
Figures from the Sustainable Web Design model v4: 0.30 kWh per gigabyte transferred at a global grid average of 494 g CO2e per kWh, and HTTP Archive median page weight. At 100,000 visits a year a median page works out at roughly 36 kg CO2e against roughly 3 kg for a 200 KB one. Estimates, not meter readings.
At scale
Now imagine everybody did it
Six billion people are online, browsing somewhere between six and ten pages a day. Call it eight. That is roughly 17 trillion page views a year, and at today’s median page weight it costs the atmosphere about 6.3 million tonnes of CO2e.
Build those same pages at 200 KB and the bill drops to around half a million tonnes. Nobody is claiming every page on the web can be 200 KB. The point is which way the effort should be pointing.
What 5.8 million tonnes of CO2e looks like
-
5.8 million flights
Return, London to New York, at about a tonne each.
-
1.3 million cars
Taken off the road for a whole year.
-
276 million trees
Absorbing carbon for a whole year.
-
2.5 billion litres
Of petrol, never put in a tank and burned.
Plans
From £120 a year
-
Static
From £120 /year
Billed annually.
- One website, unlimited pages
- 100GB bandwidth a month
- 500MB of site files
- Two custom domains, TLS included
- Three staging environments for previews
- Serverless endpoints for forms
- Site report at onboarding, then yearly
- UK business-hours email support
-
WordPress
From £144 /year
Billed annually.
- One WordPress site
- 10GB app storage, 16GB database
- Managed MySQL flexible server
- Unlimited bandwidth
- Custom domains, TLS included
- Staging slot for testing changes
- Core and plugin updates applied
- Site report at onboarding, then yearly
- UK business-hours email support
-
Production tier
Add £90 /year
Billed annually. For a site that cannot be down.
- 99.95% uptime SLA
- Bandwidth beyond the 100GB cap, rather than a hard stop
- 2GB of site files
- Five custom domains
- Ten staging environments
- Private endpoints and IP restrictions
Something bigger than a plan
More sites, more traffic, more storage, or a setup that does not fit on a card. Tell us what you have and we will price it.
Prices exclude any applicable sales tax.
Questions
The things people ask first
Would you really turn a site away?
Yes. Standards, tested code and a check before release are low cost and low effort, and the reason so much of the web is slow and unusable is that people skip them. We would rather lose a hosting account than add to that. What usually happens is less dramatic: we tell you what is in the way, and you either have us fix it or fix it yourself and come back.
What can you actually run?
Most things. Static output from any generator, headless front ends, serverless functions, and full server-side applications with a database behind them. The stack is not what decides it. How the site behaves is.
Why be selective at all?
Because the bar is only worth something if everything here clears it. Holding to industry standards and ordinary coding discipline is what separates a site that works from one that merely looks finished, and it costs almost nothing to do properly the first time.
How do changes get made once it is live?
Changes go through the retainer or a fixed project quote, so development never turns up disguised as a hosting invoice.
Do you handle our domain?
Domains stay with your registrar by default, where you can see them and nobody else can lose them. We tell you which records to point at us and keep the certificate working on our side. If you would rather not deal with it at all, we can manage the domain for you given access, through the retainer or quoted as project work.
Where does it run?
Azure, in whichever region matches your requirements.
What does the report cost on its own?
It is a paid report if you are not hosting with us. Accept a quote from us to fix what it found and we refund what you paid for it. Add a year of hosting to that quote and the improvement work comes down 10%.
What happens if the site goes down?
We watch the infrastructure and fix what is ours during UK business hours. Best efforts, said plainly. The £90 production tier moves the site onto a plan carrying a 99.95% uptime SLA, with higher bandwidth and storage limits.