Six tests, ten minutes
A repair business website has six jobs. Each has a one-minute test you can run on your own phone, ideally on mobile data with poor signal, because that is where a customer with a broken device is standing. The first three are the path from that phone to a job on your bench. If any of them fails, fix it before anything else.
1. State the price
Test: find the price of your most common repair. Time it.
Pass: price tables by device, item or service level, found within a minute, editable by you. Screens and batteries by model, callout fee and repair ranges by appliance, bike service levels, standard alterations, a stated diagnostic fee for anything that needs opening.
Fail: "call for a price"; a single "from" figure; prices in a PDF; a table you have to ring the developer to change.
Fix: the tables built as records on the site, matching your software's menu, with a line on what is included and what moves the price.
2. Book the job in one tap
Test: open the site on your phone. Without scrolling, is there a Book button? Tap it. Does it ask what the item is and what is wrong with it?
Pass: one tap into RepairDesk, RepairShopr, Housecall Pro, Jobber or Acuity with the repair pre-selected, the device or item captured and the fault described, landing in your job list. Drop-off, mail-in and visit as separate options where you offer them.
Fail: "call us to book"; a general contact form; a link to a hosted page where the customer has to find you again.
Fix: the booking embedded or deep-linked from a Book button in the header on every page, pre-selecting the repair from the page it was tapped on.
3. Appear in under two seconds
Test: private window, mobile data. Load the home page and your busiest repair page. Count.
Pass: under two seconds, Core Web Vitals Good on mobile in Search Console.
Fail: blank, then a slider of the shopfront.
Fix: images sized and compressed, hero prioritised, slider removed, scripts trimmed, decent hosting.
4. Take a fault with photos
Test: pretend the item has an unusual problem. Find where you would report it. Count the fields. Try to attach a photo. Submit, and time how long until it reaches a phone.
Pass: a fault form with item, make and model, symptoms, photos, whether it powers on, and a call-back window, with the diagnostic fee stated on the form, reaching your software or a phone within a minute.
Fail: a general contact form with no photo upload; an inbox checked at closing time.
Fix: the fault form built and wired, with a same-day reply promise stated on it, and a bookable diagnostic slot for customers who would rather skip the call. The electronics repair sub-page covers quoting from a description.
5. Prove you are not a kiosk
Test: find the warranty length, the grade of parts you fit and a typical turnaround. Then find what you say about the data on a customer's device.
Pass: a warranty and parts page with all of it in plain words, a data privacy promise for devices, real photos of the workshop and the people, and Google reviews near the Book button.
Fail: no warranty stated; "quality parts" with no detail; stock photos; nothing about data.
Fix: half a day of photography at the bench, the warranty page written from the questions the counter hears, reviews embedded. For a jewellery repairer add qualifications, insurance and security; the customer is handing over an heirloom.
6. Stop the status calls, and serve the business buyer
Test: find Track my repair. Then, as an office manager, try to find support plans, response times and a monthly price.
Pass: a tracking link in the header going to the software's status page or client hub, with status texts as jobs move; and a separate business IT support route with plans, inclusions, response times, per-user or per-device ranges and a discovery call booking.
Fail: no tracking, so the counter phone answers "is it ready yet" all day; business buyers landing on a page about cracked screens.
Fix: the software's status page linked and its notifications switched on; the business route written for a non-technical owner and linked from the header.
Scoring
Six of six: the site is working. Add pages for the next repairs and keep the workshop photos coming. Four or five: fix the failures, no rebuild needed. Three or fewer with 1, 2 or 3 failing: the site is losing jobs every week to the shop that told the customer the price, and the fixes cost less than a few of those jobs.
Where this sits
This is the launch checklist for every repair business website we build, and the first ten minutes of a diagnosis on an existing one. Most repair sites fail at least four, and the price tables are the fix that changes the counter phone fastest.