What makes a good website? A guide for small businesses
A good website brings in enquiries, not just compliments. Here is what actually makes a website good, in plain English, and how…
Helen Marsh · 27 Jul 2026
Design
Most of your customers visit on a phone, and Google indexes the mobile version first. Here is how to make a website mobile friendly, how to check yours, and the fixes that matter most.
Most people will see your website on a phone, not a computer. If it is fiddly to use on a small screen, they leave, and Google notices too. The good news is that making a website mobile friendly is mostly a set of clear, fixable things. This is a plain-English guide to what “mobile friendly” really means, how to check your own site, and the fixes that make the biggest difference.
You make a website mobile friendly by using a responsive design that adapts to any screen, text that is readable without zooming, buttons that are easy to tap, and pages that load fast. The aim is simple: someone on a phone should be able to read, tap, and get in touch without pinching, zooming, or waiting. Get those basics right and you are most of the way there.
Two things make this non-negotiable now. First, more than half of all web traffic comes from mobile phones (StatCounter), and for local businesses it is usually higher, because “near me” searches happen on the move. Second, Google now uses the mobile version of your site for ranking, a change it calls mobile-first indexing. In plain terms: if your site is poor on a phone, it is poor in Google’s eyes, even for people searching on a desktop.
For a Kent business competing for local customers, this is often the difference between getting the call and losing it to the firm whose site just works on a phone. It is also a core part of what makes a good website in the first place.
You do not need special tools to start. Do these three checks:
Once you know there is a problem, these are the changes that matter most, roughly in order of impact:
On a phone, speed and mobile friendliness are the same conversation. Google measures real-world loading and stability through Core Web Vitals, and slow, jumpy pages lose both visitors and ranking. The usual culprits are heavy, uncompressed images and cheap shared hosting. Fixing those two things resolves most slow mobile sites, and it is work you only have to do once.
If your site is broadly fine but has a few of the issues above, they are usually quick fixes. But if it was built before responsive design was standard, is not responsive at all, or is slow no matter what you try, you are patching the wrong thing. That is the point where a website redesign pays for itself, because a modern rebuild is mobile-first from the ground up rather than retrofitted. If you are not sure which camp you are in, the checks above will tell you quickly.
We build websites, so we have an interest in you concluding that yours needs work. Two things should make this more useful than that. First, the checks in this guide are ones you can run yourself, for free, in about ten minutes, and they will tell you honestly whether you have a problem. Second, the section on fixing versus rebuilding says plainly that most sites only need a few fixes, because that is true and we would rather tell you than sell you a rebuild you do not need. The order of the fixes reflects what has made the biggest difference on the sites we have worked on. Every claim about traffic or ranking is linked to its original source below.
Mobile friendly is not a nice-to-have any more. Most of your customers and Google itself judge your site on how it works on a phone first. Use a responsive design, make it readable and tappable, and keep it fast, and you cover the essentials. Every site we build is designed mobile-first for exactly this reason, so it works for the person standing in a queue on their phone, not just at a desk. If you would like us to check yours or build one that gets it right, see our web design service, have a look at what a website costs, or tell us about your business.
It means your website works well on a phone with no effort from the visitor: the layout fits the screen, text is readable without zooming, buttons are easy to tap, and pages load fast. A mobile-friendly site uses a responsive design that adapts to any screen size, so you never need a separate mobile version.
Start by opening it on your own phone: can you read it, tap things, and find your phone number without zooming? Then run it through Google PageSpeed Insights for a free mobile score and a list of specific issues. Loading it on mobile data also shows how it feels on a slower connection.
Yes. Google uses the mobile version of your site to rank it, a system called mobile-first indexing, and it factors in page speed and stability through Core Web Vitals. A poor mobile experience can hold you back even for people searching on a desktop, so it is worth getting right.
That usually means it is not responsive, or was built before mobile mattered. Small issues like text size and tap targets can be fixed quickly. But if it is not responsive at all or is slow no matter what, a rebuild that is mobile-first from the start is the better value fix.
No. Modern sites use one responsive design that reshapes itself to fit phones, tablets, and desktops. A separate mobile site is outdated, harder to maintain, and can cause problems with Google. One responsive site is simpler, cheaper to run, and what we build.
It depends on whether it needs a few fixes or a rebuild. Minor issues are usually quick; a site that is not responsive at all is better rebuilt. You can see what a website costs and what decides the price, then send us your site for an honest view.
New website
We design clean, modern sites that turn visitors into enquiries.
A good website brings in enquiries, not just compliments. Here is what actually makes a website good, in plain English, and how…
Helen Marsh · 27 Jul 2026
What website maintenance costs, what it includes, and whether you need it. Plus how a care plan keeps your site fast, safe,…
Jake Greenfield · 27 Jul 2026
How to choose a web designer without getting burned: the difference between a designer and a developer, the questions to ask, and…
Jake Greenfield · 27 Jul 2026