Short answer: a website is usually not slow because the server is too weak. It is slow because it does too much work on every visit, and does it too far from the user. That is why moving the same site to more expensive hosting often delivers less than the salesperson promises - and sometimes delivers nothing.
The three things that really determine speed
1. Distance
A server in Warsaw answers a user in Gdynia within tens of milliseconds. The same user in Berlin gets an answer more slowly, in New York slower still, because the data physically has to travel there and back. No faster processor fixes that.
The solution is an edge network: the site is served from the node closest to the user. Cloudflare has over three hundred such locations. For a company operating locally that sounds like overkill - until a customer from abroad turns up, or Google starts checking the site from another continent.
2. How much work the server does on every visit
This is the most common cause. A typical WordPress site with a dozen or more plugins runs the PHP code of every one of them on each visit and performs anywhere from dozens to hundreds of database queries. Before the first byte of the page appears, time passes that no pretty animation can hide.
That is why caching can work wonders: suddenly the same site serves a ready-made file instead of recalculating everything. And that is also why caching is sometimes a plaster on a broken leg - it works right up until the content changes.
3. How much code lands in the browser
This is the stage the user sees. A 4 MB photo uploaded straight from a camera, three animation libraries, a slider, a counter, a chat widget, two analytics systems and a webfont loaded from an external server - the browser has to download, process and draw all of it. A phone on LTE does that several times more slowly than your office computer.
What the PageSpeed numbers mean
Google measures three things from a human's perspective, not the server's:
| Metric | What it measures | In plain terms |
|---|---|---|
| LCP | time until the largest element appears | "when do I see that the page has loaded" |
| CLS | layout shifts during loading | "does the content jump under my finger" |
| INP | response time to a tap | "does the page react when I poke it" |
Plus TTFB - time to first byte, meaning how long before the server starts answering at all. That is the metric an edge network improves, and the one neither a new theme nor lighter images will fix.
How it looks with me
The page you are reading runs on the same engine as the NEO sites I build for clients. The current PageSpeed measurement for itama.pl: 99 for performance and 100 points each for accessibility, best practices and SEO, with three out of three Core Web Vitals passed.
I am not writing this for praise, but because whoever builds websites should be able to show the score of their own site. It is the one performance portfolio that cannot be touched up in Photoshop. If somebody is selling you "lightning-fast websites", measure theirs - it takes thirty seconds.
What that score actually comes from: rendering at the network edge instead of on a single server, a handful of database queries instead of hundreds through a plugin layer, images in modern formats, fonts served from our own domain and preloaded, and the absence of a framework the browser would have to boot up just to draw text.
What changing hosting will not fix
- 4 MB photos - the same file downloads just as slowly from any server,
- twenty plugins - they travel with the site,
- a full-width carousel loaded ahead of the content,
- third-party scripts - chat, pixels, maps, review widgets; each one is somebody else's server in your loading path,
- no caching for static files - if the browser downloads the same fonts and images from scratch every time, that is not a server power problem, it is configuration.
Where to start if your site is slow
- Measure it: PageSpeed Insights, the score for mobile, not desktop. The mobile version is the one most people see.
- Check the largest photo on the home page. If it weighs more than 300 KB, you have your first thing to fix.
- Count the third-party scripts. Every one removed is a real gain.
- Check the TTFB. Above 600 ms the problem is on the server side, and then - only then - a conversation about hosting makes sense.
Would rather not deal with this? Send me your website address. I will send back a measurement and a list of the three things that will help most in your case - ordered by the size of the gain. I charge nothing for the check.
Frequently asked questions
Does a faster site really increase sales? Speed does not sell by itself, but a slow site costs you: some people leave before they see anything. It hurts most on a phone, away from Wi-Fi.
Do I need a score of 100? No. What counts is passing Core Web Vitals and opening quickly on a phone. The final PageSpeed points are often cosmetic.
I have WordPress - can it be sped up? Usually yes, and considerably: caching, image compression, removing unnecessary plugins and scripts. It will not turn into a static site, but the difference can be twofold.
Is hosting in Poland faster for Polish customers? For the server itself, yes - it is close. An edge network, though, delivers the same locally and additionally works for users outside the country.