Cloudflare hosting for a small business website

Case study. Fast for every visitor, published from Git, nothing to patch or babysit. Client details withheld for confidentiality.

At a glance

  • Client: a small business with a static website and no in-house IT
  • What they needed: hosting that is fast and reliable, a simple way to publish changes, and a safe place to try changes first
  • Result: sub-second load times, zero downtime since launch
  • My role: contractor; set-up and handover

The brief

The site had outgrown its hosting. It was slow for visitors outside the region, every change meant uploading files by hand, and there was no way to check a change before it went live. The business wanted something quick, cheap to run, and safe to update, without taking on a server to look after.

See it in action

A live illustration with sample data. The names, figures and addresses are invented, and these are not the client's screens.

Git pushGitHub Build & checksCI/CD Stagingpreview branch Productioncustom domain Cloudflare edge300+ cities Visitor D1 R2 every pushbranchesmaincached< 1 s From a change to a visitorbuilding…checks passed ✓publishing…live in 300+ cities ✓ 0.6 s ✓ Uptime · last 30 days100% Every push runs this pipeline. Nothing reaches the main site until the checks pass; everything that does is served from the city nearest each visitor. Deployments #142 Contact page redesignLive #141 Autumn pricing pagetoday #140 New gallery imagesMon #139 Fix footer linklast week one click rolls any of these back From a change to a visitor building…checks passed ✓publishing…live in 300+ cities ✓ Git pushGitHub Build & checksCI/CD Stagingpreview branch Productioncustom domain Cloudflare edge300+ cities Visitor 0.6 s ✓ every pushmainbranchescached< 1 s Uptime · last 30 days100% Deployments #142 Contact page redesignLive#141 Autumn pricing pagetoday#140 New gallery imagesMon#139 Fix footer linklast weekone click rolls any of these back
Live: a push travels through build and checks to production, the edge network ripples it out, the visitor gets it in 0.6 s, and the deployment appears in the list. Sample data.

What I built

Cloudflare Pages with a custom domain

The site is served from Cloudflare's network, so it loads in under a second wherever the visitor is, with HTTPS handled automatically.

Publish from Git

A push to the repository builds and publishes the site. No FTP, no manual uploads, and a full history of every change with one-click rollback.

Staging and production

Branches get their own preview address, so a change can be checked on a real URL before it reaches the main site.

Data and files at the edge

Cloudflare D1 for the small amount of structured data the site needs and R2 for images and documents, both alongside the site rather than on a separate server.

Nothing to maintain

No operating system, web server or certificates to patch. The business edits content; the platform does the rest.

Clean handover

The business owns the Cloudflare account, the domain and the repository, with written instructions for publishing changes.

Technology

Cloudflare PagesCloudflare D1Cloudflare R2Git CI/CD

Outcome

Sub-second load times for every visitor and zero downtime since launch. Publishing a change went from a manual upload to a push, and the business has not had to think about hosting since.

Need something similar?

If your site is slow, fragile or a chore to update, this is usually a short project. Get in touch.