Why speed is about money, not technology
A customer clicks your ad or a result in Google. Then they stare at a blank screen. One second, two, three — and some of them hit "back" and go to a competitor whose site opened faster.
Back in 2016, Google research showed that more than half of mobile visitors leave a page if it takes longer than three seconds to load. People have not become more patient since.
For a business this means three things:
- You pay for customers who didn't wait. In Google Ads a click is charged when it happens, not when the page finishes loading.
- Ads get more expensive. Google rates "landing page experience", and mobile speed is part of that rating. A worse rating means a higher cost per click.
- The site ranks lower in free search. Speed is one of the signals Google uses to decide whom to rank higher. Not the main one, but all else being equal, the faster site wins.
How to estimate it with your own numbers
Say you spend 20,000 UAH a month on ads, and 20% of mobile visitors close the page before it loads. That is 4,000 UAH every month spent on clicks with no chance of a lead. Plug in your own budget and you'll see what speeding up is worth.
How to check your site speed yourself
The simplest tool is Google's free PageSpeed Insights.
- Paste a page URL — not only the home page, but also the page your ads lead to.
- Keep the "Mobile" tab: most customers come from phones, and that is where sites are slowest.
- Wait for the result — it takes up to a minute.
The report has two parts, and it matters not to mix them up.
Top block: real visitor data
These are statistics from the Chrome browsers of people who visited your site over the last 28 days. If you have few visitors, this block won't appear — then look at the bottom one.
There are three key metrics here — Google calls them Core Web Vitals:
| Metric | What it means in plain words | Good |
|---|---|---|
| LCP | How long until the main content appears — the photo, heading, first screen | up to 2.5 s |
| INP | How quickly the site responds to taps and clicks | up to 0.2 s |
| CLS | Whether the page "jumps" while loading — you aim for a button and it moves | up to 0.1 |
If it says "Passed" next to them, speed is fine from Google's point of view.
Bottom block: lab test
This is the 0–100 score PageSpeed gives after a test load on a roughly average phone with slow internet. It is useful for finding causes, but don't chase 100 at any cost: real visitors matter more than a lab score.
Two more ways
- Open the site on your own phone over mobile data, not Wi-Fi. Count the seconds until you can tap something. Rough, but honest.
- The "Core Web Vitals" report in Google Search Console shows which groups of pages are slow. If you don't have Search Console connected, that's a reason of its own to connect it.
What usually slows a site down
From what I see in audits, slowness almost always comes down to one of these:
- Heavy photos. A 4–5 MB phone shot displayed at the size of a matchbox. Modern formats (WebP, AVIF) and correct sizing cut the weight several times over.
- Third-party scripts. Live chat, several ad pixels, a reviews widget, a map, a messenger button — each loads its own code. Together they often weigh more than the site itself.
- A slider on the first screen. Several large photos load at once, though the visitor sees only one.
- A site that draws everything with JavaScript. Until the script loads, the page is empty. For such sites, speed and visibility in Google are often linked.
- Slow hosting. If the server thinks for a long time before it starts sending the page, optimizing the site itself only helps partly.
Where to start speeding up
Not everything at once. The biggest effect for the least money usually comes from:
- Compressing and resizing photos on the pages your ads lead to.
- Reviewing third-party scripts: which of them really bring leads, and which were installed "just in case" and forgotten.
- Removing or simplifying the slider on the first screen.
After each change — a repeat check in PageSpeed Insights. Real visitor data updates gradually, so the honest result shows after a few weeks.
In a technical audit I check speed along with other errors and show which third-party services the site loads and how much they weigh. That way you see what slows down your site specifically, not generic advice.