{"id":20398,"date":"2026-11-02T12:26:01","date_gmt":"2026-11-02T11:26:01","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/waaruit-bestaat-snelle-wordpress-hosting\/"},"modified":"2026-11-03T14:54:15","modified_gmt":"2026-11-03T13:54:15","slug":"what-does-fast-wordpress-hosting-consist-of","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/waaruit-bestaat-snelle-wordpress-hosting\/","title":{"rendered":"What makes up fast WordPress hosting? NVMe, LiteSpeed, PHP workers, and caching"},"content":{"rendered":"
\"What<\/figure>\n\n\n\n

Every hosting package claims to be fast and throws around terms like NVMe, LiteSpeed, and PHP workers, but rarely explains what they mean for your site. Fast WordPress hosting consists of NVMe storage, a web server with built-in caching like LiteSpeed, sufficient PHP workers and memory per site, an up-to-date PHP version, object caching for the database, and a data center close to your visitors. I\u2019ll walk you through them one by one below, along with how you can check for yourself whether your hosting provider actually delivers on these promises. If you\u2019d like to start with the basics, read What is managed WordPress hosting?<\/a>.<\/p>\n\n\n\n

What makes WordPress hosting fast?<\/h2>\n\n\n\n

Fast WordPress hosting is hosting where the server builds each page quickly or serves it directly from the cache so that it doesn\u2019t need to be built at all. That distinction is the key to everything that follows. WordPress regenerates a page with every visit using PHP and a series of database queries, and every aspect of the hosting determines how fast that happens or how often it\u2019s necessary at all. In the table, you can see what each component does and how to check it.<\/p>\n\n\n\n

Component<\/th>What it does<\/th>How to Check It<\/th><\/tr><\/thead>
NVMe Storage<\/td>Reads files and database records faster than a SATA SSD<\/td>Package Specifications<\/td><\/tr>
Web server with caching<\/td>Serves pre-rendered pages without PHP or a database<\/td>Ask which web server is running<\/td><\/tr>
PHP Workers and Memory<\/td>Process uncached requests simultaneously<\/td>Ask your hosting provider<\/td><\/tr>
PHP Version and OPcache<\/td>Execute the WordPress code faster<\/td>Gereedschap > Sitediagnose<\/strong><\/td><\/tr>
Object caching<\/td>Stores database results in main memory<\/td>Check if Redis is available<\/td><\/tr>
Data Center<\/td>Reduces the round-trip time for each request (latency)<\/td>Ask for the location<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

NVMe storage and a web server with built-in caching<\/h2>\n\n\n\n

NVMe is a storage technology in which the drive is connected directly to the server\u2019s high-speed interface, rather than via the older SATA connection used by a standard SSD. For WordPress, this makes a bigger difference than you might think. For every page, the server reads dozens of small files and database rows, and it\u2019s precisely with those many small read operations that the difference is noticeable. You\u2019ll notice it less with a cached page, but more with a shopping cart. We\u2019ve made that choice ourselves; read Why We've Completely Switched to NVMe<\/a>.<\/p>\n\n\n\n

The web server is the program that accepts and responds to requests from visitors. Apache is the best known and most widely used, but it does not have built-in page caching. NGINX and LiteSpeed are stronger in that regard, and LiteSpeed has server-level page caching that works directly with the plugin LiteSpeed Cache<\/a>. A cached page is like a pre-packed grocery bag. The cashier doesn't have to scan anything\u2014you just hand it to them. PHP and the database aren\u2019t accessed in this case. The most common problem I see is having two caching plugins running at the same time. Choose one caching solution and leave the rest out; otherwise, they\u2019ll interfere with each other. You can find more background information at Types of Caching in WordPress<\/a>.<\/p>\n\n\n\n

PHP workers and memory determine how many visitors can be served at the same time<\/h2>\n\n\n\n

A PHP worker is a process on the server that handles one request at a time that cannot be served from the cache. Think of it like the checkout lanes at a supermarket. If there aren\u2019t enough lanes open, the line grows longer, no matter how fast the cashiers work. If all workers are busy, visitors will have to wait or receive an error message with status code 503. A brochure site hardly notices this, because almost everything is served from the cache. A WooCommerce web shop<\/a> Well, because the shopping cart and checkout are never cached. The same applies to membership sites, sites with many logged-in users, and internal search functions.<\/p>\n\n\n\n

My advice when comparing plans is therefore always the same. Don\u2019t focus on the number of gigabytes of storage, but on PHP workers and the web server. That\u2019s what makes the difference between a fast and a slow online store. The amount of memory allocated per site also matters, because resource-intensive plugins need space to run without error messages. With cheap shared hosting, you often share workers and memory with other sites, and some providers put more sites on a server than it can actually handle (overselling). So be sure to ask about resource isolation\u2014for example, with CloudLinux and CageFS\u2014so that a busy neighboring site doesn\u2019t drag down your site. If you\u2019re running an online store, then there\u2019s also Managed WooCommerce Hosting<\/a> that is designed for that type of traffic.<\/p>\n\n\n\n

An up-to-date version of PHP and object caching<\/h2>\n\n\n\n

A current version of PHP executes the same WordPress code faster and more securely than an older version. There\u2019s another layer beneath that: OPcache stores compiled PHP code in memory, so the server doesn\u2019t have to recompile it with every visit. On a good server, this feature is simply enabled by default. To learn how to safely upgrade to a newer version, read Update PHP Version<\/a>. Keeping the PHP version, plugins, and theme up to date isn't a one-time task\u2014it's part of the WordPress Management<\/a> from your site.<\/p>\n\n\n\n

Object caching is the process of storing the results of database queries in memory, usually using Redis. Where page caching ends\u2014for online stores and logged-in users\u2014object caching takes over. This way, the database doesn\u2019t have to keep answering the same query over and over again. The database itself also plays a role. WordPress recommends MySQL 8.0 or MariaDB 10.11 and higher, and a bloated table wp_options<\/code> slows down every page, regardless of the server. High-traffic online stores that need object caching with Redis choose to use their own resources with us, with managed cloud hosting<\/a>. For more information, see Object Caching and Redis<\/a>.<\/p>\n\n\n\n

Here's how to test if your hosting is fast<\/h2>\n\n\n\n

You can tell if your hosting is fast by measuring the server's response time on actual pages, not by the specifications listed on the pricing page. This is the order I follow myself.<\/p>\n\n\n\n

    \n
  1. Measure the Time to First Byte (TTFB)\u2014the time it takes for the server to return the first byte\u2014in PageSpeed Insights. TTFB isn\u2019t a Core Web Vital, but a slow server will slow down your Largest Contentful Paint (LCP). According to web.dev, 0.8 seconds or less is good, and anything over 1.8 seconds is bad\u2014as a general guideline.<\/li>\n\n
  2. Take multiple measurements on multiple pages of a fully loaded site from a fixed location, and calculate the median. GTmetrix and WebPageTest also work.<\/li>\n\n
  3. Test a page that isn't cached, such as the shopping cart or a page where you're logged in.<\/li>\n\n
  4. Check your PHP version at Gereedschap > Sitediagnose<\/strong> in WordPress.<\/li>\n\n
  5. Ask your hosting provider about the number of PHP workers, the memory allocated per site, and the location of the data center.<\/li>\n<\/ol>\n\n\n\n

    The fastest WordPress hosting doesn\u2019t exist on paper\u2014you have to measure it. What we do as standard at Surver is reflected in that first measurement. Our shared hosting plans run on LiteSpeed servers with NVMe storage and LiteSpeed Cache; OPcache is enabled, and accounts are protected with CloudLinux and CageFS. You can choose the PHP version yourself via cPanel > Select PHP Version<\/strong>, from July 4 through August 5. Redis for object caching is included in Surver Cloud, and our data centers are located within Europe. You can find all the details about the plans on our Managed WordPress Hosting<\/a>.<\/p>\n\n\n\n

    Frequently Asked Questions<\/h2>\n\n\n\n

    How many PHP workers do I need?<\/strong><\/p>\n\n\n\n

    That depends on the number of concurrent requests that aren't cached. A brochure site doesn\u2019t need many, but a busy WooCommerce online store with lots of visitors at checkout needs more. If you see error messages or slow pages during peak traffic while the cache is enabled, ask your hosting provider how many workers you have and whether that\u2019s enough.<\/p>\n\n\n\n

    Does the location of the data center matter?<\/strong><\/p>\n\n\n\n

    Within Europe, the difference for Dutch visitors is minimal, because the distance\u2014and thus the latency\u2014remains low. It\u2019s only when reaching a global audience that distance becomes noticeable, and that\u2019s when a CDN helps. Read When a CDN Is Useful<\/a>. Surver's data centers are located within Europe.<\/p>\n\n\n\n

    Does faster hosting always fix a slow website?<\/strong><\/p>\n\n\n\n

    No. Hosting is the foundation, but a heavy theme, too many plugins, or large images can slow down even the fastest server. Read Why Your WordPress Website Is Slow<\/a> and the guide Making WordPress Faster<\/a>. At Surver, support helps identify where the delay is occurring, and with WordPress Speed Optimization<\/a> we'll tackle the site ourselves.<\/p>","protected":false},"excerpt":{"rendered":"

    Elk hostingpakket noemt zichzelf snel en strooit met termen als NVMe, LiteSpeed en PHP-workers, maar zelden staat erbij wat ze voor jouw site betekenen. Snelle WordPress hosting bestaat uit NVMe-opslag, een webserver met ingebouwde caching zoals LiteSpeed, voldoende PHP-workers en geheugen per site, een actuele PHP-versie, object caching voor de database en een datacenter dicht […]<\/p>\n","protected":false},"author":2,"featured_media":20517,"template":"","kennisbank_categorieen":[52],"class_list":["post-20398","kennisbank","type-kennisbank","status-publish","has-post-thumbnail","hentry","kennisbank_categorieen-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank\/20398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank"}],"about":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/types\/kennisbank"}],"author":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media\/20517"}],"wp:attachment":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media?parent=20398"}],"wp:term":[{"taxonomy":"kennisbank_categorieen","embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank_categorieen?post=20398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}