Your site takes seven seconds to load on a phone. Your competitor's takes two. You both do good work. One of you gets the call.
I spent five-plus years as a developer inside the PPC and SEO industry before starting MAKR Labs. I watched small businesses pay for clicks that landed on pages too slow to convert. The ads worked. The site lost the customer. Nobody billed for that part.
The good news: slow small-business sites are rarely slow for interesting reasons. It is almost always the same four problems, stacked.
Where the weight comes from
Page builders. Elementor, Divi, WPBakery and friends make editing easy by shipping everything, everywhere. Slider libraries you never use. An icon font for three icons. Scripts that load whether the page needs them or not. Convenience for the person editing, weight for every person visiting.
Plugin stacks. An aging WordPress site commonly runs twenty to forty plugins. Each one can inject its own CSS and JavaScript into every page. The gallery plugin loads on your contact page. The form plugin loads on your gallery. Things get added when there is a problem. Nothing gets removed when the problem goes away.
Unoptimized images. A photo straight off a phone is often 3 to 5 MB. Put twenty of them on a job-photos page and you are asking a visitor to download a small movie over parking-lot LTE. Most of those photos could be a tenth of the size with no visible difference.
Cheap hosting. On five-dollar shared hosting your site waits in line behind hundreds of strangers' sites. The server can take a second or more just to start answering. Every other problem stacks on top of that head start.
| Culprit | What it adds | The fix |
|---|---|---|
| Page builder | Scripts and styles for features you never use | A lean build without the builder |
| Plugin stack | Every plugin injects code into every page | Audit hard. Keep the few that earn it |
| Raw images | Multi-megabyte photos on mobile connections | Resize, compress, serve modern formats |
| Shared hosting | A long wait before the page even starts | Hosting that answers in milliseconds |
What slow costs
You do not need a study to know people hate waiting, but the studies exist. Google's own published research, cited everywhere for years, found the chance of a bounce climbs sharply as mobile load time stretches past a few seconds. Treat the exact percentages as rules of thumb. The direction is not in question.
Here is the version that matters to a contractor. Most local searches happen on phones. A person with a burst pipe opens two or three tabs and calls whoever loads first and looks legitimate. The slow tab loses by default. It does not matter that your work is better if nobody waits long enough to see it.
If you run ads, it is worse than a lost visit. You already paid for that click. Google also factors landing page experience into ad quality, which means a slow page can quietly raise what you pay per click. You get charged more to convert less.
What to ask your developer
You do not need to become technical. Ask these and listen for straight answers.
- What does the site score on PageSpeed Insights on mobile? Not desktop. Mobile.
- What is the largest image on the homepage, in kilobytes?
- How many plugins are installed, and what do the bottom five actually do?
- What would happen to load time if we dropped the page builder?
- Where is the site hosted, and how fast does the server respond?
A good developer answers with plain numbers. A defensive answer, or a lecture about how speed does not really matter, is also an answer.
The five-minute test
Open PageSpeed Insights. It is a free tool from Google, no signup. Enter your URL and look at the mobile result. Then test two or three competitors. Five minutes, and you know more about your local market's websites than most sales decks will ever tell you.
We build sites that take this test in public. Every case study on this site links the live build next to the test, so you can run the numbers yourself. That is the standard worth demanding from whoever builds yours: not a promise, a public number.