Fix these 3 things before you pay for ads
Paid traffic is a multiplier, and if your site converts at 1% right now, more ad spend just burns more money at 1%.
Read it →Most small business sites take 7 to 9 seconds to load on a phone, and the fix is usually a few hours of boring maintenance, not a full rebuild.
Someone walks up to your front door, waits eight seconds, nothing happens. They leave. That is what a slow website does every single day, except you never see it happen and you definitely never get a chance to say "wait, come back."
Speed is not a tech nicety. It is the difference between a lead and a bounce. For most small businesses I work with, the fix does not require blowing the whole thing up and starting over.
Google has the receipts on this. About 53% of mobile visitors abandon a page that takes more than three seconds to load. Not five. Not ten. Three. And the average small business website loads in seven or eight seconds on a phone, which is exactly where most of your visitors are coming from.
The money math gets uncomfortable fast. Say you get 600 people to your site each month and your close rate on serious inquiries is reasonable. If four out of every ten visitors bail before the page finishes loading, that traffic never even had a chance to read your pitch. You paid for the ad, earned the Google ranking, handed out the card, and the site just dropped the ball quietly.
Maria runs a tile and flooring shop outside Phoenix. She had been running Google ads for about two years, spending around $1,100 a month. Her calls were okay but she had this feeling the ads were underperforming. Her web person had built the site four years earlier in a drag-and-drop builder. It looked fine on a desktop.
When I ran a speed test, her homepage took 9.4 seconds to show anything usable on a mid-range Android phone. Three things were killing it: a hero image that had never been compressed, two extra font families loading from outside servers, and a chat widget firing on page load even though she used it maybe once a week.
In about a month I compressed the images (her hero went from 3.8MB to 190KB), cut the two unused font imports, deferred the chat widget, and moved her phone number out of the footer and into the header on every page. Load time dropped to 2.1 seconds. The following month her contact form submissions went from 11 to 29. Ad spend stayed exactly the same. She told me: "I thought the ads were broken. Turns out my site was."
Giant uncompressed photos are the number one offender by a wide margin. Someone uploads straight from their phone, which is a 4 or 5 megabyte file, and it sits there taxing every visitor's connection indefinitely. A properly sized web image is well under 200KB for most purposes.
After that it is script clutter. Plugins, chat widgets, review badge code, cookie banners, analytics from two or three tools nobody checks. Each one is a separate request the browser has to fire before your page feels alive. Some can be deferred. Some can be deleted with zero visible impact.
Then there is hosting. The cheapest shared hosting plans are genuinely slow. Not slightly slow. We are talking 600 to 900 milliseconds just to send back the first byte of the page, before a single image or script even starts. A better host runs $15 to $25 more per month and can cut that number nearly in half.
None of these problems require a redesign. They are maintenance, the way changing the oil is maintenance.
Google uses page speed as a ranking signal, especially for mobile searches. A slow site does not just lose the visitors who find it. Over time it loses the ability to get found at all. If your rankings have drifted down over the past year or two without an obvious explanation, speed is a fair suspect. It fits into the broader picture of local search visibility, which is worth understanding even if the details bore you to tears.
A faster site is not just better for the humans on it. It is better for the algorithm deciding whether to show it to the next human.
Sometimes the platform is the ceiling. Certain website builders compress nothing, load everything on page one, and cannot be configured otherwise. If you are on one of those and the underlying design is also working against you, patching the speed might get you from a 9-second load to a 5-second load. That is better, but still not good. That is when a rebuild makes economic sense, particularly if the site already has other problems that are costing you work.
But honestly, most sites I look at have not had the basics done. No image compression. No cleanup of unused scripts. Hosting that was fine in 2019 and is quietly struggling now. Those fixes take hours, not weeks, and they cost a fraction of what a rebuild does. The real cost of doing nothing is usually higher than people expect once you put an actual number on the leads walking away.
Maria did not need a new site. She needed someone to stop ignoring the obvious problems on the one she had. If you have a nagging feeling your site is underperforming but you are not sure exactly why, tell me what you have and I will take a look.
Run it through Google PageSpeed Insights or GTmetrix on a phone connection. If your load time is above 3 seconds, you are losing a meaningful share of visitors before they see anything.
Usually not. The most common culprits are giant uncompressed images, too many scripts loading at once, and cheap hosting. Those can be fixed in a few hours without touching the design.
Yes. Google uses page speed as a ranking signal for mobile searches. A slow site can quietly drift down in results over time even if nothing else changes.
Tell me what you're dealing with, an old site, a slow one, an app idea or a task eating your week. I'll reply myself, usually within a day.
Start a project →