Services

Start a project Chat on WhatsApp
News & Insights

Is Your Website Slow in Google’s Eyes? A Small Business Guide to Core Web Vitals

Small business owner working at a desk on a laptop

Your website might look fine on your own laptop and still feel slow to the people who matter most: your customers. A visitor who waits for a page to load, taps a button that does not respond, or watches the text jump while they are reading it is a visitor who may leave and try a competitor. Google measures exactly those experiences through Core Web Vitals, and the results feed into how your pages perform in search.

Core Web Vitals are three measurements Google collects from real visitors using the Chrome browser, through a dataset called the Chrome User Experience Report. That detail matters. These are not only lab scores from a single test on a fast connection. They reflect how real people experience your pages, on their phones and connections, and Google judges each metric at the 75th percentile of visits. In plain terms, three out of four visits need to meet the target, not just the average visit.

Google treats page experience as one ranking signal among others. Relevant content still matters more than speed alone, and a fast site with thin or unhelpful content will not outrank a useful site purely because it loads quickly. Speed works as a tie breaker and as a customer experience issue in its own right. When two businesses offer something similar, the one whose site feels smooth is easier to buy from.

The three metrics, in plain English

Largest Contentful Paint, or LCP, measures how long the largest visible element on the page takes to load. On most small business pages that element is the hero image or the main heading. A slow LCP usually means a heavy image, a slow server, or a page that waits for other work before it shows the main content. Google classes LCP as good at 2.5 seconds or less.

Interaction to Next Paint, or INP, measures how quickly a page responds when a visitor taps a button, opens a menu, or types in a form. A high INP means the page is busy doing other work when the visitor tries to use it, often because of heavy scripts or a page builder loading more code than the page needs. Google classes INP as good at 200 milliseconds or less.

Cumulative Layout Shift, or CLS, measures how much the page moves while it loads. If the text jumps when an image or an advert loads late, or a button moves just as a visitor tries to tap it, that is layout shift. Google classes CLS as good at 0.1 or less, and it is the metric most small business sites fail without noticing.

A site passes only when all three are in the good band for enough real visits. Fixing one and ignoring the others is not a pass.

How to check your own site

Start with two free Google tools, and understand what each one tells you.

PageSpeed Insights, at pagespeed.web.dev, tests one page at a time and shows both field data from real visitors and lab data from a controlled test. Run your home page and your most important service or product page, on mobile first, and note which metric is in the poor band rather than chasing the single headline score.

Google Search Console, in the Experience section under Core Web Vitals, groups your pages into good, needs improvement, and poor, based on the same real visitor data. That view tells you whether the problem is one page or the whole site, which is the first question to answer before you change anything.

Check mobile first. Most small business visitors arrive on a phone, and mobile scores are almost always worse than desktop scores because phones have less power and often a slower connection. A site that passes on desktop and fails on mobile still fails for most of its visitors.

What usually slows a small business site down

Most slow sites share a small set of causes, and they are rarely mysterious.

Oversized images are the most common cause. A photo uploaded straight from a camera or a phone can be several megabytes, and a page with five of those images asks a visitor to download far more than they need to see. Images should be resized to the size they appear at and saved in a modern format.

Too many scripts are the next cause. Chat widgets, tracking tools, pop ups, social feeds, and page builder features all add JavaScript that has to download and run before the page feels responsive. Each one alone may be small, but together they can push INP over the limit.

Slow hosting is the third cause. If the server takes a long time to respond, every metric suffers, because nothing can load until the server answers. Shared hosting that is overloaded, or a server located far from your visitors, shows up here.

Finally, late loading elements cause layout shift. Images without width and height values, adverts that appear after the text, and web fonts that load after the page has drawn all push content around and damage the CLS score.

The fixes that help first, in order

Work in this order, and measure after each step rather than changing everything at once.

First, shrink the images. Resize them to the size they actually appear at, convert them to a modern format such as WebP, and let WordPress serve a smaller version to mobile visitors. This one change often fixes a failing LCP score on its own.

Second, cut what you do not need. Remove plugins and scripts that are no longer used, and check whether your theme or page builder loads features you never use. Every extra script is another thing that has to download, run, and wait its turn before the page responds.

Third, fix the hosting and caching basics. If your host is slow or your server is far from your visitors, no amount of image shrinking will fix the wait. Make sure your site uses caching, which stores ready copies of pages so the server does not rebuild them on every visit, and ask your host whether a content delivery network is included for your audience’s location.

Fourth, deal with layout shift. Give images and embedded content fixed width and height values in your theme or builder, and load web fonts in a way that does not swap them in late and push text around. Most themes have settings for this, so check them before you accept the shift as normal.

Fifth, look at the theme and the page builder. A heavy theme with many built in features can load far more code than a simple site needs. If the theme or builder is the bottleneck, switching to a lighter one is often cheaper than paying for a faster server to carry the extra weight.

What not to chase

Do not chase a perfect lab score. A score of 100 on a single test does not mean real visitors have a good experience, and a score in the high 90s is usually good enough for a small business site if the field data is in the good band.

Do not expect speed alone to fix rankings. Speed will not rescue thin content, a weak service, or a site that does not answer the visitor’s question. Treat speed as the foundation, and build useful content on top of it.

Do not accept a single number as proof either. A developer who reports only a lab score, without field data from Search Console, has not proved the site passes. Ask for both, and ask for the mobile figures.

When to ask a developer for help

You can check the scores yourself, and you can fix images and remove unused plugins without a developer. When the problem is the theme, the server, or the way the site is built, a developer can usually find it faster than trial and error, and the fix is often a change to how the site loads rather than a new design.

If you are planning a new site or a redesign, put Core Web Vitals in the brief from the start. It is far cheaper to build a fast site than to speed up a slow one after launch.

If you would like help with a site that feels slow, see Digilistan’s Web Development service, and how it connects with SEO Optimization and Hosting and Setup. You can also get in touch to talk through which pages matter most for your customers.

Start the conversation

Tell us what you are building

Whether you need a website, a chatbot that never sleeps or a workflow that gives your team its evenings back, start with a short conversation. We reply to every serious enquiry personally.

  • Your message goes to the founder, not a call center.
  • We suggest the smallest service that fixes the problem.
  • The first conversation costs nothing but a few minutes.

Prefer to talk first? Message us on WhatsApp and skip the form.

Chat with us