Website analytics in plain English: what to watch, and what all those acronyms mean

Somewhere behind your website there is a quiet record of everyone who visited it: how they found you, what they looked at, and whether they did the thing you hoped they would. That record is your analytics. For most small business owners it sits in one of two states. Either it is switched off and nobody has ever looked, or it is switched on and it is a wall of charts and three-letter abbreviations that make you close the tab.

This is the plain-English version. What website analytics actually are, the handful of numbers worth watching if you have them set up, and what all those acronyms mean, so the next time you open that dashboard it reads like a sentence instead of a cockpit. I am not going to tell you which tool to use or what to pay. That is a conversation for another day. This one is just about understanding what you are looking at.

What are website analytics, really?

Analytics are a running tally of how people use your website, collected automatically as they visit. Not names and faces, in the normal case, but patterns: two hundred people came this week, most of them from Google, most of them on a phone, most of them landed on your home page, and eleven of them tapped your phone number. It is less like a security camera pointed at individuals and more like a foot-traffic counter at the door of a shop, telling you how busy it is, when, and which way people tend to walk once they are inside.

It helps to know there are really two different things people lump under "analytics." One is about how people find and use your site: how many visit, where they came from, what they do. The other is about how well your site performs: how fast it loads, how smoothly it responds. Both matter, and I will touch on each, but they answer different questions and often live in different tools.

Do I even need analytics?

Honestly, less than the internet would have you believe. A very small business can run for a long time without ever opening a chart, and be perfectly fine. Analytics are not the goal. Customers are the goal. The numbers are only useful when they help you make a decision you were going to make anyway.

So the right amount of analytics for most small businesses is: enough to answer a few simple questions, and no more. Is anyone finding me? Where are they coming from? Once they land, do they do the one thing I want, like call or book or fill out the form? If your setup answers those three, you have plenty. Everything past that is depth you can add later, if you ever actually need it. Drowning in data you never act on is not being data-driven. It is just noise with a login.

What should I actually watch?

If you do have analytics running, here is the short list that earns its keep. You can ignore almost everything else on the screen.

• Your traffic trend over time. Not today versus yesterday, which bounces around for no reason, but this month versus last, or this quarter versus the one before. The question is simply: is the line generally going up, flat, or down?
• Where your visitors come from. This is the most useful number most owners never look at. It tells you whether people arrive from a Google search, from a link on another site, from social media, or by typing your address in directly. If a change you made worked, this is where you will see it.
• Which pages people land on and leave from. The page people arrive on first is your real front door, and it is often not your home page. The page where they tend to leave is worth a look too, especially if it is a page where you wanted them to do something.
• Whether they do the thing that makes you money. A call, a booking, a form submitted, a quote requested. This is the one that actually matters, and it is the one people skip because it takes a little setup. A thousand visitors who do nothing are worth less than fifty who call.
• Where people drop off. If lots of people start your contact form or booking and few finish, that gap is telling you something is in the way. This is usually easier to see with a tool that shows you how people move through a page, rather than a table of numbers.
• Whether the site is fast and steady. Speed and stability are part of analytics too, measured from real visits. I wrote about this in more depth in is your website fast enough, and the section on acronyms below decodes the three you will see.

The numbers that look important but are not

A lot of what a dashboard shows you is what people politely call vanity metrics. They are big, they feel good, and they change nothing. Raw page views are the classic one. A page can be viewed ten thousand times and sell nothing. Total time on site is another: a high number might mean people love your writing, or it might mean they are lost and cannot find your phone number.

The test I use is simple. If a number went up or down, would I do anything differently? If the answer is no, it is decoration. Watch the numbers that map to a real question or a real decision, and let the rest scroll by. A smaller dashboard you actually read beats a huge one you avoid.

What do all these acronyms mean?

Here is the part nobody explains. These are the abbreviations and odd words you are most likely to run into, in plain language, one line each.

• GA4 is Google Analytics 4, the current, free, and by far the most common analytics tool. The "4" just means it is the fourth version. If someone set up analytics for you in the last few years, this is probably what you have.
• A session is one visit. If the same person comes back tomorrow, that is a second session.
• A user is one person (well, one device or browser). One user can have many sessions.
• Engagement rate is the share of visits where someone actually did something, stayed a little while, viewed more than one page, or took an action. Higher is better.
• Bounce rate is the old flip side of that: the share of visits where someone looked and left without engaging. A quick warning, because this one causes needless panic: the tools changed how they define it a couple of years ago, so old rules of thumb about a "good" bounce rate no longer apply. Do not read too much into it.
• An event is any single action the tool records, a page viewed, a button clicked, a video played. Modern analytics counts almost everything as an event.
• A conversion, sometimes now labelled a key event, is an event you have marked as one that matters to your business, like a form submitted or a call tapped. These are the ones to care about.
• Channels are the buckets your traffic sources fall into. Direct means they typed your address or used a bookmark. Organic means they found you through an unpaid search result. Referral means they clicked a link from another website. Social means they came from a social platform. Paid means they came from an ad.
• A UTM is a little tag added to the end of a link so analytics can tell where a click came from. If you have ever seen a long web address full of "utm_source=..." after a real link, that is a campaign being tracked.
• SEO, search engine optimization, is the practice of helping your site show up in search results. It is not an analytics number itself, but analytics are how you tell whether it is working. I unpack it in how to actually show up on Google.
• Core Web Vitals are three scores Google uses to grade how a page feels to a real person: LCP (Largest Contentful Paint, how quickly the main content loads, good is under about two and a half seconds), INP (Interaction to Next Paint, how quickly the page responds when you tap or click, good is under about a fifth of a second), and CLS (Cumulative Layout Shift, how much the page jumps around while it loads, and here you want a low number). You do not need to memorize these. You just need to know that when a report mentions them, it is talking about whether your site feels fast and steady.
• RUM, real user monitoring, means the measurement comes from your actual visitors' devices, out in the real world, rather than from a lab test on a perfect connection. It is the more honest kind, because it is what people really experienced.

That is most of the vocabulary. If you can read those, you can read almost any analytics dashboard put in front of you.

A quick self-check

If you want to know where you stand, right now:

• Do you know whether your website even has analytics running? If you are not sure, that is worth finding out, and it is often already switched on and simply never looked at.
• If it is running, open it and find just one number: where your visitors come from. Are they mostly from search, from social, or typing you in directly? That one answer usually teaches you something.
• Ask yourself what the single most valuable action on your site is, a call, a booking, a form. Do you actually know how many people do it? If not, that is the first thing worth setting up to track.
• Ignore the rest for now. You do not have to understand every chart to get value from the two or three that matter.

None of this requires you to become an analyst. It just requires knowing which few things are worth a glance.

How I think about it

I treat analytics as a way to answer questions, not as a scoreboard to obsess over. Before I design anything for a client, I look at where their current site stands, including how real visitors find it and how it performs, and I hand them a plain, graded report rather than a pile of raw numbers. It is the same thinking behind why I start with research, not a requirements list: the point is not to collect data, it is to understand what is actually happening so the next decision is a good one.

Once your site is set up so the few numbers that matter are easy to see, analytics stop being intimidating and start being useful. There is a lot more to say about the specific tools, the privacy-friendly ones especially, and I will get into comparing them in a future post once I have put them through their paces myself. For now, if your analytics feel like a foreign language, that is completely normal, and it is a good thing to sort out. You can see a few small business sites I have built or start a project.