Page Speed Basics for Small Sites
Technical basics · 8 min read ·
Slow pages lose visitors. The three Core Web Vitals in plain words, how to measure them on a phone and the fixes that help small sites most.
Few things lose a visitor faster than waiting. A page that takes several seconds to show anything, or that jumps around as it loads, invites a tap on the back button. For a small business, each of those visitors is a possible customer. Speed is not only a technical nicety. It is part of how the site treats the people who use it.
The good news is that most small sites can be made noticeably faster with a few simple fixes. This guide explains the measures that matter, how to check them and what to do first.
The three measures that matter
Google's web performance guidance defines three Core Web Vitals, each capturing a different part of the experience.
Loading: how quickly the main content appears
The measure is called Largest Contentful Paint. It records when the biggest visible element, often a main image or a block of text, has appeared. The target is within 2.5 seconds of the page starting to load.
Responsiveness: how quickly the page reacts
The measure is called Interaction to Next Paint. It looks at how long the page takes to respond visually after a visitor taps, clicks or types. The target is 200 milliseconds or less.
Visual stability: how much the layout moves
The measure is called Cumulative Layout Shift. It adds up unexpected movements of content as the page loads: a button that jumps just as you tap it, or text that shifts when an image appears. The target is 0.1 or less.
Google says these should be met at the 75th percentile of page loads, segmented across mobile and desktop, which means that three out of four visits should have a good experience. The three metrics are stable in Google's terms, meaning fully supported and considered essential.
You do not need to memorise the names. Remember the three questions: does it appear quickly, does it respond quickly, does it stay still?
Why it matters
Visitors. People abandon slow pages, especially on phones with patchy connections. A fast page feels professional and trustworthy.
Search. Page experience is one of many signals, and it is less important than relevance. But a page that is clearly useful and also fast has an advantage over one that is equally useful and slow.
Mobile first. Google explains that it uses the mobile version of a site's content for indexing and ranking. A site that is fine on a fast laptop and sluggish on a mid-range phone is judged by the second.
Cost and sustainability. Lighter pages use less data and energy, which matters to visitors on limited plans.
Measure before you change anything
You cannot improve what you have not measured.
- Pick three to five key pages: home, a main service, contact, a popular article.
- Test them with a free tool that reports both real-world data, where it exists, and a lab test. Search Console includes a report on how your pages perform on these measures, which Google describes as part of helping you monitor and troubleshoot your presence in search results.
- Test on a phone, ideally a mid-range one, on an ordinary mobile connection, not just on your office wi-fi.
- Record the results so that you can compare after changes.
The tool will often suggest specific fixes. Start with the biggest ones.
The fixes that help most
For small business sites, a handful of fixes usually account for most of the improvement.
1. Tame the images
Images are the largest part of most pages.
- Resize them to the size they are shown. A photograph that is four thousand pixels wide, displayed at four hundred, wastes bandwidth.
- Compress them. Most photographs can be reduced a great deal with little visible loss.
- Use modern formats that your platform supports, with a fallback.
- Serve smaller versions to phones if your platform allows.
- Load images below the first screen lazily, so they only download when needed. Do not lazy-load the main image at the top, because that delays the loading measure.
- Set width and height on every image so that the browser reserves space and the layout does not jump.
2. Cut unnecessary scripts and plug-ins
Every script adds weight and work. Review what your site loads.
- Remove plug-ins and widgets you do not use.
- Be selective with third-party tools: chat widgets, tracking scripts, social feeds, embedded maps and videos. Each can add noticeable delay.
- Load heavy embeds on demand, for example showing a picture of a video that loads the player only when tapped.
- Keep one analytics tool unless you truly need more.
3. Simplify fonts
Custom fonts can delay text. Use a small number of font files, load only the weights you need and make sure the text shows in a fallback font while the custom one loads.
4. Choose decent hosting
Slow servers slow everything. If your pages take a long time to start loading, even with small images, the host may be the problem. Consider a reputable host with servers near your visitors, and use caching so that repeated requests are served quickly. A content delivery network can help for sites with visitors in many places.
5. Reserve space and avoid late changes
Layout shifts often come from content that appears late: banners, cookie notices, adverts, embedded forms. Reserve space for them in the layout. Do not insert content above existing content after the page has loaded.
6. Keep pages simple
Heavy page builders, sliders and animations can produce a lot of code. Where you can, use simple layouts. A page with clear text and a few good images is both quick and readable.
7. Update and tidy
Keep your platform and plug-ins up to date, remove old test pages and unused media and do not let the site accumulate clutter.
Check responsiveness
Responsiveness problems usually come from too much script work on the page. If a menu takes a moment to open or a form feels sluggish, look for:
- Large, unnecessary scripts.
- Heavy third-party widgets.
- Animations that block interaction.
Removing or deferring them helps. For simple business sites, the fix is usually to have fewer moving parts.
Test as a real user
Numbers are useful, but also use the site as a customer would.
- Open it on your phone, using mobile data, and time how long until you can read and tap.
- Try tapping a button as the page loads. Does it move?
- Ask a friend with an older phone to try.
- Watch how it behaves in poor signal.
If it feels slow to you, it is slow.
Balance speed with the rest
Speed is one of several qualities. Do not remove content that people need, such as clear text and useful images, or accessibility features, in the pursuit of a score. A fast page that does not help is no help. Google's guidance on helpful content says content should be created primarily for people and leave them satisfied. Speed serves that aim by getting out of their way.
Remember also Goodhart's observation, that when a measure becomes a target, it ceases to be a good measure. Do not chase a number at the expense of the experience. Use the thresholds as guides to what visitors feel.
A worked example
A small florist's site takes six seconds to show its main image on a phone. A test shows that the home page loads a four-megabyte hero photograph, five font files, a chat widget, a social feed and a slider. The owner decides to simplify.
She replaces the hero image with a resized, compressed version about a fifth of the size and sets its dimensions. She removes the slider and the social feed, replaces the chat widget with a visible phone number and form and cuts the fonts to two. She asks her host about caching and enables it. A retest shows the main content appearing in about two seconds on the same phone, and the layout no longer jumps.
Over the following weeks, she notes that fewer visitors leave the home page immediately, and more tap the phone number. She sets a reminder to retest every three months and to check any new widget before adding it.
Common mistakes
- Testing only on fast wi-fi.
- Huge, uncompressed images.
- Too many plug-ins and widgets.
- Lazy-loading the main image.
- Missing image dimensions, causing layout shift.
- Heavy page builders and sliders.
- Ignoring hosting.
- Obsessing over scores instead of experience.
A checklist
- Key pages measured on a mid-range phone
- Images resized, compressed and dimensioned
- Unused plug-ins and scripts removed
- Third-party widgets limited and loaded on demand
- Fonts simplified
- Decent hosting and caching
- Space reserved for late content
- Retested after changes and each quarter
The search page here finds listings by words, the categories page shows a simple structure and the submit page lets a business add a listing that links to its own site.
Frequently asked questions
Does a faster site rank higher? Speed is one factor among many. It helps visitors, which is the main reason to care.
Do I need to understand the code? Not for the main fixes. Image handling, plug-ins and hosting can be managed through your platform or by asking a developer.
How often should I test? After any significant change, and at least every quarter.
Questions and answers
- What are Core Web Vitals?
- Three measures of real-world experience: how quickly the main content loads, how quickly the page responds to interaction and how stable the layout is.
- What counts as good?
- Google gives thresholds of 2.5 seconds for loading, 200 milliseconds for responsiveness and 0.1 for layout shift, at the 75th percentile of visits.
- What slows most small sites?
- Oversized images, too many scripts and fonts, slow hosting and plug-ins that add weight without value.
- How do I test my page?
- Use the free measurement tools that report real-world and lab data, and test on a mid-range phone on an ordinary connection.