Why Small Business Websites Get Slow

A website is fast on launch day and slow three years later, and nobody can point to the day it changed. There wasn’t one. The weight built up gradually.

Here’s what builds up, roughly in order of how much damage it does.

Images nobody resized

This is the biggest one by a wide margin. Somebody uploads a photo straight off a phone, 4,000 pixels wide and four megabytes, into a slot that shows it at 600 pixels. The browser downloads all four megabytes and throws away 97% of the data before drawing it.

Do that on twenty pages and the site carries tens of megabytes it doesn’t need. A good share of traffic across Southeast Ohio and West Virginia comes from phones on rural broadband, and for those visitors the extra weight decides whether the page loads or gets abandoned.

The fix is plain work. Resize each image to the largest size it’s shown at, save it as WebP, and set width and height attributes so the layout doesn’t jump while it loads. Every image on this site is WebP at exactly two sizes, and all the images on a page here together weigh less than one unresized phone photo.

Most slow websites turn out to be one folder of unresized photographs.

Plugins that each seemed reasonable

A contact form, a slider, a newsletter popup, a social feed, a reviews widget, a cookie banner, a page builder. Each was a sensible decision on its own. Together they load fifteen stylesheets and twenty scripts on every page, including pages that use none of them.

The page builder usually does the most damage, because it ships its whole framework on every page whatever the page contains. On a heavily built site, a page of plain text can carry several hundred kilobytes of CSS to show one paragraph.

Audit them honestly. Most sites actively use three to five plugins and keep several more that were installed for a problem that went away.

Third-party scripts, which are somebody else’s performance problem

Analytics, tag managers, chat widgets, retargeting pixels, heatmap recorders, review embeds. Each one pulls JavaScript from a server you don’t control, and your page waits for it.

On a small business site the chat widget is often the heaviest thing on the page, heavier than all the content combined. On many of these sites nobody has read a transcript in a year.

• Ask what each script is for and whether anyone reads what it collects
• Load the ones you keep with async or defer, at the end of the body
• Hold non-essential ones until the browser is idle, after the page has loaded
• Delete the rest, including the pixel from the campaign that ended in 2023

Hosting that was cheap for a reason

Shared hosting at a few dollars a month puts hundreds of sites on one machine. When a neighbour gets busy, your site slows down. It shows up in server response time, the wait before the browser receives the first byte, and image optimisation can’t fix it.

If your time to first byte sits above about 600 milliseconds and the site isn’t doing anything heavy, blame the hosting. It’s one of the few cases where spending more solves the problem.

Fonts, redirects, and the small stuff

Four font families at three weights each means twelve files, and each one holds up the text. Two families at three weights, with display=swap so text shows right away in a fallback, is almost always enough.

Each redirect in a chain adds a round trip. A link to http://example.com/page/ that goes to HTTPS, then to www, then strips the slash makes three round trips before anything downloads. Point links at the final URL and set the server to redirect in a single hop.

How to measure it honestly

Test on a phone over a mobile connection, since the office fibre will flatter you. PageSpeed Insights gives you a lab test and, more usefully, field data from real Chrome users on your site. That field data is the only number that tells you what your actual visitors get.

1. Largest Contentful Paint: when the main thing appears. Target under 2.5 seconds.
2. Interaction to Next Paint: how fast it responds to a tap. Target under 200ms.
3. Cumulative Layout Shift: how much the page jumps while loading. Target under 0.1.

Speed is part of every website audit we run. It’s the item that most often explains why a site with decent content isn’t getting calls.