Vayle
← Guides

Why Your Website Is Slow, and What That Is Quietly Costing You

The usual causes of a slow site, how to check yours in two minutes, and which fixes are worth paying for. Written for owners, not developers.

Speed is the one website problem nobody complains about. Visitors do not email to say your site took six seconds to load. They just leave, and you never learn they were there.

This is a plain-language explanation of what makes a site slow, how to check your own in about two minutes, and which fixes are actually worth paying someone to do.

Why it matters beyond the obvious

Two separate things are happening when a site is slow.

People leave. Especially on phones, on ordinary mobile connections, away from your office wifi. The visitor who bounces before the page renders is indistinguishable in your analytics from the visitor who never existed.

Google notices. Page experience, including loading performance, is part of how Google evaluates pages. It will not rescue bad content, and a fast page about nothing still ranks for nothing. But between two comparable pages, speed is a real tiebreaker, and Google measures it using data from actual Chrome users rather than a lab test.

The three measurements that matter

Google groups these under Core Web Vitals. In plain terms:

LCP, Largest Contentful Paint. How long until the main thing on the page appears. Usually your hero image or headline. Aim for under 2.5 seconds. This is the one most sites fail, and the usual culprit is an enormous image.

CLS, Cumulative Layout Shift. How much the page jumps around while loading. You have experienced this: you go to tap a button, an ad or image loads above it, and you tap something else. Caused by images without reserved space, late-loading fonts and injected banners.

INP, Interaction to Next Paint. How quickly the page responds when someone taps or clicks. A page can look loaded and still be unresponsive because the browser is busy running scripts.

How to check yours in two minutes

Run your homepage through Google's PageSpeed Insights. Then, and this is the part people skip, do two things:

  1. Look at the mobile score, not the desktop one. Desktop is flattering and irrelevant. Your customers are on phones.
  2. Look at the field data if it is shown. That section reflects real visitors over the past month. The lab score below it is a simulation. When they disagree, believe the field data.

Then test a page that matters, not just the homepage. Product pages and service pages are usually heavier and are where the money is.

The usual causes, roughly in order

Images. By a wide margin the most common. A photo straight off a phone can be several megabytes, and it is often being shrunk by the browser after downloading the whole thing. Correctly sized, modern-format images fix more slow sites than any other single change.

Too many third-party scripts. Chat widgets, analytics, pixels, heat maps, review embeds, cookie banners. Each is small on its own. Together they can outweigh your entire site, and each one is a request to a server you do not control.

Plugin and theme bloat. Common on WordPress and on Shopify stores running a bought theme plus a dozen apps. You load the code for every feature the theme offers, including the ninety percent you do not use.

Fonts loaded badly. Custom fonts are fine. Loading five weights of three families, blocking the text from appearing until they arrive, is not.

No caching or a weak host. Cheap shared hosting under load will undo good work everywhere else.

What is worth paying to fix

Cheap and high return: compressing and correctly sizing images, removing scripts nobody uses, fixing layout shift by reserving space for images, trimming fonts. On most sites this is a day of work and the biggest visible improvement.

Worth it if the site is otherwise sound: proper caching, cleaning up how scripts are loaded, replacing heavyweight plugins with lighter equivalents.

Only worth it if the build is genuinely finished: micro-optimising a site that is already fast. Diminishing returns start quickly once you are in decent shape.

Not worth it: rebuilding purely for speed when the site has other problems. If the structure and content are also wrong, you are paying twice.

The honest caveat

Speed is necessary and not sufficient. A fast site with nothing to say converts nobody, and no amount of optimisation compensates for a page that does not answer the question a visitor arrived with. Fix speed because it removes a reason to leave, not because it is a growth strategy.

That said, it is one of the few problems where you can measure the before and after, which makes it a good place to start when you are not sure what is wrong.

If you want someone to look at yours and say plainly which of the causes above applies, send it over. You get the specific list back within two business days, whether or not you do anything with it.

See what's quietly costing you sales

Send us your site and we'll send back 3 to 5 prioritized fixes for design, speed, conversion and accessibility. Free, within 2 business days.