BLOG
The real cost of a slow website
Visitors don’t announce it when your site is slow — they just leave. What load time actually costs, and where the time goes.
Every millisecond of load time costs you visitors you will never know you lost. That is the uncomfortable part: slow sites don’t generate complaints. They generate silence. The person who gave up at four seconds doesn’t email you about it — they opened the next search result.
Where the time goes
When a page feels slow, it is almost always one of four things:
- Too much JavaScript. Frameworks ship hydration code for pages that are static content. The browser downloads it, parses it, runs it — and the user stares at a blank screen for most of that.
- Images that were never optimized. A hero image straight out of a design tool, served as a 2 MB PNG, doing the job of a 100 KB WebP.
- Fonts from a third-party CDN. Render-blocking requests to servers that are sometimes on the other side of the planet from your visitor.
- No caching strategy. Every visit asks the origin server to rebuild what could have been served from an edge location milliseconds away.
None of these are exotic. All of them are fixable in days, not months.
What the numbers say
Google’s Core Web Vitals set the bar the whole industry is measured against: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds. Those thresholds are not a mystery — Google publishes them, and uses them as a ranking signal. If your site misses them, you are paying a tax in both conversion and search position.
The pattern we see over and over: a marketing site rebuilt as a static site with optimized assets goes from a 4–6 second load to under a second. Nothing about the design had to change. The delivery changed.
The uncomfortable math
You do not need analytics to know slow is expensive — just arithmetic. If 100 people land on your pricing page and 3 of them bounce because the page takes five seconds to appear, that is 3 potential clients who never saw your price. Do that every day for a year and the slow page has cost you a thousand first impressions.
What we do about it
Every site we build starts from a performance budget, not a decoration budget: static-first architecture, self-hosted fonts, optimized images with explicit dimensions, and edge delivery through Cloudflare. The result loads before doubt sets in.
If your current site is slow and you want to know exactly why before spending anything, that’s a conversation — tell us about it. We also wrote about why static sites are eating the web, if you want the architectural argument.