Different WordPress groups on Facebook have the perfect symbiosis and coordination. This is teamwork. Some “experts” will try to convince you to switch to the “best” shared hosting plan with slow hardware, while others will try to convince you that there is nothing faster and more secure (sic!) than an unmanaged Vultr HF VPS on Cloudways. In both cases, affiliate fees are collected by misleading the unsuspecting public and convincing them to switch to the wrong service provider.
Many users are surprised to learn that there is a third option: Premium Shared Hosting providers with hardware as good or better than unmanaged VPSs. With cPanel, server-level malware protection, and LiteSpeed Enterprise, you get a much more secure experience and faster website loading speed from Premium Shared Hosting. For WooCommerce sites, the benefit is even greater. The best providers may not have an army of affiliate warriors behind them, but that does not mean their services are any less attractive.
You have to consider the hosting configuration based on LiteSpeed WebServer software and SSD disk with a high-speed PCIe socket for Non-Volatile Memory Express interface protocol (NVMe). Such a winning formula boosts about four times the speed of specific internal processes on a server, removing the bottleneck in its performance. Servers with such improved technical specifications will carry heavy traffic with more internal resources and degrade their response time more gracefully. It is not just empty words – sensible shared hosting providers increase fourfold the number of simultaneous entry processes and the disk I/O speed quota when introducing this improved configuration to their offerings.
LiteSpeed Web Enterprise provides additional WordPress Brute Force Attack Protection. A “brute force” login attack is an attack on a website that attempts to gain access to the site by repeatedly guessing the username and password. WordPress is the most popular CMS and, therefore, a frequent target of this type of attack. LiteSpeed protects shared hosting WordPress environments from large-scale brute force attacks that have the potential to bring down entire servers.
Please be aware that any request in WordPress is single-threaded and uses only a single CPU core. The faster the thread, the quicker the PHP request or MySQL query to the database will run. High-frequency CPUs provide the highest single-threaded performance.
If your website requires a high amount of server resources and CPU processing power, you first have to check the number of allocated simultaneous entry processes on your plan. It is as critical as the number of available CPU cores. Of course, it is useful to have more than one CPU core for the busy website with simultaneous concurrent requests coming from different visitors. It is unlikely your case unless you have more than 50,000 clicks per month. Even then, the higher the clock speed of the CPU, the faster your page will be generated.
You will also see increased RAM allocation with the increased number of available CPU cores on a good hosting plan. It is common to have a similar number of GBs of RAM and the number of allocated CPU cores (such as 2GB of RAM and 2 CPU cores). Adding more RAM per CPU will help to serve multiple simultaneous PHP requests. You want to be able to store the entire database of your website in RAM and have extra space in the RAM for the object cache and OPcache. If you keep many domains under your account, then having more RAM could be beneficial. In this case, more RAM is needed to store all databases of different websites.
The number of allowed simultaneous entry processes is the crucial parameter determining the speed of processing the uncashed requests. An entry process allowance is the number of visitors you can serve at the same time when someone is accessing your website. If a user accesses a page of your website, that is a single-entry process. When this exceeds the maximum number of the entry process, you will likely receive an Error 503 when a page is accessed. It usually happens if a long queue is created when many users start accessing your website’s pages simultaneously.
It would be best to have about 16 entry processes per crowded eCommerce website. Your server will cope perfectly fine with delivering cached webpages using just four entry processes. The rule of thumb is to have about 1 CPU core per 15 entry processes. As a result, you have to watch that the number of CPU cores is scaled up sufficiently to reflect the entry processes’ allowance. A modern single logical CPU core on the LiteSpeed Web server should be capable of enduring a continuous load of up to ten HTTP requests per second.
Another issue to check is your Disk I/O speed allowance on the plan. It determines how fast your website and scripts are allowed to perform input/output (I/O) operations per second on your hosting server’s disk when a visitor hits your website. If you are throttled to a low disk I/O speed, your website and scripts will always perform slower. It will not matter how much storage, CPU or RAM you have. Avoid values below 30 MB/s. Even 20 MB/s is too low, and you should push a hosting provider to increase it before signing for their plan – or walk away. The current gold standard in our study is 50 MB/s. About 100 MB/s is the most appropriate value for NVMe SSD storage speed, but hosting providers are too conservative, sometimes incompetent, or just unemphatic to pass the increased speed to their users.
CloudLinux recommends using a speed restriction of 4 MB/s for the I/O speed for the HDD drives. It is shocking to find that another darling of so many WordPress bloggers, A2Hosting, is applying such ancient limits of 4Mb/s on their NVMe servers, two generations apart from HDD technology and 50 times faster. The company is followed by Hostinger, who is offering a terrifying 1 MB/s speed on their Business WordPress plan. Hostinger updated its disk speed to 10 MB/s but only on its most expensive WordPress Pro plan (also traded as Woo Premium and Cloud Business Startup) in August 2021.
LiteSpeed Cache Engine is a built-in feature of LiteSpeed servers; it provides powerful acceleration of dynamic content. An LSCache plugin submits web application rules to LiteSpeed Cache Engine. Cached files are not stored in the WordPress file structure, and the plugin does not execute any of the caching tasks.
LiteSpeed Cache works in a similar way to Varnish. It implements server-side caching. Dynamic content that is not limited to PHP pages is cached by LiteSpeed. Unlike Varnish, LiteSpeed has integrated its Cache Engine into its Web Server, eliminating a layer of reverse proxy. This results in higher efficiency for static content.
If needed, LiteSpeed can store pages in a public cache, a private cache, or it can leave a page uncached. Simple websites often work with public caching only, offering the same cached page to every visitor. If a specific version of a page can be shown to a specific user multiple times as a static page, that page is cached privately. A shopping cart is a classic example of data that should be privately cached. If the response is different each time the page is requested (and therefore cannot be served as a static page to anyone), the page should not be cached.
ESI means that you cache most of the page publicly and add dynamically generated specific content that is different every time the page loads. Most of the HTML, inline scripts, images, etc. remain static, even if several different users access a user-specific page.
An example of this would be a shopping page with a shopping cart widget. The content of the widget needs to be cached privately because it differs from customer to customer, but the rest of the shopping page is the same for everyone. In this case, you would cache the page publicly, while using ESI to cache only the widget privately. The mixed content would be reassembled and delivered together. Using ESI, LiteSpeed Cache Engine can fully serve dynamic web pages from cache without the need for backend server intervention. This way you can serve more eCommerce visitors without increasing CPU resources on your hosting plan.
By combining HTTPS/HTTP2 termination, caching, and web server into a single tool, LiteSpeed offers a higher level of simplicity and ease of maintenance compared to Varnish. Some advanced paid caching plugins can also use ESI markup, but they need to call backend PHP scripts to populate dynamic content. As described in the following section, such calls can be accelerated using Redis or Memcached in combination with OPcache. However, they cannot match the efficiency of LiteSpeed’s server-side caching.
The loading of hybrid ESI dynamic pages is now greatly improved. LiteSpeed Cache 4.0 introduces Guest Mode for WordPress. The site will load quickly on a user’s first visit to improve the Core Web Vitals Score for your complex eCommerce site. Guest Mode allows you to defer decision making for user-specific content and immediately serve a default cached version. For this first visit only, there are no caching variations and no ESI. You do not have to worry about whether the visitor is logged into your site or not.
Such a page loads quickly because the system does not have to spend time processing ESI. It simply finds the “public” page in the cache and serves it. During the HTML loading process, an Ajax call is made. This is the point at which any factors that were ignored are processed and the “correct” version of the page is loaded with ESI for that user.
The LiteSpeed Cache plugin is designed to understand the rules of the app and implement public, private and ESI caching as needed. Hosting providers should enable ESI on their server, but most will do it automatically.
Full automatic ESI integration with WooCommerce is one of the benefits of using LiteSpeed servers. The WooCommerce plugin itself specifies which part of the page is suitable for processing ESI markup, and LiteSpeed takes this into account when generating the page. Most caching plugins for WordPress do not include ESI. With LiteSpeed, you get advanced ESI caching for free, making LiteSpeed webhosts the ideal platform for hosting WooCommerce.
Cloudflare Railgun is not yet compatible with RedHat 8, CentOS 8, AlmaLinux 8, and CloudLinux 8 because Cloudflare has not updated its software. As a result, many providers that offer Railgun will not be able to use it. You are not alone if this story sounds more complicated than switching to LiteSpeed Web Hosting.
Many web designers are not even aware of the role of ESI (Edge Side Includes) in delivering dynamic content. By default, ESI is turned off in LiteSpeed Cache, and only knowledgeable users will implement it on their websites. If you use ESI, you do not have to worry about object caching. However, there may be cases where the ESI approach fails (a good example is BuddyBoss), and you need to revert to the old-fashioned Nginx-era approach, such as using an Object Cache.
Object cache such as Memcached, Redis, or OPcache can be activated, but it is not touched if you use a full page cache such as LSCache with ESI. Hosting providers use LiteSpeed Web Server Enterprise, but smaller private VPS servers often use free OpenLiteSpeed software. Note that it does not provide ESI support unless used with QUIC.cloud CDN. In the end, the page will be served from a CDN node cache instead of OpenLiteSpeed cache, and ESI will work there. If you are not using ESI with LS Cache or using another caching plugin like WP Rocket, you may need Memcached or Redis, and OPcache.
Most cache plugins are automatically considering cart and checkout pages uncacheable. Pages with such private content are dynamically generated each time and served uncached.
For eCommerce WordPress sites with many requests for dynamic HTML pages, adding a persistent object cache like Redis in front of your MySQL database can boost performance and reduce entry processes load. Without a persistent object cache, MySQL database queries will be executed for each request even if the result is identical to a previous query. Redis stores the results of database queries in the RAM, which allows PHP to grab the results of queries that have already been executed. This object caching method allows PHP workers to conserve CPU resources and spend less time fulfilling a request because it removes the need for repetitive database queries.
Memcached or Redis will accelerate typical websites on the fast servers by only 5%, making it a far less critical issue. In contrast, if you are using crap hosting like WPEngine or Raidboxes, you should put more emphasis on the object cache. In fact, Memcached or Redis can disguise your otherwise inefficient performance in accessing the database.
Redis is open-source software that offers various security improvements to its latest versions, including reduced attack surface for hackers, encrypted communication channels, and permissions management. However, by its nature, open-source software like Redis can be configured to use all or none of the available security features. When it comes to using Redis in shared servers, providers should review their security settings and add additional mechanisms.
The main advantage of Redis is that it is best in single-tenant environments, such as when a single website uses an entire VPS or cluster of servers. However, you can use Redis on a shared server if you have confidence in the security team of your hosting provider.
The memory pools of Object Caches such as Redis and Memcached might be shared and there is a high risk of cache poisoning (which is regarded as a security risk) by other users. Object Caches configuration is extremely complex and involves many systems, so it is possible that many hosting providers are using shared pools and advertising Object Caches without the risks being disclosed to the end user.
Before executing a PHP script, the PHP interpreter reads the script from the filesystem, compiles the contents into bytecode, and only then executes the bytecode. OPcache just stores that bytecode in shared memory on the system, and the next request for that specific PHP file (if cached) can skip the reading/parsing/compiling phases, making it significantly faster at the expense of using some shared memory space.
OPcache only stores PHP, not the results of database queries. When you open a WordPress file, you will see many ‘include’ statements followed by a .php filename. When the server parses a PHP script, it includes all PHP scripts mentioned in the include statements into the parent script and then compiles it into bytecode so CPU can read it directly.
Any database query in this PHP file will be executed if the PHP parser uses cached bytecodes. OPcache does not store database query results or data. For this reason, OPcache is safe to use with WooCommerce.
Professional hosting providers rarely use OPcache as their default caching layer. Since no PHP code is executed when serving user requests from the server cache, OPcache has no relevance when serving fully cached static web pages. OPcache might allocate too much RAM to cache precompiled PHP code on a complex eCommerce website. To control the use of RAM, the website owner must be given the freedom to decide whether or not to use OPcache along with Redis or Memcached object caches. Hosting providers who turn on OPCache by default on their servers are aware of the “professional” tests performed by numerous naive and ignorant WordPress bloggers.
PHP 8 will level the playing field. PHP 8 adds a JIT compiler to its core, potentially speeding up performance. The impact on real-world web applications will be small, but most hosting providers will configure JIT properly. JIT will only work if OPcache is enabled. We therefore assume that all hosting accounts will come now with OPcache extensions preconfigured in PHP 8.
Since LSCache prepares the cache of all static resources, it is not necessary to run PHP for static pages and therefore there is no need or benefit from using OPcache for simple static webpages. Using OPcache will be beneficial for a busy eCommerce website. By compiling and caching a PHP script, OPcache improves the performance of any non-cached dynamic page. Combine OPcache with Redis/Memcached for optimal performance when serving dynamic web pages. Small sites can be faster with Memcached. Those that require more resources should use Redis. Currently Redis on shared hosting is insecure, but that will soon change with the new Redis Object Cache module developed by CloudLinux team. OPcache speeds up PHP code performance by caching compiled codes in memory, but it requires more RAM, so you run the risk of hitting resource limits. You can enable OPcache on LiteSpeed server, but in the rare case if you experience problems with RAM, you should disable OPcache.
Consider using BunnyCDN’s geo-replicated Perma Cache for low traffic sites. Your static assets will be delivered via local BunnyCDN PoPs or directly from BunnyCDN storage centers on each continent, in the case of a cold cache in a local PoP. For such brilliant services, you need to pay only about $1 per month. In addition, you need to set up LiteSpeed Cache plugin to have your static HTML files delivered via free QUIC.cloud CDN. In this case, your origin server will be used primarily for editing your website files and occasionally for delivering cached HTML files that have expired on the CDN. Even if you choose a hosting provider with relatively low resource allocation, you can rest easy knowing that your speed score is largely determined by the BunnyCDN and QUIC.cloud CDNs, as well as by the optimisation of all assets by the LiteSpeed Cache plugin.
QUIC.cloud CDN is an essential extension for OpenLiteSpeed. It provides functionality like ESI and the Guest mode at the front-end of a CDN node. LiteSpeed Enterprise implements these things in the back-end of your origin server.
In your hosting provider selection, don’t force yourself to be restricted to using massive hosting corporations aiming to maximise servers for money. Enthusiasts have created many small hosting companies in the UK and USA with the whole idea to be affordable and fast. They aim to monitor the usage and utilise servers below 60% for the peak traffic to provide breathing space for the growing websites. Their technical support team does not treat clients as just records in the Excel spreadsheet. So, if you behave professionally and politely, they will do everything to keep you as a happy customer.
Please be aware of a strategic problem facing the hosting industry. For the last 16 years, it was dominated by the Nginx (pronounced “engine X”), a specialised web server software developed in 2002 by the Russian software developer Igor Sysoev. It is used by about 50,000,000 websites and is very hard to install and configure on the webserver. All important names in the hosting industry became software developers powerhouses tasked to customise and tune the Nginx. They employed many people and were involved in the acquisition spree to develop and customise, further develop, and further customise. Now all these efforts are waisted – LiteSpeed Web Server has vastly outperformed Nginx. About 5,000,000 recent websites use LiteSpeed now, with the tipping point reached somewhere in 2020.
In the last decade, it was indeed tricky to select the best server hosting provider. They all ran the home-tuned customised caching and web server software, and some were indeed better than others. Nowadays, everything is much simpler. If the hosting provider offers standard third-party software on their server, it will be your best choice. We have listed all the essential features in the section above, but let’s summarise them again: CloudLinux CageFS, cPanel, Redis, daily off-site backup using JetBackup, Softaculous, Imunify360 or CXS/ImunifyAV+, ModSecurity, MailChannels, LiteSpeed, MariaDB, Let’s Encrypt SSL Certificate, HTTP/3. This list became an industry standard and significantly simplified setting up and maintaining the hosting server. Unless you are in a charity business, you should run away from any hosting provider who cannot accept a defeat and is still mourning about a decade of development invested in optimising the Nginx server.
The hardware of a server is the main difference between modern hosting providers embracing new software suites. Aim for high speed in CPU, RAM and disk I/O speeds to have web servers that are as speedy as possible. Professional third party software and modern hardware – all you need for your website to run smoothly with nothing slowing it down. It has nothing to do with the name or size of your hosting provider. It’s more about what Intel Xeon, AMD EPYC, AMD Ryzen, NVMe SSDs, or DDR4-3200 RAM hardware they offer to run your processes. Be sure that these days any hosting provider is renting a space for their servers at a reputable Data Center fully integrated into global Internet Exchange Points (IXPs).
Any person capable of installing third-party software on a server will be qualified to set up a web hosting business. He will provide a good uptime as the server health will be monitored by the Data Center. The server will have a professional-grade 1 GBps uplink to the network, and you will measure a very fast time-to-the-first byte (TTFB). Everything will work reasonably well as is expected from the commercial-grade third-party software. The quality of the technical support team is the most difficult issue to evaluate. Try to find reviews of the company. If all reviews are positive, it can be a bad sign. You want to have some real-life reviews rather than the one engineered by the hosting provider himself.
The low threshold of setting up the web hosting business implies a low threshold to winding it down. So, hosting with a new company might be riskier than staying with the established micro-business with about five years of serving clients under their belt.
When websites attract heavy traffic, they overwhelm the provider’s hosting capacity. Adding a CDN service is an excellent way to get your website in front of more people and grow your audience. If you have a website with high traffic, then we recommend giving BunnyCDN a try. It will store a permanent cache of your website’s static files like CSS, JS, and images in its Geo-Replicated Perma-Cache servers. These servers will provide your files to the cache of 30 servers located around the world, shielding your origin from traffic. Your origin server will be left with the task of delivering HTML files to visitors, reducing the bandwidth load at your origin by a minimum of thirty times. BunnyCDN services cost you about $1 per month. It is a much better option than upgrading the level of your subscription with your original hosting provider.
Through our comprehensive solutions, we can help your business from logo designs to designing eCommerce stores. We provide a range of services, including technical SEO and relocation assistance to better web hosting. With our graphic design expertise, we are prepared to meet any other creative need that may arise.
