Static Website Development

A website that is just files: hand-built HTML and CSS, no CMS, no plugins, no database. The fastest and most secure kind of site there is — for businesses whose site is a showcase and a contact point, not a shop.

  • My own site is built this way
  • PageSpeed 98–100 on mobile, up from 78 on Divi 5
  • Nothing to hack, nothing to update
Hand-built HTML files served straight to a phone, with a 100 performance badge

No Moving Parts

Every page on a static site is a finished HTML file. When someone visits, the server hands it over — no PHP running, no database queries, no page builder assembling layouts on the fly. The design lives in one stylesheet. The only code that runs in the browser is what the page needs: a menu, a contact form, analytics.

That simplicity is the whole point. Nothing to hack because there is no login. Nothing to update because there are no plugins. Nothing to cache because there is nothing slow.

  • 0plugins to update
  • 0logins to hack
  • 1stylesheet for the whole site
  • 98–100mobile PageSpeed on this site

Who a Static Site Is For

Service Businesses With a Showcase Site

Contractors, consultants, practices, studios — anyone whose site needs to look sharp, explain what you do, show the work, and get people to call or fill out a form.

Agencies That Need Fast, Clean Landing Pages

Campaign pages, microsites, and client brochure sites that have to score well and never break. White-label available.

Anyone Tired of WordPress Upkeep

If you are paying for maintenance on a site that gets edited twice a year, a static rebuild can end that bill.

What You Get

  • Custom design built as a single, consistent design system — not a template
  • Every page hand-coded, semantic, and accessible (WCAG AA contrast checked in light and dark mode)
  • Google PageSpeed scores in the high 90s to 100, Core Web Vitals in the green
  • Light and dark mode if you want it
  • Contact form with spam protection and email delivery (one small PHP handler)
  • Google Analytics 4 wired for page views and lead events, loaded so it never slows the page
  • SEO fundamentals: clean URLs, titles and descriptions, XML sitemap, schema markup, 301 redirects from your old URLs
  • Image optimization — SVG for graphics, WebP for photos, every image sized to prevent layout shift
  • Hosting on my private VPS, or files you can put anywhere
  • A one-command build so changes deploy in seconds
  • Verified at phone, tablet, and desktop widths before you ever see it
  • You own every file — nothing proprietary, nothing rented

How I Build It

  1. Scope and Copy

    We settle the page list, the copy, and the brand. I tell you up front if anything you need is dynamic — and if it is, I will recommend WordPress instead.

  2. Design System First

    Colors, type, spacing, and components are defined once, with contrast checked before a single page is laid out.

  3. Build on Staging

    You review every page at real device widths, in both color modes, before anything goes live.

  4. Launch With Redirects

    Old URLs are mapped and redirected, the sitemap is submitted, and analytics are confirmed firing. Then I hand you the keys — or keep them under a webcare plan.

Read How I Rebuilt My Own Site

When I Will Steer You to WordPress Instead

A static site is the right tool for a specific job. It is the wrong tool when you need:

  • Frequent edits by your own team without a developer or AI assistant in the loop. Static means every change is code.
  • Dynamic features: online store, memberships, bookings, logins, a large searchable catalog, content pulled from feeds.
  • Many authors and a publishing workflow. A static blog is fine for occasional posts; it is not a newsroom.

I build and maintain WordPress sites every week. If that is what your business needs, that is what I will recommend.

WordPress solutions for sites that need dynamic features

Changes Are Fast — and Cheap

Because the site is files, edits are quick for me: a new page, a price change, a new photo, a seasonal banner. Most clients fold updates into a webcare plan or send them as they come up and are billed in hourly blocks. If you work with an AI assistant yourself, the files are the most legible format there is — plain HTML and CSS, nothing proprietary.

  • Small edits, small bills. A price change or a new photo is minutes of work, not a plugin hunt.
  • Nothing to break on the way. No update can conflict with a change, because there are no updates.
  • Every change is reviewed and tested at phone, tablet, and desktop widths before it goes live.
A website being maintained and updated with care

Frequently Asked Questions

Will a static site rank well?

Yes. Google rewards fast, stable, crawlable pages, and a static site is all three by nature. You get the same SEO fundamentals as any site I build: titles, descriptions, schema, a sitemap, and redirects from your old URLs.

Can I have a blog?

Yes. Posts are files generated by a build script, with categories and a filterable index. It works well for a company that posts a few times a month.

Can I edit it myself?

If you are comfortable editing HTML, or you work with an AI assistant, yes — the files are plain and well organized. Most clients prefer to send me changes.

What about forms?

A small, self-hosted form handler with spam protection and a delivery log. No third-party form service required, though I can wire one if you prefer.

Where is it hosted?

On my private LiteSpeed VPS by default, with SSL, backups, and Cloudflare. Because it is just files, it can also live on any host or CDN you choose.

How much does it cost?

Like all of my projects, a static build is billed on time. Static sites take less time to build than WordPress sites — typically 30–50% less, depending on what you need, and for some projects the savings are larger. Tell me about your project and I will give you a considered estimate.

See how I bill
Can you convert my existing WordPress site?

Yes, if the site fits the profile above. I port the copy, keep every URL or redirect it, and rebuild the design as a clean system. That is exactly what I did to my own site.

Want a Site With Nothing to Break?

Tell me what your site needs to do. If a static build fits, I will show you mine and quote the work. If it does not, I will say so. Here is what one conversation gets you:

  • A clear answer on fit. I ask about edits, features, and who publishes, then tell you whether static or WordPress is the right tool.
  • A considered estimate before any work starts. Static builds take less time than a comparable WordPress build, and the number reflects that.
  • Proof you can inspect. This site is a static build. I will walk you through the files and the PageSpeed scores.
  • No hard sell. If WordPress is the better fit, you leave with that recommendation and a clear next step.