Speed gets treated like a technical score, but the practical question is simpler: does the page load before the customer gives up or switches back to search? Check the contact page and main service page first, not every page at once.
Check: Run the contact page on a phone and note whether the first useful action appears quickly.
The first thing to check is not whether the form submits. Check where the message lands, who sees it, and whether the customer knows what happens next. A form that sends to an old inbox is an operations problem wearing a website costume.
Check: Send one test message from a phone and confirm who receives it.
If nobody can say whether the company serves a town, takes a job type, or offers a minimum project size, the page should not guess. Mark it as owner input before sending it to a designer or copywriter.
Check: List the promises the site makes that the owner has not confirmed.
A review badge in the footer is weaker than one relevant proof point near the action. Put job photos, warranty language, insurance notes, or a short project example near the place where a customer hesitates.
Check: Move one proof point closer to the quote request or phone number.
One of the fastest ways to clarify an offer is to name the edge. If the business does not take emergency jobs, residential work, tiny projects, or out-of-area requests, saying so can save the owner and customer the same wasted call.
Check: Add one 'not a fit if...' line to the busiest service page.
A longer process note for turning repeated questions into useful page answers.