Why Is My Website Slow? Hosting-Side Causes and Fixes

A slow website usually has one of two problems: the server takes too long to produce the page (slow hosting, heavy code, no caching, resource limits), or the page is too heavy for the browser to load quickly (large images, too much JavaScript, many third-party scripts). The first step is to find out which one you have, because the fixes are completely different.

This routine starts with the cheapest checks and ends with when to change hosting.

Step 1: Measure before you change anything

Test the same page several times, at different times of day, using:

• PageSpeed Insights (pagespeed.web.dev), which shows field data from real Chrome users when available, plus a lab test;
• your browser's developer tools (Network tab), with the cache disabled;
• an independent waterfall tool such as WebPageTest.

Write down two numbers: Time to First Byte (TTFB) and the total page weight.

Step 2: Read TTFB to separate server from front-end problems

TTFB is the time between the browser requesting the page and receiving the first byte of the response. It covers network latency, the TLS handshake and, above all, the time the server spends generating the HTML.

• TTFB is high (consistently above roughly 600–800 ms for an HTML page): the bottleneck is on the server side. Go to step 3.
• TTFB is fine but the page still loads slowly: the bottleneck is the page itself. Go to step 5.

Google's guidance treats a TTFB of 0.8 seconds or less as a reasonable target for most sites.

Step 3: Check whether pages are cached

For a CMS like WordPress, most pages can be served from a full-page cache instead of running PHP and database queries on every visit.

• Look at the response headers in developer tools. Cache plugins and servers usually add a header showing a cache HIT or MISS.
• Load the page twice. If the second load still has a high TTFB, caching is not working.
• Remember that logged-in users, carts and checkouts usually bypass the cache.

Caching layers are explained in website caching explained.

Step 4: Check the hosting account itself

• Resource limits: open the Resource Usage page in cPanel. Frequent CPU, memory or entry-process faults mean the account is being throttled. See hosting resource limits explained.
• PHP version: an old PHP version is slower and unsupported. See which PHP version should your website use.
• Slow database queries: large tables without indexes, bloated WordPress options or huge logs slow every page. See WordPress database optimization.
• Server distance: a server on another continent adds latency to every request.
• Plugins or extensions: disable non-essential plugins on a staging copy to see which one costs the most time.

Step 5: Fix page weight and front-end issues

If TTFB is good but the page is slow, look at what the browser has to download and run:

• Images: the most common culprit. Resize to the displayed size, compress, and use WebP or AVIF. See WordPress image optimization.
• JavaScript: sliders, page builders, chat widgets and tracking scripts block rendering and slow interactions.
• Fonts: several font families and weights add requests; self-host and limit them.
• Third-party embeds: videos, maps and social feeds can be loaded only when needed.
• No browser caching or compression: check that static files are served with cache headers and compressed (gzip or Brotli).

These front-end problems map directly to Core Web Vitals; see Core Web Vitals explained.

Step 6: Look for unusual traffic

A sudden slowdown with no site changes often means bots: aggressive crawlers, scrapers or attacks on login pages. Check access logs or your host's visitor statistics for many requests from a few IPs or user agents, and block or rate-limit them. See brute-force attack prevention.

Step 7: Decide whether the hosting is the problem

The hosting is the bottleneck when, after caching and optimisation:

• uncached TTFB stays high even for simple pages;
• resource limits are hit regularly by legitimate traffic;
• performance varies widely at different times of day for reasons you cannot control.

At that point, a larger plan, cloud hosting or a VPS makes sense. Compare them in shared hosting vs VPS.

Quick diagnosis table

Symptom	Likely cause	First fix
High TTFB on every page	No caching, slow PHP or database, resource limits	Enable page cache, check Resource Usage
High TTFB only for logged-in users	Uncached dynamic pages	Object cache, lighter plugins, more resources
Low TTFB but slow load	Heavy images and scripts	Compress images, defer scripts
Slow only at certain hours	Traffic peaks or scheduled jobs	Reschedule jobs, review limits
Sudden slowdown, no changes	Bots or a compromised site	Check logs, block abusive traffic, scan for malware

Frequently Asked Questions

Will a CDN fix a slow website?

A CDN speeds up delivery of static files and can cache full pages, but it cannot fix slow uncached pages, heavy JavaScript or a slow database.

Is my host slow, or is it WordPress?

Measure TTFB on a simple static file (such as an image or a plain text file) and on a dynamic page. If the static file is fast and the dynamic page is slow, the delay is in your application, plugins or database.

Related reading

For hosting fundamentals, read what is web hosting. WordPress owners should continue with how to speed up a WordPress website.

Sources

• web.dev: Optimize Time to First Byte
• PageSpeed Insights