SummitAI Solutions

Sheet G-501Article

Is your contractor website fast enough on a phone?

By Dee, Summit AI Solutions · Updated

Q.01

Why does phone speed matter so much for a contractor website?

Short answer

Because many home-service searches happen on a phone, often in a hurry and sometimes on weak signal. A page that takes too long, jumps around, or hides the phone number loses the visitor before they ever read a word.

Think about where your customers are when they search. In a driveway with a leaking roof estimate in hand, in a house with no AC, standing in a kitchen with a flooded floor. They are not sitting at a desk on fast wifi. They have a thumb and a few seconds of patience.

Google publishes guidance on page experience, including loading speed, responsiveness, and visual stability, and says its ranking systems look for pages that give a good experience. Be realistic though: speed is one of many things, and a fast page that says nothing useful will not outrank a slower page that answers the question. Think of speed as removing a reason for people to leave, not as a trick to climb.

The good news is that for a typical contractor site, a handful of fixes cover most of the problem. You do not need to understand the code. You need to know what to ask for and how to check that it was done.

Q.02

What usually makes a contractor site slow?

Short answer

Oversized photos are the most common cause, followed by too many add-ons: chat widgets, tracking scripts, sliders, and video backgrounds. Each one adds weight a phone has to download before it can show the page.

Job photos are the big one. A photo straight off a modern phone can be several megabytes, far larger than a page needs. If your web person uploads those as they are, the browser has to download all of it even if it displays the picture at a small size. Ask that every image be resized to roughly the size it appears and compressed.

Next are the extras. A chat bubble, a review carousel, a booking widget, three analytics tags, a pop-up tool, and a font loaded from somewhere else can each pull in more files. Ask yourself what each one earns. If a widget has not produced a single lead you can point to, remove it.

Cheap hosting and builder templates can add to it, but you rarely need to switch platforms to fix a slow site. Start with the images and the add-ons, then see what is left. Auto-playing video backgrounds deserve special mention: they look impressive in the office and cost a lot on a phone. A still image of real work with your headline on it is nearly always better.

  • Resize and compress every photo before upload
  • Remove widgets and scripts that do not produce leads
  • Replace background video with a single strong image
  • Limit the number of fonts and font weights
  • Avoid sliders that load several large images at once
  • Ask for modern image formats if your platform supports them

Q.03

What matters on a phone besides speed?

Short answer

Whether a thumb can use it. That means a tappable phone number, buttons big enough to hit without zooming, text you can read without pinching, and nothing that shifts while the page loads.

Open your site on your own phone and use it with one hand, the way people do. Can you tap the call button without hitting something else? Do you have to zoom to read the text? Does a menu cover the content? Do form fields open the wrong keyboard? These are the small frictions that cost calls.

Watch for layout jumps. You start to tap a button, an image finishes loading above it, the page shifts, and you tap the wrong thing. That is called layout shift, and it often comes from images and embeds with no reserved space. Your web person can fix it by setting image dimensions so the browser leaves room.

Also check that forms are short and use the right input types. A phone field should bring up the number pad. A form with ten required fields on a phone is a form people abandon. Ask for name, phone, and what they need, and cover the rest on the call.

Q.04

How can you test your site for free?

Short answer

Use Google PageSpeed Insights, which is free and reports how a page performs on mobile, and the Core Web Vitals report in Google Search Console if your site is verified there. Then test it yourself on mobile data.

Go to PageSpeed Insights, paste the address of your homepage, and run it. It reports how the page performs on a mobile device and lists specific suggestions, such as images that are too large. You do not have to fix every item. Look at the top few and pass them to your web person in plain words.

Search Console is a free tool from Google that shows how your pages perform for real visitors once enough data exists. If nobody has set it up for your site, ask your web person to verify the site and give you access. You should have access to your own data.

The best test costs nothing: turn off wifi, load your site on your phone over cellular, and time how long it takes before you can read the headline and tap the number. Do it in a spot with a mediocre signal. Test your homepage and your top two service pages. Repeat after changes so you know they helped.

Q.05

What should you ask your web person to do?

Short answer

Ask for a short written list: resize and compress images, remove unused scripts and widgets, set image dimensions, check tap targets and forms on a phone, and send you before and after test results.

Vague requests like "make it faster" get vague results. A specific list gets done. Give your web person the PageSpeed report, ask which items they will fix, and agree on a date. A good one will explain what each change does in plain language.

Be wary of promises of a perfect score. Scores vary from test to test and depend on the connection, and a score is not a goal in itself. The goal is a page that shows its headline and phone number quickly on a normal phone, and does not misbehave afterward.

Finally, make it a habit. Every time you add a gallery, a plugin, or a new tracking tool, ask what it does to the page. Check speed once a quarter. And keep your own login, so you are never stuck waiting on someone to resize a photo.

  • Resize and compress all images
  • Remove plugins and scripts you do not use
  • Set width and height on images so the page does not jump
  • Make the phone number a tap-to-call link
  • Check forms and buttons by hand on a real phone
  • Send before and after PageSpeed results

Next step

Want us to look at your setup?

The free audit checks your calls, website and Google profile together and ranks the biggest gaps.

Get my free audit

Related service

Related guides

Crew Chief, the Summit AI Solutions robot mascot, waving

Find out what your phone, site and reviews are costing you.

Get my free audit
Book free audit Call