Why page speed is a sales problem, not a tech problem

A painting company's site that takes a while to open on a phone in a parking lot is not a technical problem. It is a prospect who tapped the next result and called someone else.

Why this belongs on the sales side of the ledger

Think about when a local business gets searched for. Someone has a leak, a project, a deadline. They are on a phone, often on a weak connection, and they have a list of results in front of them. The result they tap has a short window to show them something. If the screen is blank, they go back and tap the next one. Nobody waits for a website the way they used to.

Google also treats speed as one of its signals when deciding which pages to show, so a slow site gets fewer visitors to begin with and then loses a share of the ones it gets. Either way the cost shows up as missing calls, not as an error message. That is why we talk about speed with owners as a sales issue first.

What actually makes a site slow

Almost every slow site we have opened up has the same few problems, in some combination:

• Images far larger than the screen showing them. A photo straight off a phone camera is enormous. Put ten of them on a homepage and the page is mostly waiting for photos.
• Scripts nobody can name. Chat widgets from two vendors ago, tracking pixels for campaigns that ended, fonts loaded from three places, a map that loads on every page. Each one is a separate trip to a separate server before the page settles.
• Page builders. The drag and drop tools that make a site easy to assemble ship a thick layer of code on every page, whether that page uses the features or not.
• Plugins stacked on plugins. Each one adds its own code and its own requests.
• Hosting that builds the page on every visit. If the server has to assemble the page from a database each time, the visitor waits for that work. If the server is shared with hundreds of other sites, they wait for those too.
• Hosting far from the visitor. A page served from one server across the country is slower than the same page served from a server nearby.

How we measure it from the outside

We do not start by reading code. We start by loading the site the way a visitor does: on a phone, on a mobile connection, from a location in the client's area, with nothing already stored in the browser. We time how long it takes before something useful is on the screen, how long before the page stops shifting around, and how long before a tap does something. Those are the moments a visitor feels. Then we look at what was loaded, in what order, and how big each piece was.

The weekly audit we run across client sites does the same check every Monday, so a slow week shows up before the owner hears about it from a customer.

What we change first

The order matters because the first items fix the most for the least work:

1. Images. Resize them to the screens that will show them, convert them to a modern format, and load the ones further down only when the visitor scrolls toward them. On most sites this alone changes how the site feels.
2. Remove scripts. Every script gets a question: what is this for, and who uses the result? If nobody can answer, it goes.
3. Move what remains so it loads after the page is visible, not before.
4. Fix the hosting. Pages generated ahead of time and served from servers near the visitor beat a shared server assembling pages on demand.
5. Only then, if the page builder itself is the weight, talk about a rebuild. That is a separate decision with its own set of questions.

What an owner should expect

You should not need a tool to know your site is fast. Open it on your own phone, in the parking lot, on cell service. It should be readable before you finish lifting the phone. If it is not, the people searching for you are already looking at the next result. A fast site does not win the job by itself, but a slow one quietly loses jobs you never hear about.

Speed is a standard we hold for every site we host, from a landscaper's gallery of project photos to the rider app a transit company runs on a campus.

Questions people ask