Website Speed and Sales: How a Slow Site Quietly Costs You Customers

Speed is the least glamorous thing on a website and one of the few that touches every other number. It affects how many visitors stay long enough to read your offer, how many finish a checkout, and how Google ranks you. It is also invisible to the person who commissioned the site, because they usually check it on office fibre on a laptop, where everything looks fine.

Test it the way your customers experience it

The single most useful habit is testing on the real conditions of your market: a mid-range Android phone, mobile data, somewhere with imperfect signal. A site that opens instantly in a Makati office can take an uncomfortable amount of time in a jeepney in Rizal or a barangay in the province. That second experience is the one costing you sales.

The three numbers Google actually publishes

You do not need to guess at what "fast enough" means. Google's Core Web Vitals define it, and these are the published thresholds for a page rated good:

• Largest Contentful Paint (LCP) under 2.5 seconds — how long until the main content is actually visible.
• Interaction to Next Paint (INP) under 200 milliseconds — how quickly the page responds when someone taps something.
• Cumulative Layout Shift (CLS) under 0.1 — how much the page jumps around while it loads.

CLS is the one business owners underestimate. It is what happens when a customer taps "Add to cart" and an image finishes loading a split second earlier, pushing the button down so they tap an ad instead. It reads as a broken site, and people do not give broken sites a second chance.

What is usually making your site slow

Uncompressed images

This is the number one cause on nearly every site we audit. Photos come straight off a phone camera at several megabytes each, uploaded at full size and resized by the browser. Serve them in modern formats, at the dimensions they are actually displayed, and lazy-load anything below the first screen. A product page can often lose most of its weight through this fix alone.

Plugin sprawl

A site accumulates plugins the way a phone accumulates apps. Each one loads its own scripts and styles on every page, whether or not that page uses the feature. A popup builder, three analytics tools, two chat widgets and a slider you stopped using last year are all being downloaded by every visitor. Audit them, keep what earns its place, and remove the rest.

Cheap or distant hosting

Shared hosting bought on price is shared with hundreds of other sites competing for the same resources. Worse, if the server sits on the other side of the world, every request pays a latency toll before a single byte of your content moves. For a Philippine audience, hosting placed near your users — with a CDN in front of it — removes delay you cannot code your way out of.

Fonts, sliders and video headers

Three custom fonts, an autoplaying background video and a homepage carousel are the classic combination for a site that looks impressive to the person who approved it and loads slowly for everyone else. Carousels in particular are heavy and rarely earn their weight — visitors almost never see slide three.

No caching

Without caching, your server rebuilds the same page from scratch for every visitor, and returning visitors re-download files that have not changed since last week. Page caching, browser caching for static assets and a CDN together handle the majority of the load, freeing the server to process the things that actually matter, like checkouts.

Where slowness costs you the most

Not every slow page hurts equally. Two places deserve priority attention.

1. 1.The checkout or booking flow. Visitors entering payment details are the most sensitive to delay, because a spinning loader while money is involved reads as risk, not as slowness.
2. 2.Any page you are paying to send traffic to. Slow ad landing pages waste budget twice over — you pay for the click and lose the visitor before they read the offer.

Search visibility is the third cost, and it compounds quietly. Page experience is a ranking signal, so a slow site is competing at a handicap for every keyword — and the traffic you lose there never appears in your analytics at all, because it never arrived.

Fix it in this order

If you already have a site, do not rebuild it before you have tried the cheap wins. In our experience most Philippine sites get the majority of their improvement from the first three items on this list.

1. 1.Compress and correctly size every image, and lazy-load anything below the fold.
2. 2.Remove plugins and scripts you are not using, including old chat widgets and duplicate analytics.
3. 3.Turn on page caching, browser caching and a CDN.
4. 4.Cut the homepage down: one hero image instead of a carousel, no autoplay video, at most two font weights.
5. 5.Move to hosting that is sized for your traffic and located near your audience.
6. 6.Only then, if the numbers are still bad, look at rebuilding on a lighter foundation.

Measure it properly, not once

There are two kinds of speed data and they answer different questions. Lab data is a single test run under controlled conditions — useful for diagnosing what specifically is slow on a page. Field data is what real visitors actually experienced over the last month, which is what Google uses and what your customers live with. A page can score well in a lab test and still fail in the field, usually because real users are on slower phones and worse connections than the test assumed.

1. 1.Use PageSpeed Insights on your most important pages — homepage, top service or product page, and checkout — and read the field data section, not just the score.
2. 2.Check the Core Web Vitals report in Google Search Console monthly; it groups your whole site and shows which page templates are failing.
3. 3.Test on a real mid-range Android phone on mobile data, not just in a browser with the network throttled.
4. 4.Fix by template rather than by page — one broken product page usually means every product page is broken the same way.

Ignore the single overall score as a target. It is a useful summary and a terrible goal, because chasing the last few points often costs more than the visitors it saves. The three thresholds are what matter.

Keep it fast after launch

Sites get slower over time the same way rooms get cluttered — one uploaded photo, one new plugin, one tracking script at a time. Check your Core Web Vitals monthly, and treat a large image upload the way you would treat a large expense: worth it sometimes, never automatic. If you have staff or a VA uploading content, teach them to resize images before upload. That single habit prevents most future regressions.

Nobody ever left a website because it loaded too quickly.

Speed is not a technical vanity metric. It is the first impression your business makes, delivered before your copy, your photos or your prices get a chance to work. Fix it once, keep it fixed, and every other improvement you make to the site starts from a stronger position.