A good shared plan is enough for an ordinary company site, a VPS starts to make sense only with a store or heavy traffic, and you buy managed hosting when you want the technical work off your plate. WordPress hosting is simply space on a server where the site files and the database live, plus a set of specs that decide how fast it runs and how easily you keep control of it. The difference between a cheap plan and a good one is usually a few dozen zloty a month and a second of load time.
Below I break the three hosting types down, show the specs worth looking at, and name the slogans from provider offers that you are paying for without reason.
Three types of hosting - how they differ
Shared hosting is one server split between many customers. You pay little because you share the cost with the neighbours - but you also share the power with them. A VPS is a carved-out slice of a server just for you, with guaranteed resources and full control. Managed WordPress hosting is shared or VPS with service on top: updates, backups, caching, support that actually knows WordPress.
| Type | Who it is for | Who handles the technical side | Rough monthly cost (Polish market rates) |
|---|---|---|---|
| Shared | company site, blog, one-pager, small store | you or whoever maintains your site | from around a dozen to several dozen PLN net |
| Managed WordPress | a company with no in-house IT, a store with steady traffic | the hosting provider | from several dozen to several hundred PLN net |
| VPS | a store, integrations, several sites at once, unusual requirements | you or your developer | from a few dozen PLN net upwards |
I give these as rough brackets, because hosting price lists change several times a year and first-year promotional prices can be three times lower than the renewal. Always check the renewal figure, not the one on the banner.
How to choose - the decision in three questions
You do not need to compare twenty offers. Three questions are enough:
- Does the site take orders or payments? If yes, the cheapest shelf is out. A store makes far more database queries than a brochure site, and it is the first thing to choke.
- Does anyone on your side handle updates and backups? If there is no such person, take managed hosting or add ongoing technical care on top of a regular plan. Hosting on its own watches nobody.
- Does the site fall over when traffic goes up? If yes, the problem is resources, and then a VPS or a stronger plan will genuinely change something.
Default recommendation: company site - good shared hosting with NVMe and PHP 8.2+. Store - managed WordPress or a VPS. The rest is fine-tuning.
The specs that actually matter
This is the list of things that really affect speed and peace of mind. The rest of the provider’s comparison table is decoration.
| Spec | What to look for | Why it matters |
|---|---|---|
| Drives | NVMe or SSD | HDD under WordPress is a relic today, the difference is noticeable |
| PHP version | 8.2 or 8.3, switchable | older PHP is slower and stops getting patches |
| PHP limits | memory at least 256 MB, max_execution_time at least 60 s | product imports and updates hit lower limits and fail |
| Database | MySQL 8 or MariaDB 10.6+ | a store lives on database queries |
| Backups | daily, kept at least 14 days, with self-service restore | a backup you cannot restore is not a backup |
| SSL certificate | free Let’s Encrypt included, auto-renewed | no SSL means a browser warning and a real drop in trust |
| Staging | one-click staging environment | lets you test updates away from the live site |
| Server location | Poland or the EU when your customers are in Poland | shorter response time, GDPR without gymnastics |
| Support | chat or phone, response times in writing | at three in the morning on Black Friday that is the only thing that counts |
If an offer says nothing about the PHP version or the limits, write and ask before you buy. The answer (or the lack of one) tells you a lot about the level of support.
What you are overpaying for
A few slogans from hosting offers sound serious and change nothing for a company site:
- Unlimited transfer and unlimited space - a typical company site uses a fraction of even a modest limit. That is marketing, not an advantage.
- Built-in site builder - with WordPress you will never open it once.
- Free domains in the bundle - a domain costs a few dozen zloty a year, that is not an argument when picking a server.
- A paid SSL certificate - for an ordinary site, free Let’s Encrypt is technically just as secure; I laid out the differences in the piece on a free or paid SSL certificate.
- The cheapest plan with a first-year promotion - multiply the renewal price by three years, and only then compare.
A separate category is free hosting or hosting for a few zloty. You can put a site on it, but it usually ends in ads, no backups and slow response times - I went into that at length in the piece on cheap and free WordPress hosting.
Polish or foreign hosting
If your customers are in Poland, a server in Poland or in the EU is more practical. The gain in response time is real, if small, and support in Polish plus a clean VAT invoice matter more. With foreign providers you also get the question of where your customers’ personal data physically sits - with an EU server you simply do not have to deal with it.
Foreign hosting makes sense when you sell outside Poland or need a service that is not available locally.
When hosting really is the culprit, and when it is not
Changing hosting only helps when hosting is the bottleneck. The simplest test: open the site at peak hours and compare with late evening. If the difference is large, it is resources. If the site loads slowly always, the same at ten in the morning as at one at night, the blame sits with images, the theme and plugins, not the server.
The typical breakdown of causes behind a slow WordPress looks like this:
- Images at their original size - the most common and cheapest cause to fix
- A heavy theme with a page builder layered on top - a lot of code on every single page
- Too many plugins doing the same thing - each one adds database queries
- No caching - the page is assembled from scratch on every visit
- Only then hosting - weak resources, old PHP, an overloaded shared server
How to measure this on your own site I show step by step in the speed mini audit. It is worth running before you move - so you know whether the migration will change anything.
Hosting for a store is a different conversation
A WooCommerce store has different requirements than a company site: the cart and the customer account cannot be cached, so every such visit genuinely loads the server. On top of that come integrations, stock synchronisation and invoicing. With a store I look straight away at a stronger plan, higher PHP limits and separate resources for the database - I took that subject further in the piece on hosting for a WooCommerce store.
Before you move the site
Migration between hosts is a reversible operation, as long as you do it in the right order and start from a backup you can genuinely restore the site from:
- A full backup of files and database, downloaded to your own drive - not just held at the provider
- A copy on the new server, running on a temporary address and verified
- A test of the key paths: contact form, login, and for a store a full test order
- Shortening the DNS time-to-live a day earlier, so the switch goes through quickly
- Switching the domain, with the old hosting kept for another week as a fallback
- Checking SSL and redirects after the switch
How this looks when I do it with a client
I start with a free diagnosis: I check what is actually slowing the site down and tell you straight whether moving will change anything, or whether the problem sits in the theme and the images. It often ends with the hosting staying exactly where it is while we tidy up the site itself - cheaper and more effective.
When a migration does make sense, I move the site together with its configuration, certificate and mail, with a test before the domain switch - for stores I do it in the lowest-traffic window. For bigger clean-ups, where hosting is only one element, we move into development and optimisation, and you get the scope and the amount in writing before we start. Fixed-price projects usually land in the range of around 5,000-10,000 PLN net (Polish market rates), and ongoing technical care starts from 1,000 PLN net per month.
Frequently asked questions
Which WordPress hosting is the best? There is no single best one for everybody. For a company site, decent shared hosting with NVMe drives, PHP 8.2 or newer and daily backups is enough. For a store or a high-traffic site, managed WordPress hosting or a VPS with guaranteed resources is better.
Will a VPS speed up my site? Only if server resources are the bottleneck. If the site is slow because of unoptimised images, a heavy theme and a surplus of plugins, it will be exactly as slow on a VPS, only more expensive. Start with a measurement, then decide about moving.
How much should good WordPress hosting cost? A sensible plan for a company site is usually from a dozen to several dozen PLN net per month, and correspondingly more for a store (Polish market rates). Price lists change often, so compare renewal figures rather than promotional first-year prices.
Does managed hosting free me from looking after the site? Partly. The provider handles the server, the backups and usually WordPress core updates, but nobody there will check whether your form or checkout still works after a plugin update. The site itself remains the responsibility of the owner or whoever maintains it.
Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.