Why a fast site matters, and what slows one down
The litetile team
Someone taps a link to your site from a search result. For a moment the screen stays white. They tap back and choose the next business on the list. They never saw your headline, your photos or your prices.
That is what a slow site costs: not a worse impression, but no impression at all. This post explains what "fast" means to a visitor, what usually slows a small business site down, how to measure it with a free tool, and which parts are yours to fix.
Visitors do not measure speed in numbers. They notice three moments:
- Something useful appears. Not a blank screen or a spinner, but your headline and main image.
- The page responds. When they tap a button or open the menu, something happens straight away.
- Nothing jumps. The page does not shift while it loads, so the button they were about to tap does not move.
Google measures these same three moments and calls them Core Web Vitals: Largest Contentful Paint (how soon the main content appears), Interaction to Next Paint (how quickly the page responds to a tap) and Cumulative Layout Shift (how much the page moves while loading). Google counts a page as good when the main content appears within 2.5 seconds, the page responds within 200 milliseconds, and the layout shift score stays at 0.1 or below.
Google has said it takes these measures into account in search, alongside many other signals. Speed will not lift a page that does not answer the search, but a slow page makes a good answer harder to reach.
The real test is a phone on mobile data, not your office computer on fast wi-fi. That is where most visitors meet your site, and where slowness shows first.
Small business sites are rarely slow because of one big problem. They are slow because of a few common ones that add up.
- Huge photos. A photo straight from a phone camera can be several megabytes and thousands of pixels wide. A phone screen needs a small fraction of that. Uploaded unchanged, one photo can weigh more than the rest of the page put together, and a gallery of them can take a long time to appear on mobile data.
- Scripts. Every chat widget, tracking code, social media feed, review carousel and animation library adds code that the phone has to download and run before the page feels ready. Each one seems small; together they are often the main cause of a slow, unresponsive page.
- Fonts. Each typeface, and each weight of it, is a separate file to download. Two families with a few weights is plenty. Some pages show no text at all until their fonts arrive.
- Pop-ups and overlays. Newsletter pop-ups, promotional banners and chat bubbles cover the content, often load late, and push things around as they appear.
- Autoplaying video. A large video at the top of the page can delay everything else. If you use one, keep it short and show a still image until it loads.
The simplest test is your own phone. Turn off wi-fi, open your site, and notice how long the first screen takes and whether anything jumps.
For a closer look, Google's free PageSpeed Insights at pagespeed.web.dev tests any address. Type in your page and it reports two kinds of results:
- Field data from real visitors using Chrome, when your site has enough traffic to report. Many small sites do not, and that is normal.
- A lab test that loads your page on a simulated phone and connection, gives a score from 0 to 100 and lists what slowed it down, such as images that are too large or scripts that block the page.
A few habits make the results more useful. Look at the mobile result first. Run the test two or three times, because lab scores move from one run to the next. Test a few pages, not just the home page. And work through the listed problems rather than chasing a perfect score; a page that appears quickly and does not jump is what matters.
Even with a well-built site, a few choices are yours, and they matter most.
- Photos. Upload good photos, but crop them to what you need first. Do not use photos of text, such as a menu or a price list; write the text on the page instead.
- How much is on one page. Twenty photos in a gallery weigh more than six good ones. Pick the best and leave the rest.
- Third-party additions. Before you add a widget, a feed or a tracking code, ask whether it earns its place. Remove the ones nobody uses.
- Fonts. Keep to one or two families, and only the weights you use.
- Pop-ups. Most small business sites are better without them.
Some speed work should not be yours to do by hand. A good website builder resizes each photo for each screen size, serves images in modern formats, keeps its own pages light, and does not load code a page does not use. When you compare builders, ask what they do about each of these.
litetile handles that part on every publish: photos are resized for each screen and pages are published light, without heavy scripts, so what you choose to add is what decides most of the weight. See what is included.
Related reading: Designing for the phone in your customer's hand and Photos for your website: your own or stock.
