Here's something we see constantly: a business owner invests in a well-designed website, spends money on ads or SEO to drive traffic to it, and then wonders why the leads aren't converting the way they expected. We look at the site and find pages taking four seconds to load on a good connection. Six or seven on mobile.
The design is fine. The copy is fine. The hosting is the problem — and it's silently costing them customers every day.
Why load time affects conversions directly
Most people think of a slow website as an annoyance. It's actually a conversion barrier.
A few data points that are worth knowing:
- 47% of visitors expect a page to load in 2 seconds or less. (Akamai)
- A 1-second delay in load time reduces conversions by 7%. If your site generates $10,000/month, that's $700/month evaporating from one second of lag.
- As load time increases from 1 to 3 seconds, the probability of a visitor bouncing increases by 32%. (Google)
- Walmart found that every 1-second improvement in page load time increased conversions by 2%. At Walmart's scale that's enormous, but the principle applies to any site.
These aren't edge cases. They describe what happens on every slow website, including yours, when visitors hit a loading spinner and decide not to wait.
The underlying reason is straightforward: a slow website signals unreliability. If the page takes four seconds to load, a visitor reasonably wonders whether the company behind it is equally slow to respond, ship, or support. It may not be a conscious thought — but the decision to leave is real.
What Google measures: Core Web Vitals
Since 2021, Google has used a set of performance metrics called Core Web Vitals as a direct ranking signal. A slow site doesn't just lose visitors — it shows up lower in search results, meaning fewer visitors to lose in the first place.
The three metrics that matter:
Largest Contentful Paint (LCP) measures how long it takes for the largest visible element on the page — usually a hero image or headline — to load. Target: under 2.5 seconds. Most of the slow sites we inherit are in the 4–8 second range on LCP alone.
Interaction to Next Paint (INP) measures how quickly the page responds when a visitor clicks something. Target: under 200 milliseconds. Poorly optimized JavaScript is the usual culprit here.
Cumulative Layout Shift (CLS) measures visual stability — specifically, how much the page "jumps around" as it loads. If you've ever gone to click a button and had it move on you just before you tapped, that's a CLS problem. Target: 0.1 or less.
You can check your own scores for free using Google PageSpeed Insights or GTmetrix. If your LCP is over 3 seconds or your PageSpeed score is under 50, your hosting environment is likely a significant factor.
What actually causes slow load times
A lot of content about site speed focuses on code-level optimizations — compressing images, minifying CSS, enabling caching. Those things matter. But there's a ceiling to what code-level fixes can accomplish if the underlying server is slow.
Time to First Byte (TTFB) is the time between a browser making a request and receiving the first byte of a response from your server. It measures how fast your server is, before images or CSS even enter the picture. A well-configured server on quality hosting should have a TTFB under 200ms. Sites on shared hosting commonly run 800ms–2000ms — meaning the server itself is costing you a full second before your page even starts loading.
That said, here are the most common issues we find at the application level:
Unoptimized images are the most frequent culprit on business websites. A homepage hero image uploaded at 4000px wide when it's displayed at 1200px is doing three to four times the work it needs to. Convert images to WebP, size them correctly, and use lazy loading for anything below the fold.
Too many plugins is a WordPress-specific problem that compounds quickly. Each plugin can add database queries, CSS files, and JavaScript to every page load. Twenty moderately inefficient plugins will outweigh most other optimizations.
No page caching means WordPress rebuilds every page from scratch on every visit — running PHP, querying the database, assembling HTML — even when nothing has changed since the last visitor loaded it. A caching layer (built into managed hosting, or via a plugin like LiteSpeed Cache) eliminates most of that overhead for repeat requests.
Render-blocking scripts are JavaScript files that force the browser to stop and wait before it can display anything on screen. Third-party scripts — chat widgets, ad tags, analytics, social embeds — are common offenders, and they're often loaded by well-meaning marketing teams without awareness of the performance cost.
No CDN means every visitor, regardless of where they are, is fetching assets from a single server in one geographic location. A content delivery network caches your static files (images, CSS, JS) on servers worldwide and serves them from the location closest to each visitor. For a U.S.-based business with a server in Chicago, a visitor in Miami might be adding 80ms of latency that a CDN eliminates entirely.
The hosting layer is the foundation
All of the above optimizations work better — or worse — depending on the quality of your hosting environment. This is where most of the performance gap between a 1-second site and a 6-second site actually lives.
Managed WordPress hosting — the kind that 37SOLUTIONS provides — handles several of these at the infrastructure level:
- Server-level page caching so PHP and MySQL aren't running on every request
- Object caching via Redis, so repeated database queries are served from memory
- CDN integration built in, not configured separately
- PHP-FPM tuned for WordPress workloads
- SSD storage with fast I/O throughout
The result is a TTFB that's measured in milliseconds rather than seconds, and a PageSpeed score that's possible to push into the 90s — not because of heroic optimization work, but because the infrastructure is doing its job.
When clients move to us from shared hosting, the before-and-after is rarely subtle. It's common to see LCP drop from 6 seconds to under 1.5, and PageSpeed scores jump 30–40 points, with no changes to the site content at all.
How to check where you stand
If you want to see where your site is today, start with these two free tools:
- Google PageSpeed Insights — run both mobile and desktop. Mobile scores are typically lower and more consequential for most business sites.
- GTmetrix — gives you a waterfall view of what's loading and in what order, which makes it easier to identify specific bottlenecks.
Pay particular attention to TTFB and LCP. If your TTFB is over 400ms, that's a hosting or server configuration issue — no amount of image compression will fix it. If your LCP is over 3 seconds, start there.
If you're not sure what you're looking at or what to do about it, get in touch. We've done enough of these audits that we can usually tell you in a short conversation whether the problem is fixable at the code level or whether the hosting environment is the real issue.