ENHEIT

payless.host

How much of a slow site is the host's fault

Updated Nov 22, 2026

Where slowness actually lives

A hosting provider can make a site slow. So can an unoptimised theme, a misconfigured plugin, or an image library that has never been compressed. Before moving to a faster host, it is worth knowing which one is causing the problem.

Step one: test the server response time

Go to a tool like Byte Check or WebPageTest and run a test against your site's homepage. Look for the metric labelled Time to First Byte, or TTFB. This measures how long the server takes to start responding, before any page content is sent.

A TTFB below 600 milliseconds is fine. Between 600ms and one second suggests the server is working harder than it should. Anything consistently over a second points to the host.

What can go wrong: cached pages show a faster TTFB than logged-in pages. Run the test multiple times, and test a page that is not your homepage if you suspect caching is hiding the real figure.

How to check it worked: the tool should show a waterfall chart with TTFB clearly labelled. If no such label appears, try a different testing service.

Step two: disable plugins and switch theme

Deactivate all plugins. If the site becomes noticeably faster, turn them back on one at a time until the slowness returns. That plugin is the bottleneck.

Switch to a default WordPress theme — Twenty Twenty-Four or similar. If speed improves, the theme was the problem. Managed WordPress hosts like DreamPress from DreamHost often run performance optimisations that make a badly-coded theme less of a liability, but they cannot eliminate the problem entirely.

What can go wrong: deactivating a plugin can break parts of the site. Make a backup first, or test in a staging environment if your host provides one.

How to check it worked: the homepage should load. If it does not, reactivate everything and try fewer plugins at once.

Step three: check image sizes

View the page source and find the largest image file. Download it and check the file size. Anything over 500KB is slowing the page down, and the host is not responsible.

Compress images before uploading. A 3000-pixel-wide photograph displayed at 800 pixels on the page is waste. The hosting server still has to send the full file.

What can go wrong: some themes resize images on upload. Check the actual file being served, not the one you uploaded.

How to check it worked: in Chrome, right-click the page, select Inspect, go to the Network tab, reload the page, and sort by size. The images should appear smaller than before.

Step four: test from multiple locations

A site that is fast in London and slow in Sydney may be hosted on a server located in Europe with no CDN. Geographic distance matters. Shared hosts like Hatchling from HostGator typically place your site on a single server in one region, while more expensive plans often include content delivery.

Use a service that tests from multiple locations. If TTFB is low in one region and high everywhere else, the problem is where the server sits, not how powerful it is.

What can go wrong: testing tools sometimes route through VPNs or data centres that do not reflect real visitor experience. Cross-check with a second tool.

How to check it worked: results should show different response times from different cities. If every location returns identical figures, the test may not be using real geographic endpoints.

Step five: isolate database queries

Install Query Monitor, a free plugin. Load a slow page while logged in. Query Monitor will show every database query the page makes, how long each one took, and which plugin or theme file called it.

Look for duplicate queries or queries taking over 100 milliseconds. These indicate inefficient code. Hosting with more RAM or CPU will make slow queries faster, but fixing the query is usually cheaper than upgrading the server.

What can go wrong: Query Monitor itself uses resources. On a very slow site, the plugin may time out or make the page unloadable. Test on a staging copy if the live site is barely functional.

How to check it worked: a table of queries should appear at the bottom of the page, sorted by execution time. If nothing appears, check that you are logged in as an administrator.

What this tells you

If TTFB is high, images are optimised, plugins are minimal, and database queries are efficient, the host is the bottleneck. If TTFB is low but the page still loads slowly, the problem is in the page itself. Both can be true, but only one of them costs money to fix.

The providers in this article