Victor
Your slow website is losing you customers
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.
Read it →
Three seconds. That is the number. If your site takes longer than that to load on a phone, a meaningful chunk of your visitors have already hit the back button and moved on to whoever sits just below you in the search results. Not because they are impatient. Because every other fast site they visit has trained them to expect instant.
The good news: most slow sites are slow for the same handful of boring reasons. And fixing them rarely means rebuilding from scratch.
How to tell if yours is slow
Open your site on your phone. Not your office wifi. Mobile data, somewhere with a normal signal. Count out loud. If you are still watching a blank screen or a spinner past two seconds, you have a problem worth fixing.
For a real number, search for PageSpeed Insights (it is a free Google tool) and paste your URL in. You will get a score from 0 to 100 and a list of what is dragging you down. Below 50 on mobile is genuinely bad. Between 50 and 74 is worth improving. Above 74 and you are in decent shape, though there is almost always something left to tighten.
One thing to know: a slow site does not just frustrate visitors. Google uses speed as a ranking signal, so a sluggish site can quietly cost you search visibility at the same time. Two problems, one cause.
The main culprit is almost always images
Not complicated code. Not servers. Images.
Someone builds a site, drags in a photo straight from their camera or their designer's Dropbox folder, and that photo is 4.2 megabytes. Looks fine on a fast laptop. Brutal on a phone. Multiply that by seven photos on a homepage and you have a site that takes eleven seconds to load on average mobile connections.
Images for a web page should almost never be bigger than 200 kilobytes. Most of the time you can get them under 100kb with no visible quality loss. Format matters too. Modern formats like WebP are noticeably smaller than the old JPEGs and PNGs most people are still uploading. A good developer compresses and converts images as part of building the site. If nobody did that when yours was built, it is probably the first thing to check.
// a quick story
Dana runs a small event venue outside Raleigh. She had been paying for Google ads for about eight months with frustrating results. Clicks were coming in, but the phone was not ringing the way she expected. When I looked at her site, the homepage was pulling in six full-resolution photos her photographer had sent over, each one between 2 and 5 megabytes. Total page weight: just over 19 megabytes. On mobile it was taking roughly 14 seconds to finish loading. After compressing and converting the images, the homepage dropped to under 1.8 megabytes and loaded in about 2.1 seconds. Her bounce rate fell 38% within three weeks and she started getting inquiries from organic traffic she had been ignoring because the ads felt like they were not working. The ads were fine. The site was the problem.
The second culprit: stuff that should not be there
Every plugin, widget, chat bubble, social feed, and cookie banner you bolt onto a site adds weight. Most of them load scripts that have to run before your page finishes. Some of them phone home to third-party servers that are slow or down entirely.
That Instagram feed widget showing your latest posts? It probably adds a full second to your load time on its own. The live chat bubble you installed and never configured? Still loading. The analytics tool your old developer added and you have never looked at? Same.
This is sometimes called "bloat" and it accumulates quietly over time. A site that was fast when it launched can become noticeably slow two years later just from add-ons piling up. The fix is not always to remove everything. But it usually involves removing something. If your contact form is buried under all that weight, the leads you are losing are invisible to you.
Hosting matters more than people think
Cheap shared hosting puts your site on a server alongside hundreds of other sites. When traffic spikes somewhere on that server, your site slows down too. You have no control over it and you probably will not notice it is happening.
If your site is on the cheapest plan available, or on a platform you vaguely remember setting up years ago and have not thought about since, it is worth checking. A better host can shave a full second off load time without touching a line of code. Google's threshold for "fast" on mobile is under 2.5 seconds for core web vitals, so that second matters more than it sounds.
What a real fix actually looks like
The most common version I see: uncompressed images, three or four unnecessary plugins, and a hosting plan chosen purely on price. That combination can easily put a site at nine or ten seconds. Getting it under 2.5 usually means compressing and converting every image, removing unused plugins, and sometimes moving to a better host.
It is not glamorous work. It does not change how the site looks. But it changes how the site performs, and that is what actually affects your bottom line. Spending money on ads to send people to a ten-second site is like running a promotion and then locking the front door.
Speed is also the kind of thing that compounds. A faster site ranks a bit higher, which brings more traffic, which means more people actually reaching your contact page or booking link. If you have been wondering why your site is not converting visitors the way it should, this is often the answer before anything else. Worth reading: 7 signs your website is scaring people off, because slow is only one way a site loses you business.
If you have a site you suspect is slow and you want a straight answer about what is wrong with it, tell me what you have and I will take a look.
Quick questions
How fast should my website load?
Under 2.5 seconds on mobile is Google's benchmark for a fast site. In practice, anything over 3 seconds loses a significant share of visitors before they see a single word.
What is the most common reason a website is slow?
Images. Most sites are loading full-resolution photos straight from a camera or Dropbox, sometimes 3 to 5 megabytes each. Compress them to under 200kb and convert to WebP and you will often cut load time in half.
Does website speed affect Google rankings?
Yes. Google uses speed as a ranking signal through its core web vitals score. A slow site can quietly cost you search visibility on top of frustrating the visitors who do find you.
// your turn
Got something like this on your plate?
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 →
