A useful business website audit follows one customer request, records visible obstacles and considers the smallest repair before a redesign. To find website projects, do not look only for businesses without a website. A local business may already have a reasonable site, yet a visitor may struggle to find a particular service or a way to get in touch. A business website audit can help you describe a specific problem. It should not become a list of faults designed to sell a redesign at any cost.
The method below follows a simple journey: understand the offer, check a local service and prepare an enquiry. It produces a short record that separates what you actually observed, what it might prevent and what you still need to ask the owner. There are three possible outcomes: propose nothing, repair a limited issue, or investigate a redesign. None should be decided from the visual style alone.
1. Choose a business and a credible customer request
Start with a situation you understand. For a plumber, it might be an enquiry about replacing a water heater; for a repair workshop, an appointment for a particular appliance. Do not combine emergency assistance, recruitment, spare parts and quote requests into the same journey. You are not investigating every possible use of the website. You are examining one commercial request that fits its advertised services.
Before opening the pages, write one sentence: “A person in [area] wants to know whether this business provides [service], then understand the next step.” Use that sentence as your guide. It prevents the review from becoming a design competition. An old animation is not necessarily a problem if it does not obstruct the journey; an attractive page can still leave the offer unclear.
Choose a business whose identity and activity are sufficiently clear. Check that you are looking at its current website, not an abandoned domain or another business with the same name. Record the starting address and the public details connecting the site to the establishment. If that connection remains uncertain, mark the record “needs verification” rather than writing a criticism addressed to its owner.
The broader guide to finding clients for a web agency helps you create an initial shortlist. The audit comes after that decision: it investigates one business rather than replacing targeting. Work through a small selection you can genuinely review, instead of an export in which every row will receive the same conclusion.
2. Follow the mobile journey without pretending to be a customer
Open the page on a real phone where possible. Also check it on a computer so that you can distinguish a mobile issue from a general one. Record the browser, approximate screen size, date and page address. You do not need a laboratory of devices to begin, but your report must describe what you actually checked.
Follow the same sequence: find the service, understand the area covered, locate useful evidence or an explanation, then reach the contact option. Write down the actions in order. “Home, menu, services, repairs, contact” explains more than an opinion such as “unintuitive navigation”. If you go back because a label is ambiguous, record that label and the destination that surprised you.
Inspect the contact route without creating a fictional enquiry. You can check that a button opens a form or telephone link, but do not make a call solely to complete your audit, and do not submit a fake quote request. Unless a test has been agreed with the business, mark form delivery “not verified”. A form appearing on screen proves neither successful delivery nor subsequent handling.
Review an apparent blockage a second time. A temporary connection problem or a window you failed to close can distort the observation. If the outcome changes, preserve that variation instead of keeping only the least favourable screenshot. For honest prospect research, “I could not reproduce it” is more useful than a manufactured certainty.
Keep these checks within the public areas intended for ordinary visitors. Logging into an account, searching for vulnerabilities or manipulating a shopping basket is not needed for this preliminary record. Its boundaries should remain visible when you share it with the owner.
Use these five checks on the same journey. The last column suggests an option to confirm, not work to carry out without permission.
| Check | Concrete action and evidence to keep | Smallest option to investigate |
|---|---|---|
| Service and area | Starting from the home page, find the selected service and locations covered; record the answering page or the missing information. | Clarify an existing page rather than create an unnecessary section. |
| Mobile menu | Open and close the menu, then follow the service link; record anything that obscures the destination or prevents reading. | Fix the menu or label before replacing the whole theme. |
| Main button | Read its promise, open its destination, and compare the advertised action with the page reached. | Repair the link or align the wording with the available action. |
| Telephone or booking | Check that the number is readable and the link opens the expected interface, without starting a call; stop a booking journey before confirmation. | Make the preferred channel visible or remove an obsolete destination. |
| Form | Without entering data or submitting, inspect labels, visible required fields and the explanation of what happens next; mark delivery and submission errors unverified. | Clarify an instruction and reserve full testing for an authorised phase. |
A row without an obstacle is useful too: write “journey accessible in this context” and move on. Do not turn the grid into a quota of faults to discover.

3. Separate observations, possible effects and questions
An observation describes something visible. A possible effect explains why it might interfere with the journey. A question establishes whether that interference actually matters to the business. Keeping these three layers separate prevents an interpretation from being presented as commercial data.
For example: “On the maintenance page, the request-a-quote button opens a missing page on my phone.” That is a verifiable observation, which needs a date and page address. “A visitor following that button may not complete an enquiry” is a plausible effect. “Is this form still your usual channel, or do you prefer telephone calls?” is the missing question before you price any work.
By contrast, “your website costs you ten customers every week” does not follow from a broken button. You do not know the traffic, alternative channels, enquiry values or number of people who encountered the issue. Even when a fault is obvious, do not turn a screenshot into an estimate of lost revenue.
Also record what works: a clear offer, a visible telephone number or well-explained projects. Those strengths help you propose a repair that preserves useful elements. A report in which every line is negative can look like a sales argument decided before the inspection.
Give each obstacle a simple confidence label: reproduced, seen once or not verified. This is not a quality score for the prospect. It is a guide for your own next decision: share a solid observation, ask for clarification or set the record aside. If another reviewer cannot understand how you reached the finding, add the missing step before sending it.
4. Use tools without turning their score into a verdict
Tools can supplement the journey, but they should not decide your commercial proposal. An automated result is most useful when it helps you ask a better question. Begin with a page the visitor actually uses, not an arbitrary address somewhere on the domain.
The PageSpeed Insights documentation distinguishes laboratory results from real-user data, which may be unavailable. Record which kind you observed rather than presenting a simulation as every visitor’s experience.
Core Web Vitals concern loading, responsiveness and visual stability. They do not diagnose a commercial need. Keep the page address and measurement context, then examine the relevant journey.
Avoid an isolated entry such as “performance: bad” in your record. Prefer: “The mobile report viewed on this date identifies something to investigate on this page; its effect on quote enquiries remains unverified.” If you cannot interpret a diagnostic finding, leave it for a specialist instead of turning it into an emergency.
For accessibility, the W3C Easy Checks provide a preliminary, non-exhaustive review. Passing a few checks does not certify the whole website. This commercial guide is neither a full accessibility audit nor a compliance statement.
The same boundary applies to security, legal obligations and search visibility. Do not promise to certify those areas after browsing public pages. Define a separate assignment with appropriate expertise and access if the owner wants to investigate them further. A narrowly described finding is more useful than a broad label you cannot substantiate. Keep the original report alongside your notes so that later reviewers can see what was measured and what you inferred from it.
Technical sources checked on 8 November 2026. Photographs are illustrations, not screenshots of a real audit.
5. Complete a short decision record
Use one record per business, then one row per obstacle. The following fields are enough for an initial conversation. They do not create a universal score: the order of action depends on the selected journey and on what the owner confirms.
| Field | What to record |
|---|---|
| Business and URL | Verified public identity and inspected domain |
| Request examined | Service, area and intended next action |
| Context | Date, device, browser and starting page |
| Steps followed | Exact route to the observed issue |
| Observation | One visible fact, without a commercial interpretation |
| Evidence | Page address, focused screenshot or reproducible description |
| Confidence | Reproduced, seen once or not verified |
| Possible obstacle | Action that this issue might make harder |
| Question for the owner | Information needed to establish the need |
| Minimum repair | Small intervention to investigate before a redesign |
| Decision | Do not contact, request clarification or propose an investigation |
Add a box headed “what works and should be preserved”. You might record a clear service page or an easy-to-find telephone number. This reduces the risk that a later proposal removes a useful journey merely to modernise the appearance.
Evidence should make the problem easy to find without exposing unnecessary information. Crop screenshots to the relevant interface and remove personal tabs, notifications or login details. A screenshot of a public page does not entitle you to portray the business as a client or publish its diagnosis in your portfolio.
Review the record and remove vague adjectives such as old, bad, modern and professional. Replace them with an action, a page and an observed outcome. If you cannot produce a factual description, the finding is probably a style preference rather than a sound reason for outreach. Keep uncertainty visible instead of filling empty cells with confident-sounding assumptions.

6. Fictional example: repair the route to an enquiry
Imagine a fictional bicycle repair workshop called Riverside Workshop in a medium-sized town. None of the results in this example comes from a real client. The journey concerns a visitor who wants a bicycle service and needs to understand how to book an appointment.
The home page clearly explains the activity and names the town. The servicing page describes what the service includes. On mobile, however, its “Request an appointment” button opens an old address that cannot be found. The same button fails on a second check. A telephone number remains accessible in the footer.
The record does not conclude “rebuild the website”. It preserves two positive observations, describes the broken link and asks whether the workshop prefers calls or a form. The minimum repair under consideration is to update the button destination and verify the corresponding journey. Actual delivery of an enquiry will be tested only with the workshop’s agreement.
Now suppose the owner explains that the form was removed because it generated requests the workshop could not handle. The problem is no longer purely technical: the button still promises an action that no longer exists. One solution could be a page explaining how to book by telephone and which details to prepare. That does not necessarily require a new tool.
In another possible response, the workshop genuinely wants to develop online booking. You would then need to examine availability, internal organisation and the tools already in use. The same initial observation therefore leads to two different scopes. That is why asking a question before selling a redesign package is a practical part of qualification, not an obstacle to making a proposal.
7. Choose a repair, deeper investigation or redesign
A focused repair makes sense when the issue is limited and the rest of the journey meets the need. Updating a link, clarifying a label or correcting service-area information may fit this case. You still need to check access, dependencies and the ability to test the change. “Small” does not mean “risk-free”.
A deeper investigation is useful when the causes remain uncertain. Several pages may show the same symptom, the owner may report missing enquiries, or a change may depend on a third-party provider. Offer a separate investigation scope: questions to answer, access required, deliverable and expected decision. Do not silently include unlimited repair work within this phase.
A redesign deserves consideration if the desired journey cannot reasonably be supported by the existing site, or if several confirmed constraints make fragmented repairs unsuitable. Discuss this with the owner and, where necessary, the current maintainer. Simply preferring a different platform is not sufficient justification.
Present the options in a clear order: retain, repair, investigate, rebuild. For each one, explain what it addresses, what it leaves out and how the result will be checked. You can recommend an option without claiming to know its commercial impact in advance.
Use the principles of a clear freelance services page to make the proposal understandable: one problem, deliverables, exclusions and a next step. The quote should not promise more than the diagnosis can support. If the owner decides to keep the current site or use the existing provider, that does not invalidate the observation. It simply means the useful next action belongs elsewhere.
8. Turn the observation into a useful conversation
Your first message does not need to contain every note. Choose the strongest observation that directly relates to a genuine customer request. Avoid alarming subject lines, supposedly personalised reports that name no page, and automatic compliments followed by the same proposal for everyone.
Here is an example to adapt only to an observation you have genuinely verified:
Hello, On your servicing page, the appointment button opens a missing page on my phone. I found your telephone number at the bottom, but I do not know whether you now prefer telephone enquiries. I can share the relevant address and a short screenshot if that would be useful. Best wishes, [Your name], [agency name], website design and improvement. If you do not wish to hear from me again, simply reply “STOP”.
The message does not claim that the business is losing money. It recognises a working contact route and allows the owner to explain a deliberate choice. Add your identity and business activity transparently, then respect the applicable channel rules and the recipient’s preferences. A public page is not a general invitation to send repeated follow-ups.
If the person replies, use their description of the need. Ask who maintains the website, which action they want to make easier and whether a change is already planned. Do not request a password by email. Any access should be arranged within an appropriate project framework, with only the permissions needed for the agreed work.
When building your initial shortlist, SprintLead for agencies can form part of your prospect research. Website verification remains a separate step: a prospect record cannot replace following the journey or confirming the need with its owner. Keep the conversation tied to that particular observation rather than expanding immediately into every service your agency offers.
For France, CNIL explains electronic prospecting rules: B2B outreach must relate to the recipient’s profession, with information and a simple objection mechanism. Also follow the rules of the relevant country. Source checked on 8 November 2026.
9. Plan the checks after implementation
The method does not end when a quote is accepted. Before changing anything, agree which journey must work after the intervention. For an appointment button, that might mean opening the correct page, understanding the instructions and, in an authorised test, delivering the enquiry to the right person.
Keep the original context so that you can compare reasonably similar situations. Reuse the address, device and steps in your record. Note the delivered version and the date of the check. If you use a measurement tool, keep its configuration too, rather than comparing results produced under entirely different conditions.
Separate technical success from commercial impact. A repaired link can be checked immediately; changes in enquiries require suitable data and an agreed observation period. Without access to those measurements, write “journey verified, commercial effect not measured”. Do not turn that limitation into a promise of a certain future result.
Also identify the parts excluded from the assignment. If another provider operates the contact page, specify who checks it. If an improvement depends on content the client has not supplied, do not mark it complete. A small, clearly delivered repair is more useful than a supposedly complete redesign with several steps left without an owner.
Finally, keep a record of the initial decision. It explains why you chose a repair instead of a redesign, or why you declined an ill-defined project. That document helps you improve your prospecting method: not by contacting more businesses, but by connecting an observation, a question and a defensible intervention more effectively. Review that connection when a project ends, including cases where the best outcome was to leave the existing website in place.
Frequently asked questions
- Can you audit a website without administrator access?
Yes, for a limited review of public pages. You can document the journey, links and visible information. You cannot infer that enquiries are received, inspect private analytics, assess complete security or confirm that the system can be edited. Those points need a separate phase authorised by the owner.
- Does a low PageSpeed score justify a redesign?
No. It identifies something to investigate in context. A focused repair may be enough, while a redesign may preserve the same problem if its cause is misunderstood. Connect the measurement to a page, a journey and a verifiable outcome before proposing work.
- Should you send the complete report in the first message?
Not necessarily. Describe one useful observation and offer to share the short record. A long unsolicited report may demand more attention than it gives back. Respect the recipient’s contact preferences, and do not interpret silence as agreement.
- How much should the audit or redesign cost?
This guide does not set a universal price. Scope, access, content, platform complexity and the required checks change the work. Clearly separate limited preliminary prospect research from a paid investigation and any subsequent implementation quote.
A useful outreach audit is not the one that finds the most faults. It lets the owner verify an obstacle, understand a proposed improvement and choose what happens next without feeling cornered. Start with one business and one journey. Keep useful evidence, remove assumptions and propose the smallest intervention that can solve the confirmed problem. A redesign may be the right answer, but it needs to earn that place in the reasoning.
