Every few months a client forwards me a speed report with a red number on it and asks if their website is broken. Usually it is not. Sometimes it is slow in a way that is costing them customers. The report alone rarely tells you which.
This post is for owners who want to understand their site's speed without learning to code. It covers what to measure, how to read the results and which fixes are worth your time.
A slow page does two kinds of damage. The first is obvious: some visitors give up before the page loads, especially on a phone with a weak signal. The second is quieter: Google uses page experience as one of many signals when it ranks pages, so a slow site can lose ground to a faster competitor with similar content.
The good news is that most small-business sites are slow for the same handful of reasons, and most of those are easy to fix.
Use Google's free PageSpeed Insights tool. Paste in your homepage address and run it. Then run it again for your busiest inner page, often a services page or a contact page, because visitors arriving from search often land there first.
A few habits make the results more useful:
The report shows a lot of data. If you only read three lines, read the Core Web Vitals. They describe what a real visitor experiences.
How long it takes for the main content, usually the big headline or hero image, to appear. Google considers under 2.5 seconds good. If yours is much higher, the cause is almost always a large image or slow hosting.
How quickly the page responds when someone taps a button or opens a menu. Under 200 milliseconds is good. Problems here usually come from heavy scripts: chat widgets, ad trackers, embedded feeds.
How much the page jumps around while it loads. You know the feeling: you go to tap a link and an image loads above it, pushing everything down. Under 0.1 is good. This is usually fixed by giving images and embeds a set size.
The overall performance score from 0 to 100 gets the most attention and deserves the least. It is a lab test on a simulated slow phone, and it can swing ten points between runs. A local bakery's site with a score of 72 and good Core Web Vitals is in fine shape.
You can also usually ignore long lists of "opportunities" that promise savings of a few hundred milliseconds. Chasing a perfect 100 can eat a developer's week for a change no customer will feel.
In the sites we audit, these five changes cover most of the gains.
This is the big one. A photo straight from a phone camera can be 4 or 5 megabytes. On a web page, the same photo should usually be under 300 kilobytes. Resize images to the largest size they will actually display, and save them as WebP or a well-compressed JPEG. HubSpot and most modern platforms will serve smaller versions to phones automatically, but only if the original is not enormous to begin with.
Open your site's settings and list every tracking code, widget and plugin. Many sites we audit still load code for a chat tool they cancelled, a heatmap trial from two years ago or three different analytics tags. Each one slows the page. Remove anything nobody is looking at.
A full-screen video behind the homepage headline looks great in a design review and loads slowly in real life. A strong still photo usually does the same job. If the video matters, show a poster image and let visitors press play.
Each font family and weight is a separate file to download. Two families with two or three weights each is plenty for almost any small-business site.
Images, maps and videos further down the page do not need to load until the visitor scrolls near them. Most platforms support this with a single setting. Just do not lazy-load the main image at the top, since that one should load first.
Brightwater Yoga, a studio in Southeast Portland, came to us with a homepage that took over six seconds to show its main image on a phone. The fixes took one afternoon: the hero photo went from 3.8 MB to 210 KB, an unused booking widget script was removed, and a background video became a photo. The main content now appears in under two seconds, and the class schedule page, their most visited, improved by about the same amount.
If you have done the five fixes above and your Core Web Vitals are still poor, the problem may be deeper: slow hosting, a bloated theme or code that blocks the page from rendering. That is when it is worth paying for a proper audit. Ask for a written list of fixes ranked by impact, so you can decide what to spend.
Speed is one item on our launch checklist for a reason. If you would like us to look at yours, send us your address and we will tell you the first three things we would change.