A website can look polished and still be quietly letting a business down. The useful question is not whether it looks good. It is whether the site is easy to find, easy to use, easy to understand and capable of turning the right visitors into enquiries.
Start with the job the website is meant to do
Before opening Lighthouse, running a crawler or staring at a PageSpeed score, be clear about the job. A local service business may need qualified enquiries. A professional firm may need to establish credibility before someone gets in touch. An ecommerce site may need to help people find, compare and buy.
If the website's purpose is unclear, it becomes very easy to optimise the wrong thing. A beautiful homepage that produces no enquiries is not a successful website.
1. Can people find it?
Check the basics first. Is the site indexed? Are important pages discoverable? Do page titles and descriptions accurately describe the content? Is there a sensible internal linking structure? Are there obvious technical barriers preventing search engines from reaching important pages?
For local businesses, check whether the website clearly states the services offered and the areas served. If the business is based in Glasgow but the website never actually says Glasgow, that is a surprisingly simple gap.
2. Can people understand it?
Give the homepage to someone who knows nothing about the business. Ask three questions: What does this company do? Who is it for? What should I do next?
If the answers are not obvious within a few seconds, the copy probably needs work. Good website content is not about cramming every possible keyword onto a page. It is about being specific enough that both people and search systems can understand what is being offered.
3. Does it work properly?
Broken links, missing images, console errors, awkward forms and layout problems on mobile all chip away at trust. They are also often symptoms of a site that is not being properly maintained.
- Test the main navigation and important internal links.
- Submit the main forms and check what happens afterwards.
- Check key pages on a phone as well as a desktop.
- Look for missing images, broken assets and obvious JavaScript errors.
- Check that HTTPS is working correctly across the site.
4. Is it fast enough?
Performance is not just about winning a score in a testing tool. It is about whether the site feels responsive when someone is actually using it.
Look at the pages that matter most. A huge hero image, unnecessary scripts, third party widgets and poorly optimised assets can all add friction. A good audit should identify the causes, not simply announce that a score is 72.
5. Can everyone use it?
Accessibility deserves its own check rather than being treated as a tick box. Can someone navigate with a keyboard? Are form fields labelled? Is there sufficient colour contrast? Do interactive controls make sense to someone using a screen reader?
Automated tools are useful for finding some problems, but they cannot judge everything. A site can pass an automated scan and still be frustrating or impossible for some people to use.
6. Does it build trust?
People make judgements quickly. Look for clear contact details, honest service descriptions, useful proof, sensible pricing information where appropriate and consistent branding.
Trust also comes from the small things. A form that works. A professional email address. No outdated announcements from three years ago. No five different versions of the company name across the site.
7. Does it convert?
Once someone has found the site and understood the offer, the next step should be obvious. Do not make a visitor hunt for a phone number, enquiry form or booking action.
Review the journey from landing page to conversion. Are calls to action clear? Are forms asking for information that is genuinely necessary? Is there a useful next step on pages that receive search traffic?
8. Is anyone looking after it?
A website is not finished when it goes live. Software changes, links break, content becomes stale and business priorities move on.
Check when the site was last reviewed, who owns the domains and hosting, whether backups exist, whether security updates are handled and whether there is a clear process for making changes.
A simple website health framework
When we look at a website, it helps to think in six broad areas:
- Findability: can the right people and search systems discover it?
- Clarity: does it explain the business and its offer?
- Usability: is it straightforward to use on real devices?
- Accessibility: can people with different needs use it?
- Conversion: does it make the next step obvious?
- Maintenance: is someone actually keeping it healthy?
That is a much more useful starting point than asking whether a website is simply “good”. A website can be technically impressive and commercially useless, or visually simple and exceptionally effective. The job is to understand what is helping and what is getting in the way.