Websites built by hand, not assembled from a theme
A static website is one where every page already exists as finished HTML
before anyone asks for it. There is no database to query, no plugins
waking up, no theme deciding what your page should look like a few
milliseconds before it appears. The server hands over a file, and the
browser draws it.
That sounds like a technical detail. It is really a business one: pages
that appear instantly, nothing sitting there waiting to be exploited,
and no maintenance treadmill. And because we write the markup rather
than inherit it, the structure search engines read is the structure we
chose — which is the whole reason we build sites at all.
- Written by hand, so
nothing ships that does not need to
- Core Web Vitals
handled during the build, not patched afterwards
- No plugins to update
and no database to break into
- Structured for search
engines and AI assistants from the first page
what's included
What goes into the build
Hand-written front end
HTML, CSS and JavaScript written for your site specifically.
No page builder, no theme options panel, and none of the
code a theme ships for the other ten thousand businesses
using it.
Speed as a constraint
Images sized and converted properly, fonts self-hosted,
stylesheets stripped to what the page actually uses. Core
Web Vitals get designed in rather than chased later.
Search structure from day one
Heading order, internal linking, canonicals, sitemap and
structured data built in as the pages are written — not
bolted on by a plugin once the site is live.
Responsive on real devices
Laid out to work from a phone to a wide desktop, and checked
at the awkward widths in between where most templates quietly
fall apart.
Edge hosting
Served from a global network so the site is close to whoever
is asking for it. No shared host to outgrow and no monthly
surprise when traffic climbs.
Forms, maps and reviews
Contact forms, Google Maps, review widgets, booking and chat
all work on a static site. They run as services rather than
as plugins sitting inside your website.
Migration from your current site
Content moved across, URLs mapped and redirected, and the
rankings you already have carried over rather than dropped
on launch day.
Changes handled for you
Send us the change and it goes live. If you would rather edit
pages yourself day to day, that is a fair reason to want
WordPress instead, and we will say so.
how it works
From first call to live site
01
Plan & Structure
We work out what pages the site needs, what each one has to
do, and which search each one should own — before anyone
draws a layout.
02
Design & Build
Layouts first, then the pages get written by hand, reviewed
on real devices, and tuned until the performance numbers are
where they should be.
03
Launch & Measure
Redirects mapped, analytics and Search Console connected,
then we watch indexing and rankings through the switch
rather than hoping.
A static site is a good fit if
- Your content changes occasionally, not several times a
week
- You are tired of updates, plugin conflicts and security
warnings
- Speed matters because your visitors arrive on phones
- You want the site and the SEO handled by the same
people
You probably want WordPress if
- Someone on your team publishes content regularly and
wants to do it themselves
- You need a full storefront with live inventory
- You depend on a specific plugin that has no equivalent
elsewhere
- Staff need logins and different levels of access
WordPress websites
questions
Questions we get asked
You send us the change and we publish it, usually the same day. That suits most businesses, whose pages change a few times a year. If you expect to be editing pages yourself every week, say so early — that is a genuine reason to build on WordPress instead, and we would rather sort it out at the start than hand you something that fights you.
Yes. Forms, booking calendars, live chat, maps and review widgets all work. The difference is that they run as outside services rather than as plugins living inside your website, which is exactly why there is nothing on your site for someone to break into.
Not automatically — Google ranks pages, not platforms, and a well-built WordPress site can rank perfectly well. What static gives you is a higher ceiling and fewer things working against you: no plugin bloat slowing pages down, no theme generating markup nobody chose, and speed that is difficult to lose later.
Usually, yes. Content comes across, every existing URL gets mapped to its new home, and the redirects go in before launch so the rankings you have already earned follow you. The risky part of any migration is the URLs, and that is the part we plan first.
Static builds start at $6,995. Where a project lands above that depends on how many pages it needs and how much of the content already exists, and you get a fixed number before any work begins. That is more than twice what a WordPress build starts at, for a straightforward reason: WordPress hands us a working foundation, and a static site has no foundation until we make one. Every page, layout and interaction is written rather than configured. What you are buying with the difference is a site with nothing to maintain afterwards — no licences, no update cycle, and nothing that can be broken into.
No. Plenty of people come to us for the site alone. We build every site so it can be ranked, whoever ends up doing that work — but the two together is where it pays off, because nothing falls between the site and the search work when the same people handle both.
