Why a slow website is costing you customers right now

“The site feels slow” is a complaint that gets said in the hallway and rarely makes it into the company budget. It should, because load speed is not a technical footnote: it is the first impression, and the first impression decides whether someone stays or leaves.

What Google (and your customers) actually measure

Google uses three specific metrics, the Core Web Vitals, to judge a page’s experience:

• LCP (Largest Contentful Paint): how long it takes for the main visible element to appear — usually a large image or headline. Past 2.5 seconds, people start to notice.
• INP (Interaction to Next Paint): how long the page takes to respond when someone clicks or taps something. A button that lags feels broken, even if it technically works.
• CLS (Cumulative Layout Shift): how much the content “jumps” while loading. It is the reason you sometimes click the wrong button because the page moved right before you tapped.

None of the three depends on “how heavy the site is” in the abstract. They depend on how it is built.

The real cost, not the technical one

Data point: e-commerce studies put the conversion drop at roughly 7% for every extra second of mobile load time.

That is not an abstract number: on a site generating 50 quote requests a month, one extra second can mean 3 or 4 fewer requests, every month, silently. Nobody sends a complaint email about a slow site; they just move to the next tab.

The most common causes (and the ones that actually matter)

1. Unoptimized images. By far the number one cause. A 4 MB photo uploaded straight from the director’s phone can wreck the LCP of the entire homepage.
2. JavaScript that blocks interaction. Third-party scripts (chat, analytics, pixels) loaded without priority, competing for the same thread the user needs in order to click.
3. Poorly loaded web fonts. A custom typeface that takes too long to arrive can cause the layout shift that makes people tap the wrong thing.
4. A server far from the user, or no caching. If your audience is in Spain and the server sits on another continent, every request adds latency that no amount of code optimization fully offsets.

What we do differently

We optimize images automatically into the right format and size for each device, prioritize loading what the user sees first, and delay what is not critical (chats, third-party pixels) until after the initial interaction. The result is not a “prettier” site: it is one that converts better because it never makes anyone wait.

How we do it at Bitora

Before touching a line of design, we measure: Lighthouse, real data from Search Console and, when there is enough traffic, Google’s CrUX. That tells us whether the problem is images, the server, or third-party JavaScript — and we fix it in that order.

If you suspect your site is losing customers to speed, check the full approach on custom web development.