Skip to content

Home / Blog

Guide

Why Is My Website Slow? Hosting Causes and Fixes

Why Is My Website Slow? Hosting Causes and Fixes

You open your site on your phone and wait. Then wait some more. The visitor you paid to bring in from an ad gives up before anything appears. So you ask the obvious question: why is my website slow? Is it the hosting, or the site itself?

The honest answer is that it can be either, or both. The common mistake is jumping to a fix before diagnosing: moving to a new host when the real problem is a 5 MB hero image, or compressing images while the server takes two seconds to respond. This guide measures first, separates hosting causes from site causes, then fixes things in order.

Step one: measure before you judge

Run your URL through Google’s PageSpeed Insights and look at two parts of the report:

  • Real-user data at the top, shown when your site has enough traffic. This is what Google uses.
  • Lab data from Lighthouse, a simulated load. Useful for spotting causes even when there is no real-user data yet.

Core Web Vitals in one table

Google’s three Core Web Vitals and their thresholds, as published on web.dev, are assessed at the 75th percentile of visits:

Metric What it measures Good Poor
LCP (Largest Contentful Paint) When the biggest element (hero image or headline) appears 2.5 s or less over 4 s
INP (Interaction to Next Paint) How quickly the page responds to taps, clicks and typing 200 ms or less over 500 ms
CLS (Cumulative Layout Shift) Whether things jump around while loading 0.1 or less over 0.25

One more number is essential for diagnosis even though it is not a Core Web Vital: TTFB (Time to First Byte), how long until the first byte arrives from the server. web.dev considers 0.8 seconds or less good and anything over 1.8 seconds poor.

Hosting or site? How to tell

This is the most useful part of the article. A simple rule of thumb:

  • High TTFB (regularly above about a second): the server is slow to build the page. Look at the hosting and its configuration first, or at heavy server-side code such as slow plugins and queries.
  • Good TTFB but poor LCP: the server answers quickly, but the browser is held up by images, fonts and scripts. The cause is usually the site.
  • Poor INP or CLS: almost always front-end issues, such as heavy JavaScript or images and ads without set dimensions. Hosting is rarely the culprit here.

Quick tests that help:

  1. Load the page twice in a row. If the second load is much faster, caching works and the problem is uncached pages.
  2. Compare a simple page with a heavy one. If even a short text page is slow, suspect the server.
  3. Watch the timing. Slowness only at certain hours, or 503 errors under load, means the server’s resources are not keeping up.

Why is my website slow? Hosting-side causes

1. No server-side caching

WordPress builds every page from scratch: it runs PHP, queries the database, then sends the result. Page caching stores a ready-made copy and serves it instantly to the next visitor, and missing page caching is one of the most common reasons for a high TTFB. An object cache such as Redis or Memcached adds another layer by keeping the results of repeated database queries in memory, which especially helps pages that cannot be fully cached, like a shop cart or the dashboard.

2. An old PHP version

Newer PHP releases are generally faster and safer, and old ones stop receiving security fixes. WordPress currently recommends PHP 8.3 or newer. Check your version in your hosting panel and test the upgrade on a staging copy first, because some older plugins may not be compatible.

3. Tight resources or noisy neighbours

On shared hosting, many sites share one server. Without fair per-account limits, one busy site can eat the CPU and memory and slow yours down. And if your plan’s resources are too small for your traffic, you will see slowdowns and errors precisely at peak times.

4. Slow storage and an unoptimised web server

Storage type and the web server itself affect how quickly files are read and requests answered. NVMe drives are much faster than traditional disks, and some web servers, such as LiteSpeed, include built-in caching that integrates with WordPress. We cover this in detail in what is LiteSpeed and why it matters for WordPress.

5. Distance between server and visitors

Every request makes a round trip, and distance adds a little to each one. It is usually a smaller factor than the causes above, and a CDN helps by serving static files from locations close to your visitors.

Site-side causes

1. Heavy images

The number one cause of poor LCP. A 4000-pixel camera photo shown in an 800-pixel space is pure waste. Fix it by:

  • resizing images to their displayed dimensions before uploading
  • using modern formats such as WebP or AVIF
  • lazy-loading images below the fold only, not your main hero image, because delaying it hurts LCP
  • setting width and height on images to avoid layout shift

2. Too many, or too heavy, plugins

The count matters less than what each plugin does. Some load CSS and JavaScript on every page even if they are used on one; others run expensive database queries. A tool like the Query Monitor plugin reveals slow queries. A practical method: on a staging copy, deactivate suspect plugins one at a time and measure after each.

3. A heavy theme, page builder and third-party scripts

Multipurpose themes and page builders can add a lot of code, and every third-party script, from chat widgets and trackers to maps and embedded videos, adds time and often hurts INP. For each one, ask: do I really need this on every page?

4. A bloated database

Over time, post revisions, expired transients, leftover settings from deleted plugins and spam comments pile up. Clean them periodically, after taking a backup.

5. Redirect chains

Sending visitors from http to https, then to www, then to another page adds needless round trips. Use the final URL directly in your ads and emails.

Quick diagnosis table

What you see Likely cause Where to start
High TTFB on every page No caching, old PHP or too few resources Hosting settings and caching
Slow at peak times, 503 errors Plan resources too small for the traffic Review the plan or the host
Good TTFB, poor LCP Large images, render-blocking fonts or scripts Images and front end
Poor INP Heavy JavaScript, third-party scripts Theme, plugins, scripts
High CLS Images or ads without dimensions, font swaps Theme and content
Very slow dashboard Heavy plugins or a bloated database Plugins and database

Fix it in this order

  1. Take a full backup before changing anything.
  2. Measure with PageSpeed Insights and note the numbers.
  3. Turn on page caching and confirm it works.
  4. Move to a supported PHP version after testing on staging.
  5. Resize and compress large images.
  6. Review plugins and third-party scripts; remove what you do not need.
  7. Clean up the database.
  8. Measure again and compare.

If you have done all of that and TTFB is still high, it is probably time for hosting that suits your site better. Every Start Bigger hosting plan runs on LiteSpeed with LSCache, NVMe storage, Redis and Memcached, with CloudLinux account isolation to limit how much one account can affect the others, and WP Toolkit gives you a staging copy to test updates safely. We also move your current site for free; see how to move a WordPress site without downtime. That said, good hosting will not fix an oversized image or a badly coded plugin; that part stays with the site.

If you would rather not handle updates, backups and security yourself, our Managed Site service takes care of them for one WordPress site while you keep full dashboard access.

In short

  • Measure before you fix: use PageSpeed Insights and watch LCP, INP, CLS and TTFB.
  • High TTFB usually points to the server or the code running on it; poor LCP with good TTFB points to images and the front end.
  • INP and CLS are mostly front-end problems; hosting is rarely the cause.
  • Fix in order: caching, PHP, images, plugins and database, then measure again.

Frequently asked questions

What counts as a fast enough website?

Google uses Core Web Vitals rather than a single load time. Aim for Largest Contentful Paint (LCP) of 2.5 seconds or less, Interaction to Next Paint (INP) of 200 milliseconds or less and Cumulative Layout Shift (CLS) of 0.1 or less, for at least 75% of visits.

Will upgrading my hosting plan always fix a slow site?

No. If your server response time (TTFB) is already good and the slowness comes from huge images or heavy scripts, an upgrade will barely help. Upgrading or switching hosts pays off when the server itself is slow to respond or runs out of resources at busy times.

How many WordPress plugins is too many?

There is no magic number. One badly built plugin can slow a site more than twenty lightweight ones. What matters is what each plugin does: whether it loads files on every page or runs heavy database queries. Remove what you do not use and test the heavy ones.

Why is my WordPress dashboard slow when the site is fast for visitors?

Visitors usually get a ready-made cached copy of the page, while the dashboard is built fresh on every request. A very slow dashboard usually points to heavy plugins, a bloated database or limited server resources.

Does server location affect speed?

Yes, distance adds time to every round trip between the browser and the server. It is usually a smaller factor than missing caching or a heavy page, and a CDN reduces its impact on static files such as images and scripts.

Read next

Jordan & Gulf

Does Server Location Matter? Germany, the Gulf and Speed

An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.

Ready to start, or have a question first?

We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)

WhatsApp