The tools we would actually use if you were building it yourself
For a small-business site built by its owner: VS Code to edit, Google Fonts for type, Coolors to pick a palette, Squoosh to shrink images, and an ordinary shared hosting plan to put it online. Use AI for first drafts of copy and for layout ideas, not for the finished thing. This is the short list we would hand a friend, with the reason for each and the traps.
If you have decided to build it yourself, the hardest part is not any single tool. It is that there are forty options for every step and most of the comparison articles are affiliate pages.
This is the short list. Everything here is free or has a real free tier, and everything here is something we would genuinely use.
Writing and editing the files
VS Code is the editor. It is free, it is what most of the industry uses, and the reason that matters to you is search results: when something goes wrong, the answer will be written for VS Code.
Two extensions worth having on day one and nothing else until you need it: Live Server, which shows you the page in a browser and reloads it as you save, and Prettier, which reformats your file so the indentation stops being something you think about.
If installing an editor feels like too much, CodePen lets you write HTML and CSS in a browser tab and see it immediately. It is a good way to learn what a tag does before committing to a project.
Type
Google Fonts is the obvious answer and it is the right one. Free, licensed for commercial use, and hosted for you.
The advice that will improve your site most: use one family, not three. Pick one with several weights and use the weights for hierarchy. Almost every homemade site is spoiled by three typefaces arguing with each other, and almost none is spoiled by one used well.
If you want a starting point rather than a decision: Inter, Source Sans, Work Sans and Public Sans are all free, extremely legible at small sizes, and hard to make look bad.
One technical note that matters more than it sounds: when you embed a Google Font, request only the weights you actually use. The default embed code often pulls several, and each one is a file your visitor downloads before they can read anything.
Colour
Coolors generates palettes and lets you lock the colours you like while it suggests the rest. It is the fastest way from “I have a logo” to “I have a scheme”.
The rule that keeps small-business sites looking professional: one accent colour, and a lot of restraint. Your brand colour goes on things you want clicked. Everything else is a neutral. The moment the accent appears in five places it stops meaning anything.
Then check it. WebAIM Contrast Checker tells you whether your text is readable against its background. The number to clear is 4.5:1 for normal text. This is not a nicety — light grey text on white is the most common accessibility failure on the small-business internet, and it also fails for anyone reading outdoors on a phone.
Pale grey on white is the specific thing to check. It looks refined on your monitor and is genuinely hard to read on a laptop in a cafe.
Images
This is where most homemade sites lose their speed, and it is the easiest thing on this list to fix.
Squoosh shrinks an image in your browser, with a before-and-after slider so you can see the quality you are trading. A photo straight from a phone is commonly three to six megabytes. The same photo, resized to the width it actually appears at and saved as WebP, is often under two hundred kilobytes — and looks identical.
Two rules that do most of the work:
- Never upload a photo larger than it displays. If it appears 800 pixels wide, do not upload a 4000-pixel file.
- Save as WebP. Every browser in use supports it, and it is meaningfully smaller than JPEG at the same quality.
For photographs you do not have, Unsplash and Pexels are free and licensed for commercial use. Use them sparingly. Stock photography of people in an office says nothing about your business, and customers have learned to skip it. One real photograph of your actual premises, your actual van, or your actual work beats any of it.
Putting it online
Covered properly in our guide to what a website actually costs, but the short version: a shared hosting plan with cPanel, three to six dollars a month, from any of the mainstream providers. You upload your folder through the file manager, switch on the free security certificate, and you are live.
Buy the domain separately, in your own name, from any mainstream registrar. Do not let the hosting company own it.
Where AI genuinely helps
Used well it saves real hours. Used as a finisher it produces the exact texture that makes visitors leave.
Good uses:
- First drafts you then rewrite. Ask for a description of your services, then rewrite it in your own words with your specifics in it. The draft breaks the blank page, which is the expensive part.
- Layout ideas. “What sections does a plumber’s homepage usually have, in what order” is a genuinely useful question with a genuinely useful answer.
- Explaining errors. Paste the error, ask what it means. This is possibly the best use of AI for a beginner and it is faster than searching.
- Small snippets. “Give me the HTML for a table with three columns.” Verifiable, bounded, easy to check.
- Alt text drafts for your images, which you then correct.
Where it hurts:
- Publishing the output unedited. Readers have become fast at spotting it, and the cost is trust, which is the whole thing you are trying to build.
- Facts about your own business. It will produce plausible opening hours, plausible service areas, plausible years-in-business. Every one of those has to come from you.
- Anything legal. Privacy policies and terms are not the place for confident-sounding text nobody checked.
- Whole sites, unread. It will happily produce something that looks finished and contains a contact form that goes nowhere.
The test we would apply: would you be comfortable if a customer knew which parts were generated? If yes, fine. If not, rewrite that part.
What we would skip
- Page builders with hundreds of options. The flexibility is the problem; you will spend the time on the tool rather than the site.
- Plugins for things you have not needed yet. Every one is something to update and something that can break.
- Analytics on day one. Get the site up. There is nothing to analyse yet.
- A blog you will not write. An abandoned blog with three posts from two years ago says something about the business, and it is not flattering.
The honest limit of all this
Every tool here is genuinely good and genuinely free, and with them a determined owner can build a site that beats a lot of paid work. We mean that.
What the toolkit cannot give you is the judgement about what goes on the page — which service to lead with, what a stranger needs to read before they trust you enough to call, why one layout converts and another does not. That comes from having watched a lot of them, and it is the part that takes years rather than a weekend.
If you have time and interest, build it. You will understand your own business better for having written it all down, and you will never be held hostage by somebody who will not answer the phone.
If you have neither, that is not a failure of nerve — it is a reasonable read of what your hours are worth.