When we audited the Kanata Mews website before rebuilding it, the Largest Contentful Paint on mobile was 6.2 seconds. That is the time from the moment a user taps the link to the moment the main content of the page is actually visible on screen. Six seconds is the kind of wait that causes people to go back and call someone else.
Six weeks later the same metric was 1.4 seconds. In the quarter that followed, inbound calls attributed to the website increased by 40 percent. Nothing else changed about the marketing. The site got faster and more people called.
This is not a coincidence. The relationship between page speed and conversion is well-documented. A one-second delay in load time reduces conversions by an average of 7 percent. On mobile, the numbers are worse. Most business websites are running load times of four to eight seconds on mobile, which means they are losing a significant portion of every visitor before the page even appears.
Why most business sites are slow
The cause is almost never the framework or the hosting provider. We see the same three problems on nearly every site we audit, and all three are fixable without rebuilding anything from scratch.
Uncompressed images. A JPEG exported directly from a camera or downloaded from a stock library sits between 3 and 8 megabytes. A properly resized, WebP-converted version of the same image is typically 80 to 200 kilobytes. That is a reduction of 95 percent or more in file size for the same visual result. On a page with six to ten images, this single change often cuts load time in half. We find this issue on virtually every site we audit. It is the highest-leverage fix available and it is being ignored on almost every site we have ever looked at.
No cache headers on static assets. When a browser downloads your CSS, JavaScript, and image files, it can store copies locally so that the next time the same visitor loads a page, those files do not need to be downloaded again. This is called browser caching and it is enabled through cache headers on your server or CDN. If these are not configured, every page load for every visitor starts from scratch. A single configuration file change on your server or one toggle in your CDN settings fixes this permanently. The improvement on repeat visits is dramatic.
Render-blocking third-party scripts. Most business websites have accumulated a stack of third-party scripts: Google Tag Manager, Meta Pixel, Hotjar, a chat widget, a booking plugin, a review badge. When these scripts are loaded synchronously in the document head, the browser has to pause rendering the page while it downloads, parses, and executes each one. Users see a blank screen during this process. Moving these scripts to load asynchronously or deferred, so they run after the main content is visible, often reduces perceived load time by one to two seconds with no functional change to anything on the page.
The metric to look at first
Largest Contentful Paint is the number that correlates most strongly with conversion rate. It measures how long it takes for the main visible content of your page to appear. Google considers anything under 2.5 seconds to be good, 2.5 to 4 seconds to be needs improvement, and anything over 4 seconds to be poor. Most business websites are in the poor category on mobile, which is now where the majority of their traffic comes from.
Time to First Byte matters as well. This is how long it takes for your server to start sending any response. If this number is above 600 milliseconds, the bottleneck is the server itself, not the page content, and the fix is a different conversation about hosting or server configuration.
How to audit your own site in ten minutes
Go to PageSpeed Insights and enter your URL. Run it for mobile first, since that is where most of your visitors are and where the scores are typically worst. Look at the Opportunities section on the results page. This section tells you exactly which issues are causing the most delay and gives you an estimated time saving for fixing each one.
If the top items are image-related, you are in the majority. The fix is straightforward: run your images through a converter, upload WebP versions, and update your image references. A developer can do this in a few hours. If you use a CMS like WordPress, there are plugins that automate the conversion going forward.
If the top item is Eliminate Render-Blocking Resources, the fix is the async and defer script loading described above. If the top item is server response time, you have a hosting problem and the solution is either a CDN or a different host.
What a fast site actually changes
The conversion rate improvement is real and measurable, but it is not the only thing that changes. A slow site is a signal of overall neglect that affects everything downstream, from how a visitor perceives your business to how much of your traffic ever sees your offer at all.
The Kanata Mews result was not unusual. A 40 percent increase in call volume from a speed improvement alone is on the high end, but we have seen consistent double-digit conversion improvements from speed work on every site we have rebuilt or audited in detail. The improvement is fastest and most dramatic on mobile, where the baseline is typically worst and where the most leads are being lost.
We do this audit as part of every onboarding engagement. If you want to know where your site stands before discussing anything else, book a 30-minute call.