WordPress hosting
We run your site on fast servers in the EU/EEA and keep an eye on it around the clock.
client.noAll up- Location
- EU/EEA
- Container
- Isolated, own IP
- PHP
- 8.4
- Redis
- 94% hits
- Cloudflare
- 86% from cache
- Backup
- Last night 02:00
- Uptime, last 30 days
- 99.98%
- Median response
- 140 ms
- Other sites on the server
- 0
When shared hostingis no longer enough
Many Norwegian businesses keep their WordPress site on a shared hosting plan for NOK 49–199 a month. It's cheap, and for many sites it works fine. The downside is that you share the server with others and have little control over how it's set up.
IP 185.62.•••.40Running normallyBlocklisted- client.noyou
- webshop-•••.no13:05 traffic spike
- blog-•••.no13:40 hacked
- accounts-•••.no
- salon-•••.no
- Response time
- 0.4 s3.1 s
- Email from client.no
- DeliveredBounced
- Warning from the host
- NoneNone
On shared hosting, hundreds of websites run on the same server and share one IP address. If one of the other sites gets a lot of traffic, yours can slow down. If one of them is hacked, the IP address can end up on blacklists, and you may not be told.
For a simple site or a hobby blog, that's fine. If the site matters for sales, downtime and slow pages soon cost more than you save on hosting.
- Restore from backup, from the Pro tier
- <10min
- Agreed uptime
- 99.9%
- Other sites on your server
- 0
- Automated monitoring
- 24/7
The technology behind our WordPress hosting
We set up hosting for each client based on traffic and integrations, so there's no ready-made package to buy. These parts are included in every setup.
Caching at Cloudflare
Images, stylesheets and scripts are served from the Cloudflare server closest to each visitor. Pages for visitors who aren't logged in are kept ready-built, so WordPress doesn't have to build them again for every page view.
Redis for caching and queues
Redis is a database that holds data in memory. It keeps answers from the main database, so WordPress doesn't have to ask MySQL the same thing repeatedly. Shopping baskets and logins are stored there too, and Redis takes care of email, scheduled jobs and syncing with your ERP system in the background.
Traefik spreads the traffic
Traefik spreads visitors across several copies of the site and handles SSL certificates automatically through Let's Encrypt. When we publish a new version, we move traffic across to it gradually, so the site stays up throughout.
Daily backups
We take a daily copy of the whole environment, including the database. With an operations agreement from the Pro tier, we also practise restoring regularly, and setting up a working environment from a backup takes under ten minutes. If nobody has restored from a backup, you can't be sure it works.
Tell us about your site, and we'll suggest a setup and give you a specific price.
How cachingspeeds up WordPress
On standard WordPress hosting, every page is built from scratch for every visitor: WordPress starts, the plugins load and the database gets the same questions again. The next visitor goes through the same steps.
client.no/logo.svg12 msFrom Cloudflare in OsloCloudflare/services/38 msReady-built pagePage cache/basket/160 ms41 of 44 queries from RedisWordPress and RedisWe put three layers of caching in front of WordPress. Images, stylesheets and scripts come from the Cloudflare server closest to the visitor. Pages for visitors who aren't logged in sit ready-built in a page cache. Whatever has to be built per visitor, such as the basket, gets its database answers from Redis, which keeps them in memory.
When someone publishes or edits a page, the page cache clears itself, so visitors see the change straight away.
What the setup means in practice
Ready-built pages from the cache
On shared hosting, the server typically takes 200–300 ms before it starts sending the page. A page from the cache goes out without WordPress starting at all. Visitors notice the difference, and Google takes speed into account when ranking pages.
Automatic HTTPS
SSL certificates renew automatically through Let's Encrypt, so there's no manual renewal to keep track of.
Handling traffic spikes
When traffic increases, the server starts more copies of the site automatically. Traefik spreads visitors across them, so none of them gets overloaded. That lets the site handle more traffic, for example during a sale.
Updates without downtime
We can publish new code in the middle of the working day. The old version keeps running until the new one has been checked, so customers don't notice any interruption.
Shared hosting and PXL compared
When load time goes from 1 to 3 seconds, the probability that a visitor leaves the page rises by 32% [1]. Hosting is only one part of load time, but it affects every page.
Monitoring that alertsthe developers directly
Without monitoring, it's often a customer who spots the downtime first. If the site is down for long, or it happens repeatedly over a few weeks, Google can also start dropping pages from its search results.
We measure uptime and response times around the clock, and alerts go straight to the developers who run your site. How quickly we respond depends on the response time in your SLA.
We run everything ourselves, from the server to WordPress. That means we can follow a fault all the way from the server to WordPress, without waiting for another supplier.
client.noOngoingResolved- Home page returns error 500Monitoring checks the site every minute
- Alert sent by SMS and Slack54 seconds after the site went down
- A senior developer has the caseEnterprise: within 30 minutes, at night too
- Cause: the database stopped respondingEvery connection was in use
- Database restartedCache cleared and warmed up again
- The site responds again33 minutes of downtime, report sent at 08:00
Updates are testedbefore they are published
The test environment is a copy of the site where updates are tested before visitors see them. There, automated tests check contact forms and checkout, and screenshots are compared to catch layouts that have shifted without anyone asking for it. Only updates that pass every check go further.
When an update is published, the new version starts next to the old one, and traffic moves across gradually once the new version responds as it should. That's why we can update during the day, without a maintenance window at night.
woocommerce 9.4.1 → 9.4.2RunningPassed- Backup of production
- Copy to stagingPHP 8.4, same database
wp plugin update woocommerce- Contact form sent
- Checkout with a test card
- Login and My account
- Tripletex integration
- Screenshots compared32 pages
- Deployed through CI/CD
Shared hosting, managed WordPress hosting and PXL compared
| Shared hosting | Managed hosting | PXLFor businesses | |
|---|---|---|---|
| Server | Shared with many others | Dedicated | Isolated container |
| PHP | Often an older version | 8.x | 8.4 |
| Caching | A plugin, if you install one | Page cache | Cloudflare, page cache and Redis |
| SSL | Manual | Included | Renewed automatically |
| Backup | Unknown | Daily | Daily, tested, encrypted |
| Test environment | No | Some | Yes, with automated tests |
| Monitoring | No | Basic | Around the clock, with alerts |
| SLA | No | Generic | Agreed response time |
Security in the infrastructure itself
Around 90% of hacked CMS sites run WordPress. That says more about how those sites are run than about WordPress. The cause is usually outdated versions on shared servers with no firewall in front.
Firewall in front of WordPress
The firewall stops common attacks, such as attempts to send malicious code to the database or the browser, before they reach WordPress. It's part of the server setup and doesn't depend on a plugin that can be switched off or go out of date.
Isolated containers
Your site runs in its own container, a separate environment with its own resources and its own IP address. If another site gets a traffic spike or is hacked, yours isn't affected.
DDoS protection
Attacks that try to overwhelm the site with large amounts of traffic are stopped before they reach WordPress. Traefik also limits how many requests a single sender can make.
Encrypted backups
The daily copies are encrypted and stored in several geographic locations. With an operations agreement from the Pro tier, we restore from them on a fixed schedule, so the backups have been tested before you need them.
What does WordPress hosting cost?
You can find WordPress hosting from NOK 49 a month. At that price you share a server with many others, get no SLA and do your own troubleshooting. The table shows what you get at each price level.
Shared hosting
FromNOK 49–199
Shared server, shared IP, no SLA, troubleshooting left to you
Simple hosting with PXL
FromNOK 500
Redis, a page cache and daily backups, with no SLA or operations. You keep WordPress updated yourself
Operations with SLA
FromNOK 2,500
Monitoring, updates and an agreed response time. Firewall and tested backups from the Pro tier
WordPress hosting for Norwegian businesses
GDPR and data storage
All data is stored in the EU/EEA, spread across several locations. We transfer nothing to the US without a data processing agreement in place. That makes it easier for you to document that your data storage meets GDPR.
Support in Norwegian
You speak Norwegian with the developers who run the server. They set up your environment, so you don't have to explain the issue to a support desk that doesn't know your setup.
Integrations Norwegian businesses rely on
Integrations with Vipps (Norway's mobile payment app), BankID, Tripletex and Altinn depend on a server that responds quickly and reliably. If it responds too slowly, a payment can time out and fail.
Accessibility
Accessibility is mostly about content and code, but slow loading makes a site harder to use for everyone. Fast hosting doesn't replace accessibility work, but it makes it easier.
Signs you've outgrown your WordPress hosting
Shared hosting is the right choice for many sites. These signs suggest it's no longer right for yours:
At that point, moving to another shared host rarely helps. Read more about our WordPress platform.
- Response times stay above 2 seconds, even though you've tried plugins meant to make the site faster
- The site slows down or goes down when traffic rises, for example during a campaign
- Troubleshooting takes time that should go on content
- You need to document where personal data is stored to comply with GDPR
- Integrations with Tripletex or HubSpot can't cope with unstable hosting
- Your hosting provider's support can't help when the problem is in the server setup
Seven questions to ask before choosing WordPress hosting
- Does the server run a PHP version that still gets security fixes?
- Do you get your own IP address, or do you share one with hundreds of other sites?
- Is there a test environment, or are updates tested on the live site?
- What was the actual uptime over the last 12 months? "Guaranteed 99.9%" means little until someone can document it
- Who notices when the server is struggling at 3 a.m., and what do they do then?
- Are backups taken daily, and has anyone tried restoring from one?
- Can new code be published without downtime, or are files still uploaded by hand?
Tell us how much traffic your site gets and which integrations it uses, and we'll suggest a setup.
Frequently asked questions
Can I move my WordPress site to PXL without downtime?
Yes. During the move the site runs on both platforms until everything has been checked on the new one. We copy the database, move images and other files, and test payments and forms on a copy. Only when the new platform responds correctly do we change DNS, which controls where your domain points, and move the traffic across. Visitors shouldn't notice the move at all.
Do all WordPress plugins work on your hosting?
With very few exceptions, yes. The server runs standard PHP 8.4, so WordPress, themes and plugins work as they would on any other setup. The exceptions are older plugins that don't support PHP 8.4. We review your plugin list before the move, find any such cases in the test environment and fix them there.
What happens if my site goes down?
Our monitoring sends an alert automatically to the developers who run the platform. They respond within the response time in your SLA. At the lowest level that applies during working hours, and with the Enterprise agreement it's 30 minutes, outside working hours too. Because we run everything from the server to WordPress, we can follow the fault all the way without waiting for another supplier. Afterwards we tell you what happened and what we did.
Does the hosting include an SSL certificate?
Yes. The server fetches and renews Let's Encrypt certificates automatically. You don't need to track expiry dates, and visitors won't see browser warnings because someone forgot a renewal. It costs nothing extra and needs nothing from you. If you need certificates for several domains or subdomains, we set them up the same way.
What's the difference between hosting and a maintenance agreement?
Hosting is the server and infrastructure your site runs on: PHP, Redis, caching, firewall, backups and monitoring. The maintenance agreement covers the WordPress installation itself, with plugin and core updates, security testing and small improvements along the way. Hosting keeps the server running, and maintenance keeps the software updated and secure. With both, all the day-to-day running of the site is covered.
Can I use your hosting if you didn't build my site?
Yes, but we do a technical review first. A site with more than 20 plugins and a heavy page builder often gains less from caching than one that's built cleanly. We'd rather say so upfront than promise a speed-up that doesn't happen. In the review we look at the plugin list, the size of the database and how the theme is built, and you get an honest assessment of what you'd gain by moving. If the site needs tidying up first, we'll suggest it, but the decision is yours.
Where are the servers located?
In the EU/EEA, spread across several locations, so an incident in one location doesn't take your data with it. Your data stays within the EU/EEA, so the hosting itself involves no transfer outside the EEA. We transfer nothing to the US without a data processing agreement. If you need it for your own documentation, we'll tell you which data centres we use.
What does WordPress hosting at PXL cost?
Simple hosting starts at NOK 500 a month. You get the same server setup with Redis, a page cache and daily backups, but no SLA, and you keep WordPress updated yourself. Operations with an SLA start at NOK 2,500 a month and include monitoring, updates and an agreed response time during the day. A firewall and tested backups are included from the Pro tier at NOK 5,500. The price depends on your traffic and how many integrations you have, so we set it after a short review. Our pricing overview shows what each tier includes.
Talk to us about WordPress hosting
Tell us briefly about your site. You'll get an honest assessment of the infrastructure you need, and whether your current hosting is good enough.