Web design · Portfolio
I'm a web designer. I build fast, modern websites for small businesses — the kind that load quickly, read clearly, and turn up when someone searches. Here's some of that work.
how a site comes together
What I do
Not just "a website." Design, words, and the technical groundwork that makes a site actually work.
A clean, modern site shaped around the business it belongs to — not a template its customers have seen ten times before.
I write the pages too, in plain language that tells customers exactly why they should pick this business.
Proper SEO from day one: structured data, fast loading, and the local keywords real customers actually search for.
Most visitors arrive on mobile. Every site I build is designed to look sharp and load fast on any screen.
Domain, hosting, SSL certificate, and backups — set up properly and explained in plain language.
The design, the code, the domain, the logins — all of it belongs to the business it was built for. No lock-in.
How I work
The same way every time, so nothing gets lost along the way.
Step 1
A conversation about the business, its customers, and what the site actually needs to do. Everything after this depends on getting that right.
FirstStep 2
I design the homepage first and show it early. Reactions, then refinements — until it feels like the business it belongs to.
Early onStep 3
The full site gets built, the copy written, the SEO wired up. Everything reviewable on a private preview link before it's public.
The bulkStep 4
Domain connected, site submitted to Google, every login handed across — with a plain-language guide to keeping it updated.
LastWhat I can build
Every business is different, but most projects land somewhere in here.
A simple site
One page, done properly — for a business that mainly needs to be found and understood.
A full site
Several pages, more than one language, and the things that turn visitors into enquiries.
A shop or booking site
For a business that needs to sell products or take bookings directly online.
Something different in mind? Tell me what the business needs and I'll say honestly whether I'm the right person to build it.
How I think about it
I'd rather say "you'll be able to edit your menu yourself" than "we'll leverage a headless CMS architecture." Jargon usually hides something.
Speed isn't a feature you add at the end. A site that takes four seconds to load on a phone has already lost the visitor it was built for.
The domain belongs in the owner's name and they get every login. Plenty of agencies hold onto these to lock people in. I think that's wrong.
It looks like us. That's the part I didn't expect. Most restaurant websites feel like a form somebody filled in, and this one feels like walking through the door. The wine list finally has somewhere to live.
FAQ
Hand-written HTML, CSS, and JavaScript for most things — it's why they load fast and there's nothing to break. Where a site needs a shop, a booking calendar, or content the owner edits themselves, I'll bring in whatever tool genuinely fits rather than forcing everything through one platform.
Yes. Built properly, that means separate language versions Google can actually index — not a translate widget bolted onto one page. La Réserve's site is bilingual for exactly this reason.
Not much time, but the right things: a conversation about what the site is for, photos, and honest reactions to the design. I write the text, but the good lines almost always come out of that first conversation.
Every login gets handed over, along with a short plain-language guide to updating things. The domain sits in the owner's name. Nothing about the setup depends on me still being around.
Sometimes. Some sites are worth improving and some are quicker to rebuild — it depends what's underneath. I'd rather look and say honestly which one it is.
Get in touch
Tell me about the business and what the site needs to do. I'll give you an honest opinion either way — including if I think you don't need me.
or write to sales@letknowco.com