A website can look stunning and still perform poorly as a business tool.
It may take too long to show its main content. It may shift while it loads. It may respond late when someone taps a button. It may run well on a powerful desktop and poorly on a real phone.
Google uses Core Web Vitals to measure three concrete aspects of real-world experience: loading, responsiveness and visual stability.
But the goal is not a perfect score.
The goal is for the visitor to understand, navigate and act without friction.
A professional website has two jobs
For a small or medium-sized business, the website usually has two jobs at once:
Explain the business well
- what it does;
- who it is for;
- why it can help;
- how it works;
- how to get in touch.
Make an action easy
- send a WhatsApp message;
- ask for information;
- book;
- send a form;
- call;
- ask about a service.
The design should support both jobs.
It should not compete with them.

1. LCP: how long the main content takes to appear
Largest Contentful Paint, or LCP, measures how long it takes for the largest visible content element to render.
Google defines thresholds for LCP. Measure the real page before deciding what to fix.
On a business website, that element is usually one of these:
- a hero image;
- a large headline;
- a main content block.
What makes it worse?
- oversized images;
- fonts that load slowly;
- unnecessary scripts;
- slow servers;
- too many resources before the main content.
The business takeaway is simple:
if the first thing a customer needs to see takes too long, we start the relationship by making them wait.
2. INP: how long the website takes to react
Interaction to Next Paint, or INP, measures how quickly a page responds to user input.
Google defines thresholds for INP, measured on the real page.
This shows up in everyday actions:
- opening a menu;
- pressing a button;
- switching a tab;
- using a dropdown;
- filling in a form.
A website can look fully loaded and still feel sluggish if the browser is busy processing too much JavaScript.
Visitors never see “the browser's main thread”.
All they notice is this:
“I tapped it and nothing happened”.
3. CLS: the page should not move on its own
Cumulative Layout Shift measures visual stability.
A typical example:
you are about to tap a button when, just before you do, an image or banner appears and pushes everything down.
You end up tapping something else.
That is an experience problem, not just an aesthetic one.
It usually happens when:
- images reserve no space;
- fonts resize the text as they load;
- banners appear late;
- components are injected above existing content.
A stable page feels more controlled.
4. Google recommends looking at the experience as a whole
No single number captures the experience of a page.
Alongside Core Web Vitals, Google recommends checking aspects such as:
- HTTPS;
- correct display on mobile;
- no intrusive interstitials;
- clear separation between the main content and secondary elements.
That matches how we think about a website: we do not optimise a single metric; we optimise the visitor's journey.
5. A fast but confusing website is still a bad website
A page can have strong technical metrics and still cause business problems.
For example:
- the visitor does not understand what we offer;
- too many services are presented with equal weight;
- they do not know what to do next;
- the form asks for too much information;
- WhatsApp is hidden;
- the content is full of jargon;
- the calls to action compete with one another.
Technical performance reduces friction.
Content structure reduces confusion.
We need both.

6. Mobile should be treated as a primary environment
Many companies still review their website almost only on a large monitor.
But a customer may arrive from Instagram, Google Maps, an ad or a WhatsApp link and open the page on their phone.
That changes a lot:
- available width;
- connection;
- device power;
- the way people tap buttons;
- the visitor's patience.
A design that “fits” on mobile is not necessarily designed for mobile.
Check:
- text size;
- spacing between buttons;
- forms;
- menus;
- images;
- real speed;
- calls to action.
7. Forms are business performance too
A form can load perfectly and still fail commercially.
Every field has to earn its place.
If a few details are enough for a first enquiry, asking for more adds friction.
A good flow can collect more details later.
The first step should match the commitment we are asking for.

8. AI and chatbots must not make the page worse
Adding AI to a website can add value.
It can also add weight, scripts, pop-ups and distractions.
A chatbot should:
- load reasonably;
- not block content;
- not open aggressively;
- be accessible on mobile;
- have a clear function;
- make it easy to reach a human when appropriate.
AI should improve the experience.
It should not become decoration that slows the site down.
9. How to prioritise improvements
Not all issues have the same impact.
We would rank them like this:
First: blockers
- forms that fail to submit;
- buttons that do not work;
- errors on mobile;
- content that does not load.
Second: perceived performance
- slow hero section;
- delayed interaction;
- visual jumps.
Third: clarity
- value proposition;
- navigation;
- CTAs;
- service structure.
Fourth: refinement
- animations;
- micro-interactions;
- visual details.
A perfect animation does not make up for a broken form.
10. What a small business should measure
There is no need to turn your website into a lab.
We can start with:
- Core Web Vitals;
- sessions and landing pages;
- clicks on WhatsApp;
- forms started and submitted;
- errors;
- real conversions in the CRM.
That connects technical performance with business results.
Practical summary of priorities
In practice: a business website should first fix anything that stops people from understanding, interacting or converting. Visual refinements come later.
| Priority | Examples | Why it matters |
|---|---|---|
| 1. Functioning | Forms, buttons, mobile errors | Without this, visitors cannot complete the action. |
| 2. Performance | LCP, INP, CLS, script loading | Affects perceived speed, usability and stability. |
| 3. Clarity | Proposition, navigation, CTAs | Helps people understand the offer and the next step. |
| 4. Refinement | Animations and micro-interactions | Improves the experience once the essentials work. |
Frequently asked questions
Does a high Lighthouse score guarantee a good website?
No. It is a useful technical signal, but a website also has to be clear, easy to use, stable and capable of meeting business goals.
What should a small business look at first?
Real errors, the mobile experience, forms, perceived speed, and whether a visitor can quickly tell what you offer and how to proceed.
Can a chatbot harm performance?
Yes, if it adds heavy scripts, blocks content or loads aggressively. It should be integrated so it adds real value without weighing the page down.
You can see how we approach a business-focused professional website, or ask us about your case through Contact.
Conclusion
A professional website is not just a nice picture in a browser.
It is a system that has to:
- load;
- respond;
- stay stable;
- explain;
- guide;
- capture;
- integrate with the rest of the business.
Core Web Vitals are useful because they put numbers on part of that experience.
But the final question is still a human one:
can a visitor arrive, understand what we do and take the next step without fighting the page?