Does hosting actually affect site speed?

Yes, hosting affects site speed, but only the part of it that happens on the server — and for most sites, that is a smaller share of total load time than the page itself. A slow server adds delay to every single request; a heavy, badly optimised page adds delay regardless of how fast the server underneath it is. Both matter, and confusing which one you actually have leads to spending money on the wrong fix.

What hosting genuinely controls

The server side of the equation is real, and it comes down to how quickly your hosting can execute code, query a database, and start sending a response — measured as server response time. Storage speed matters here too: NVMe storage, standard on plans here, reads and writes data faster than older mechanical or even standard SSD storage, which shortens the part of a request that involves reading files or database records from disk. NVMe and SSD storage: what the difference means covers why that matters mechanically.

Shared resource limits matter too. An account regularly hitting CPU, memory or process limits shown in your control panel's usage panel will respond more slowly under normal load, and considerably worse under any spike — that is a genuine hosting constraint, not a front-end problem.

What hosting does not control

Everything that happens after the first byte arrives is decided by the page itself, not by the server that sent it:

• Image weight. An unoptimised, oversized image takes just as long to download on a high-end server as on a modest one — the file is the same size either way.
• JavaScript execution. A script that takes a while to run does so in the visitor's browser, on the visitor's device. The server has already finished its part by the time this happens.
• Layout shift. Content jumping around while it loads is a markup and CSS issue — missing width and height attributes, fonts without a reserved fallback — with nothing to do with the server at all.
• Number of requests. A page loading forty separate small files makes the same forty requests whether the server is fast or slow; hosting changes how quickly each one is answered, not how many there are.

How to tell which one you actually have

The most reliable check: compare a simple, mostly static page on your site against a complex, database-driven one. If both are slow to first byte roughly equally, the cause is upstream of any individual page's content — genuinely the server or something running on every request. If only the complex page is slow, or if TTFB is fast but the overall load time is still poor, the cause sits in that specific page's content, not the hosting underneath it. Why your website is slow, and how to find out walks through this properly with a full diagnostic method.

When hosting genuinely is the answer

Real signals worth taking to a hosting review: server response time that is consistently poor on simple, already-cached pages; an account regularly at or near its resource limits during normal traffic, not just during a spike; or a site that has grown substantially in visitors or content since the plan was chosen. How to tell when you have outgrown your plan covers these signals properly. Outside of those, the higher-value work for most sites is still in the page itself — compressing images, cutting unnecessary scripts, and caching what does not need to be regenerated on every visit.