keepcalculator

06 Numbers and Powers

Hosting & Google PageSpeed Insights: What Matters

Card No. 06·75182 · Updated · Standard formula, shown below

Your web hosting can affect your Google PageSpeed Insights score, but it is rarely the main reason for a low score. The score is calculated from lab data (a simulated load) and field data (real user experiences), and hosting influences it mainly through server response time (TTFB), available resources, and the physical location of the server. This article explains how hosting fits into the PageSpeed equation, what you can realistically fix by switching hosts, and what you should optimize instead.

How PageSpeed Insights Works

Google PageSpeed Insights (PSI) gives two sets of scores: Lab Data and Field Data. Lab data is generated by running Lighthouse in a controlled environment (a simulated slow 4G connection and a mid-range mobile device). It measures metrics like First Contentful Paint (FCP), Largest Contentful Paint (LCP), and Cumulative Layout Shift (CLS). Field data comes from the Chrome User Experience Report (CrUX), which aggregates real-world loading experiences from actual Chrome users. Your hosting provider can affect both, but the effect is often indirect.

The Hosting Factors That Actually Matter

Several hosting characteristics directly influence the metrics PSI tracks:

  • Server response time (TTFB): Time to First Byte measures how long the browser waits before receiving the first byte of data from the server. A slow server (due to overload, poor configuration, or long processing) increases TTFB, which delays every subsequent metric. A good target is under 600ms, but many shared hosts exceed 1 second.
  • CPU and memory limits: If your hosting plan has strict CPU limits, PHP scripts (like WordPress) may be throttled, causing slow responses during traffic spikes. This shows up as high TTFB or long LCP times.
  • Server location: The physical distance between your server and your users adds latency. A host with servers in the US serving users in Europe will have higher network latency, increasing TTFB and LCP. Using a CDN can mitigate this, but the origin server still matters.
  • PHP version and caching: Newer PHP versions (8.x) are significantly faster than older ones (5.x or 7.x). A host that doesn’t let you update PHP or doesn’t have built-in caching (like OPcache) will produce slower responses.
  • Resource contention: On shared hosting, your site shares CPU, RAM, and disk I/O with other tenants. If a neighbor gets a traffic spike, your site can slow down. This is unpredictable and often the cause of intermittent slowdowns.

How to Test Your Hosting’s Impact

To see if your hosting is a bottleneck, run a few tests:

  1. Open PageSpeed Insights and enter your URL. Look at the Diagnostics section for “Reduce server response times (TTFB)”. If it’s red, your server is slow.
  2. Use a tool like WebPageTest with a location close to your server. Check the TTFB value. If it’s above 600ms, your host is likely the problem.
  3. Test a simple HTML file (not a CMS) on your server. If that also has a high TTFB, it’s definitely the hosting, not your site’s code.
  4. Check your hosting dashboard for CPU usage. If you’re consistently hitting limits, your plan is too small.

What Switching Hosts Will and Won’t Fix

Switching to a faster host (e.g., from shared to VPS or dedicated) can improve TTFB and provide more consistent performance. However, it won’t fix issues like:

  • Unoptimized images (huge PNGs, missing dimensions)
  • Render-blocking CSS/JS
  • Too many plugins or heavy scripts
  • No caching plugin or CDN
  • Large DOM size or excessive JavaScript

In fact, a site with a perfect hosting setup but terrible front-end optimization can still score 30 on PSI. Conversely, a well-optimized site on a mediocre host can score 90+. Hosting is just one piece.

How to Choose a Host for Good PageSpeed

When evaluating hosts, look for these features:

  • Server location: Choose a host with data centers near your target audience. If you have a global audience, use a CDN like Cloudflare.
  • PHP version: Ensure you can run PHP 8.0 or higher. Most modern hosts offer this.
  • Built-in caching: Look for servers with OPcache enabled, and consider hosts that offer server-side caching (like LiteSpeed with LSCache).
  • SSD storage: Solid-state drives are faster than traditional HDDs for database queries and file reads.
  • Scalability: If you expect growth, a host that allows easy upgrades to VPS or dedicated is better.
  • Uptime and support: A host with 99.9% uptime and responsive support is less likely to have unplanned slowdowns.

Common Misconceptions

“A faster host will make my PageSpeed score 100.” No. The score depends on many factors. A fast host helps, but you still need to optimize images, minify CSS/JS, and reduce server requests.

“PageSpeed Insights measures real user speed.” Lab data is simulated, not real. Field data is real, but only if your site has enough traffic to be included in CrUX (usually thousands of visits per month). If you don’t have field data, the score is purely lab-based.

“My host is slow because TTFB is high.” TTFB can be high due to slow server, but also due to slow application code (e.g., a plugin doing heavy database queries). Test with a static file to isolate.

Cost vs. Performance

Shared hosting is cheap ($2–$10/month) but often has slower TTFB and resource limits. VPS hosting ($20–$50/month) gives dedicated resources and better performance. Dedicated servers are expensive but rarely needed for most sites. A good middle ground is a managed WordPress host that optimizes for speed (e.g., with server-side caching and CDN). Before upgrading, try a caching plugin and image optimization—these are free and often yield bigger gains than a host switch.

Frequently Asked Questions

Does hosting affect PageSpeed Insights score?

Yes, but indirectly. Hosting affects TTFB, resource availability, and server location, which influence LCP and other metrics. However, front-end optimizations usually have a larger impact.

What is a good TTFB for PageSpeed?

Google recommends a TTFB of under 600ms. If your TTFB is over 1 second, you should investigate your hosting or application code.

Will switching to a faster host improve my score?

It can, especially if your current host has high TTFB or resource limits. But if your site has unoptimized images or heavy JavaScript, you may see little change.

Is shared hosting bad for PageSpeed?

Not necessarily. Many shared hosts with good caching and PHP 8 can perform well. The problem is unpredictable resource contention, which can cause slowdowns during peak times.

Should I use a CDN instead of upgrading hosting?

A CDN (like Cloudflare) can reduce latency for global users and offload static files, which helps LCP. It’s often a cheaper alternative to a host upgrade, but it doesn’t fix server-side processing time.

How can I test if my hosting is the problem?

Run PageSpeed Insights and look for “Reduce server response times”. Then use WebPageTest with a location near your server to see TTFB. Test a static HTML file to rule out application code.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →