Check the customer’s next step
Start with two questions: can this business help, and how do I contact it? A failed quote button matters more than colour preferences.
Allow about twenty minutes for this first look. It isn’t a complete security, accessibility or technical audit. Each check takes about a minute to start; careful testing takes longer.
Open the homepage, a service page and contact page on phone and desktop. Use free PageSpeed Insights and notes. Save addresses, dates, screenshots and exact steps, separating observations from suspicions.
Phone speed, layout and calling
Loading speed
Compare phone loading with PageSpeed Insights’ mobile results and repeat slow runs. Save the delay you saw. Say: ‘The quote button took a while to appear; can I show you?’
Layout and text
Read upright, try menus and check for sideways scrolling, tiny text or crowded buttons. Try desktop keyboard navigation too. Say: ‘The service text runs off the screen here.’
Tap to call
Tap header and contact-page numbers, checking the dialling screen without placing calls. Confirm the number is right. Say: ‘Tapping this number does nothing; customers must copy it.’
Treat speed scores as clues
Device, connection and test runs affect scores. Separate real visitor data from simulated tests and note differences from your phone. A score doesn’t establish that customers left.
Capture the obstacle: an empty screen, banner hiding a button or jumping text. Show the owner what happened. They don’t need to learn performance metric names.
Booking, quotes and business details
Booking route
Check that booking opens the right business and usable appointment screen without reserving a slot. Say: ‘This link opens an error; can we check whether customers can choose times?’
Quote form
Check labels, required fields and access to the submit button on a phone. Avoid fake inquiries. Say: ‘Only an agreed test with you can confirm where submissions arrive.’
Opening hours
Compare website hours with the public profile, including emergency service claims. Flag conflicting days. Ask: ‘Which hours should customers follow?’
Address and service area
Compare map and written addresses. Mobile trades need clear coverage without publishing home addresses. Ask: ‘Do you cover this town, and where should that be explained?’
Trust and business identity
Visible reviews
Look for readable feedback with a source, especially near service inquiry buttons. Say: ‘Customers on this page won’t see your feedback elsewhere.’ Ask whether they want it here.
Real work photos
Check homepage, team and project photos against the business. Polished doesn’t mean fake. Ask: ‘Do you have recent job photos showing your team’s work?’
Licences and credentials
Check named qualifications against linked public registers where available. A missing badge doesn’t prove missing credentials. Ask: ‘What credentials do customers ask about?’
Current footer details
Read the year and try contact and policy links. An old year doesn’t prove closure. Ask: ‘Are these contact details still correct?’
HTTPS connection
Open HTTPS and check the final address after redirects. Don’t bypass browser warnings. Say: ‘My browser showed a warning; could your host check the certificate?’
Describe obstacles without guessing losses
Show the broken link and the extra step it creates for a customer. Ask whether that matters to the owner. You can’t say how much business it lost without something to back that up.
Search access and page details
Title and description
Read the tab and page source for service and location details. Search snippets can differ. Say: ‘The title only says Home; we could explain the subject more clearly.’
Service and town detail
Compare menu pages with main services and coverage. Avoid copied pages swapping town names. Ask: ‘Is drain repair here work you want, and where is it explained?’
Search access
Read /robots.txt and look for noindex in page source. Save affected addresses and exact instructions; this doesn’t prove indexing. Ask why instructions exist before recommending changes.
Business markup
Use Google’s free Rich Results Test to compare LocalBusiness data with visible names, hours and addresses. Missing markup doesn’t establish poor rankings. Google’s markup guide explains supported fields.
Read the before-call card
The website audit feature combines public-page findings, homepage grade, phone view and PageSpeed results. Attunr shows up to three main problems and uncertainty.
Recheck important findings yourself. Blocked reads leave gaps; the card doesn’t submit forms or inspect every page. Explain what remains unconfirmed.
LoadingPlumbing repairs in Kingston- 1Main number is plain text
- 2Service text extends past the screen
- 3Quote form delivery needs confirmation
SCORE
Failed links, forms and spam
Dead links
Try navigation, service buttons and footer links, saving error addresses and referring pages. Prioritise inquiry routes. Say: ‘The boiler repair button needs pointing to the correct page.’
Form delivery
Check visible errors and unresponsive submit buttons. Agree a labelled delivery test with the owner watching the inbox. Say: ‘A thank-you message alone doesn’t confirm arrival.’
Hidden spam
Look in page source for unrelated gambling, medicine or foreign sales links, and note unexpected domain search results. Avoid suspicious destinations. Say: ‘Your developer should investigate these unrelated code links.’
Choose useful findings
Prioritise sites that won’t open, unusable contact routes and unclear services. Label findings confirmed, needs confirmation or optional. Save visual preferences for later.
Use the local SEO sales guide for search work. Link findings to services the owner sells. A missing description alone doesn’t justify a marketing programme.
Make a one-page pitch
- 01
Open with their goal
Name the service and customer action you want to make easier. Use the owner’s words once you have spoken.
- 02
Show a few findings
Use two or three screenshots. Under each, write what happened and the practical fix. Leave uncertain checks clearly labelled.
- 03
Ask for one next step
Offer a short walkthrough. Keep the detailed scope and price for a conversation about what they actually want changed.
Share findings the owner recognises
Pitch pages in Attunr use the owner’s website. They show findings, suggested fixes and phone and laptop screenshots when capture works.
Failed capture can leave screenshots missing. Read the finished page before sharing. Give it the same care as your own notes.
1LoadingServing you since 1998Welcome to our website! We are a family owned business serving the greater area.
- 1Make the main number tap to call
- 2Keep service text inside the phone screen
- 3Confirm quote enquiries reach the inbox
Prepare your next call
Start free with no card. Use site checks and pitch pages to bring something useful to show at the next conversation.
Retest after the fix
Repeat the original steps on the same page after a fix. Save a fresh screenshot and remaining questions. Ask the owner to recheck form delivery.
Review after site changes or reported problems. Keep original steps for comparison.