Websites

Website speed for people who are not developers

Why your site feels slow on a phone, what to measure, and the handful of fixes that account for most of the gain.

5 min read

Most visitors arrive on a phone, on a mobile network, on a device that is slower than the one you built the site on. That is the only test that matters.

Test the way your customers browse

Images are almost always the biggest problem. A photo straight from a camera can be twenty times larger than it needs to be on screen.

Images come first

Every extra script — chat widgets, pixels, sliders, font libraries — costs time on every page load. Keep the ones that earn their place and remove the rest.

Scripts you forgot you added

Measure with a free tool, note the largest element that takes the longest to appear, and fix that one thing first. Repeat.

Measure, fix one thing, repeat

Speed is not vanity. Slower pages get fewer enquiries, and search engines notice too.

The three numbers worth knowing

You do not need to read a waterfall chart. Three measurements explain nearly every slow site.

  • Largest Contentful Paint: how long until the main thing appears. Aim under 2.5 seconds.
  • Interaction to Next Paint: how quickly the page responds to a tap. Aim under 200 milliseconds.
  • Cumulative Layout Shift: how much the page jumps while loading. Aim under 0.1.

Fixes ranked by payoff

Resize and compress every image to the size it is actually displayed at, and use a modern format. Remove chat widgets, tracking pixels, sliders and font libraries that nobody uses. Limit yourself to two font weights. Load anything below the fold only when it is scrolled into view. Then, and only then, worry about caching and hosting.

Why slow sites cost money

Every extra second before a page becomes usable loses a share of visitors, and the losses are worst on phones and mobile networks — which is where most local service enquiries begin. Speed also feeds into search rankings, so a slow site pays twice: fewer people find it, and fewer of those who do stay.

Keeping it fast after launch

Speed decays. Somebody uploads a photo straight from a camera, a marketing tool adds a script, a plugin gets installed and never removed. Re-test once a quarter, keep an eye on total page weight, and make "does this earn its load time?" the standard question before anything new goes on.

Where the weight usually hides

Open any slow small business site and the same suspects appear: hero photographs several thousand pixels wide, a slider carrying five of them, three font families, a chat widget nobody answers, two analytics tools, a social feed embed and a map that loads before anyone scrolls to it. Removing four of those items typically halves the page weight without changing how the site looks.

Photographs, done properly

  • Resize to the largest size actually displayed, then export at a sensible quality.
  • Use a modern format with a fallback.
  • Give every image fixed dimensions so the page does not jump.
  • Load images below the fold only when they are scrolled to.
  • Never upload straight from a camera or phone into the page editor.

Hosting matters less than people think

Upgrading the server is the fix people reach for first and it is rarely the problem. A lean page on modest hosting beats a bloated page on an expensive plan. Fix the page first; if it is still slow after that, then look at where it is hosted and whether content is being served from somewhere near your customers.

Make speed somebody's job

Put a quarterly reminder in the calendar: run the test, note the three numbers, compare with last quarter and remove one thing. Fifteen minutes, four times a year, keeps a site fast for its whole life — which is considerably cheaper than the rebuild that eventually replaces a site everyone quietly stopped using because it took too long to load.

Want this handled for you?

Fixed-price builds with branded email, hosting and domain setup included.

Keep reading

All articles