Aiwa Logic logo
All articles
Performance4 min read

Website speed is a conversion problem, not a technical one

What Core Web Vitals actually predict, what a realistic budget buys you, and which optimisations move revenue versus which just move a score.

When a website feels slow, the conversation usually turns technical: scores, plugins, servers. But visitors do not experience a Lighthouse score. They experience waiting — and while they wait, they decide whether you look like a business worth trusting. Speed is the first impression your brand makes, and it is made before a single word is read.

We rebuilt our own site with this in mind, and we apply the same approach to every client build. Here is how to think about speed as a business problem, and where the real wins are.

What visitors actually notice

Google's Core Web Vitals are a useful lens because each one maps to something a person feels:

  • Largest Contentful Paint (LCP) — how long until the main content appears. Google treats 2.5 seconds or less as good.
  • Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
  • Cumulative Layout Shift (CLS) — whether things jump around while loading, causing mis-taps. Good is 0.1 or less.

These are also part of how Google assesses page experience, so they matter for search visibility. But the stronger reason to care is simpler: a page that appears quickly, responds instantly and stays still feels professional. One that stutters feels like a risk.

Where slow websites lose time

In our audits, the same handful of causes come up again and again. Very few of them need a rebuild.

Oversized images

A hero photo exported straight from a camera can weigh several megabytes — more than the rest of the page combined. Serving modern formats such as WebP or AVIF, at the size the screen actually needs, is often the single biggest improvement available.

Too much JavaScript, too early

Chat widgets, sliders, animation libraries, tracking pixels and page builders all add script that the browser must download and run before the page becomes responsive. Most of it is not needed for the first screen. Loading it after the page appears — or removing what nobody uses — makes the site feel instant without changing how it looks.

Pages built on every request

If every visit makes the server query a database and assemble the page from scratch, visitors wait for that work every time — and if the database is slow or far away, they wait longer. Pre-building pages and serving them from a CDN close to the visitor removes that wait entirely, and pages can still refresh automatically when content changes.

Hosting far from your customers

Distance adds delay to every request. If your customers are in South Asia and your server is in the United States, each round trip carries a cost before anything loads. A CDN for static files, and servers in a region near your database and your customers, fix this.

The fastest request is the one that never has to wait for a server. Pre-build what you can, cache what you can't, and keep the first screen light.

Fixes that move revenue, not just scores

Not every optimisation is equal. Chasing a perfect 100 can cost weeks for gains no visitor will notice. We prioritise in this order:

  1. Make the first screen fast on a mid-range phone over mobile data — that is your real audience.
  2. Make the path to an enquiry or a purchase fast: the contact form, the product page, the checkout.
  3. Remove layout shifts around buttons and forms, where a mis-tap costs a lead.
  4. Only then fine-tune the long tail of pages and scores.

How to check your own site in five minutes

  • Run your homepage through PageSpeed Insights and look at the mobile result, not desktop.
  • Open the site on your own phone using mobile data, not Wi-Fi, and time how long until you could act.
  • Try the enquiry form or checkout end to end — slow steps here cost the most.
  • In Google Search Console, check the Core Web Vitals report to see how real visitors experience the site.

If the numbers are poor, do not panic and do not rebuild by reflex. Most sites can be made dramatically faster by fixing images, deferring scripts and caching pages. If you would like us to look at yours, send us the link — we will tell you honestly what is worth fixing first.

Work with us

Want this applied to your business? Let’s talk.

Keep reading