Open your roofing website on your phone. Can a homeowner find the service they need, check that you cover their area and get in touch without hunting around?
This checklist starts there and follows a test lead through to your team. Use your live website, not a design preview, and start on a service page as well as the homepage. Someone arriving from search or an ad may never see your main introduction.
Have a teammate ready to check the request at the other end. Mark each check as working, needs attention, or not tested. An untested form should not count as a pass.
1. Can someone tell what roofing work you do?
Open the site without scrolling. Can you find the business name, the roofing services offered, the area served and a clear next step?
Be specific about work you actually take on. Roof repairs, replacements, inspections and commercial projects involve different questions. A homeowner should not have to decode a slogan to find out whether you handle a leaking roof or a planned replacement.
Check service pages too. Each should make sense on its own and give visitors a way to contact you about that work. Remove locations and services you no longer cover.
2. Is there believable proof near the decision?
Look for real project photos, clear descriptions of the work and genuine customer feedback. A caption can explain the roofing material, the work completed and the general area without exposing a customer's address.
Keep qualifications, warranties and memberships accurate and easy to verify. Explain what a warranty covers rather than relying on a badge. Use customer comments and photographs only with the appropriate permission.
Ask someone unfamiliar with the business what they learn from the page. If all they find is stock photography and claims of being the best, start by improving the evidence. A new layout alone won't supply it.
3. Can a visitor call without hunting?
Find the phone number from the homepage, a service page and the estimate page. Tap each call link on a phone and check that the correct number appears in the dialler. You can do this without completing a call.
Make the call button easy to spot. If it stays fixed on screen, check that it doesn't cover text, form fields or other controls.
Keep the published contact hours accurate. Only describe the number as an emergency or 24-hour service if your team actually provides that service.
4. Does the estimate form ask for the right details?
List the information your team needs to decide the next step. That might include a name, a reply method, the property area and a short description of the roofing work. Add a field because someone uses the answer, not because another website has it.
Every field needs a clear label, including an indication of whether it's required. Labels should remain clear while someone enters their details; W3C's form-label guidance explains how labels help people understand and use controls.
If photos help your team assess a request, make the upload requirements clear and test the upload on a phone. Never ask a homeowner to climb onto a roof to complete the form.
5. Can the form be completed comfortably on mobile?
Try the whole form with your phone's on-screen keyboard open. Can you see the field you're editing? Can you reach the next control? Does zooming or larger text make anything disappear?
Check that menus, pop-ups and chat tools don't get in the way. Try a longer email address and a realistic job description, rather than filling every field with a single word.
These checks catch everyday usability problems, but they don't replace a full accessibility audit. Ask your developer to test keyboard access, assistive-technology behaviour and accessible form controls too.
6. Does the visitor know whether the request worked?
With your team expecting the test, submit a clearly labelled test lead. Look for a confirmation that the request was received and a clear explanation of what happens next.
An estimate request isn't a booked appointment unless the system has confirmed one. If the office is closed, the message should say what to expect rather than promise an immediate callback.
Then try missing or invalid information. The page should explain what needs fixing without making the person guess. W3C's form-notification guidance covers clear success feedback and useful error messages.
7. Does the lead reach someone who can act?
Ask your teammate to find the test request. Check the original details, arrival time, notification and assigned owner. The website's success message is only half the check: did the office receive the lead, and does someone know to respond?
If the form connects to a CRM or job-management tool, check the record there too. Find out what happens if the same request is submitted twice and where a failed connection is reported.
Agree who handles new leads and who covers absences. Our speed-to-lead guide explains the handoff between receiving a request and giving the person a useful response.
8. Can people use the page before everything finishes loading?
Try a normal mobile connection, not only the office Wi-Fi. Watch for oversized images, video or animation that delays the useful content or shifts a button while you're trying to tap it.
Note the page, device and exact problem so your developer can reproduce it. A performance score can help diagnose a problem. Still try the tasks that matter: reading the page, calling the business and completing the form.
Check the links as well. A service tile that goes nowhere or a quote button that opens the wrong page is an obstacle you can fix.
Practical checklist
Look for evidence, not a green tick.
Mark each item Working, Needs attention or Not tested only after trying it on the real site.
| Checkpoint | Evidence to look for |
|---|---|
| Understand the service | The services and coverage make sense without visiting another page. |
| Choose a contact route | The phone link opens the correct number and the estimate route is easy to find. |
| Complete the request | Labels, keyboard, larger text and errors work on a phone. |
| Confirm receipt | The visitor sees a truthful confirmation and next step. |
| Find the real lead | The expected person can see the original details in the right system. |
| Handle the exception | After-hours, duplicate and failed-connection cases have a responsible owner. |
On a narrow screen, swipe the table to see every column. Keyboard users can focus the table area and scroll with the arrow keys.
This is a test sheet, not an assessment of your website. Fix broken contact paths before adding visual extras.
Your pass-or-fix checklist
- Services and coverage are clear on every important entry page.
- Project evidence and business claims are genuine and current.
- Call links open the correct number.
- Estimate fields are understandable and useful.
- The form works with the mobile keyboard and larger text.
- Success and error messages explain what happened.
- A test lead reaches the expected person and system.
- After-hours expectations match real staffing.
- Important buttons and links work without overlays blocking them.
Give each failed check an owner and a next action. Fix broken contact paths before adding cosmetic features or sending more paid traffic to them.
Decide what needs changing
A confusing service page needs clearer content. A broken form needs a technical fix. An unanswered request needs a better team handoff. Work out which problem you have before committing to a full rebuild.
If several parts of the site need reworking, explore our roofing website design approach. When comparing proposals, use our guide to what changes the cost of a roofing website to connect the price to the work you actually need.
