Redis has long been one of the most admired in-memory databases – fast, flexible, and widely adopted across modern applications. In 2024, however, the company behind Redis moved the project away from its long-standing open source roots, triggering widespread concern in the developer community and sparking forks like Valkey.

In May 2025, Redis reversed course.

The release of Redis 8 introduced a new open source license (AGPLv3), reintegrated Redis Stack features into core Redis, and reaffirmed the company’s commitment to the open source ecosystem.

In this post, we’ll briefly cover what Redis is and why in-memory databases are so useful. Then we’ll walk through the recent licensing changes and what they mean for developers. Finally, we’ll highlight several powerful alternatives you might want to consider, whether you’re sticking with Redis or exploring something new.

What is Redis?

Redis, which stands for Remote Dictionary Server, is an open-source, in-memory data structure store – which means that instead of storing the data on your hard disk, it stores it in the RAM.

It’s primarily used as a database, cache, and message broker, and supports various data structures, including:

• Strings
• Hashes
• Lists, sets
• Sorted sets with range queries
• Bitmaps
• Hyperloglogs
• Geospatial indexes
• Streams

All of which makes it very flexible and versatile for a wide range of applications.

Advantages of In-Memory Databases

If you know a little bit about web applications, you might have already heard of traditional database systems such as MySQL and MariaDB – but what makes in-memory databases special?

1. Speed: In-memory databases use RAM instead of hard disk drives (HDD) or solid-state drives (SSD) to store data, drastically reducing the latency of reading and writing data. Using an in-memory database can deliver extremely fast read and write operations, making them suitable for scenarios where low-latency is critical.
2. Real-Time Analytics: These databases are ideal for applications that process a lot of data, such as advanced planning, simulation, and analytics.
3. Scalability: In-memory databases are simpler to scale up and down compared to other databases, because of how they store data.

Redis Licensing: From Restriction to Open Source Again

In early 2024, Redis changed its license from the permissive BSD license to a dual model: RSALv2 (Redis Source Available License) and SSPLv1. The move was designed to prevent cloud providers from monetizing Redis as a managed service without contributing back.

While the change didn’t affect most users running Redis in their own environments, it had a major impact on providers like AWS, Google Cloud, and DigitalOcean, sparking concerns across the open source community and leading to the launch of Valkey, a fully open fork backed by several tech giants.

In May 2025, Redis responded to this shift by releasing Redis 8 under the OSI-approved AGPLv3 license, re-establishing its open source status. The release also unified Redis Stack features (like JSON, Time Series, and probabilistic data types) into core Redis and delivered major performance improvements.

The licensing reversal signals Redis’ renewed commitment to the open source community, but the landscape has already shifted. Forks like Valkey have gained traction, and many developers are still evaluating which long-term direction best suits their infrastructure and licensing preferences.

Top Alternatives to Redis

If you’re looking for other in-memory database solutions to replace Redis, then we recommend considering the following Redis alternatives.

1. Valkey

Valkey, a fork of Redis, is a new project that aims to resume development of the formerly open-source Redis project. It aims to be a high-performance data structure server primarily serving key/value workloads, hence the name val-key.

The fork was triggered by Redis Labs’ licensing changes, which made Redis incompatible with the standard definition of “open source.” The large cloud vendors had profited from the open source Redis version and, as a result, Valkey is backed by major tech players including AWS, Google, Oracle, and Snap Inc.

Just like Redis, it supports a wide range of native structures, and has an extensible plugin system for adding new data structures and access patterns. However, At the time of writing, Valkey is still not a polished product, and things are evolving. While it serves as a drop-in replacement for Redis, users should be aware of its ongoing development and potential rough edges.

2. Dragonfly DB

Dragonfly is a powerful in-memory data store that offers extreme performance, reliability, and scalability. It is fully compatible with Redis APIs, making it a seamless drop-in replacement for Redis – you can use the same SDKs and tooling without any code changes.

It’s optimized for modern cloud computing, ensuring sub-millisecond reads and real-time experiences for your customers, and claims to deliver 25x more throughput compared to legacy software. Unlike traditional in-memory data stores, Dragonfly makes efficient use of memory during snapshotting which reduces the risk of out-of-memory outages.

A single Dragonfly instance can handle workloads of up to 1TB, which means you no longer need to maintain complex distributed clusters. Additionally, it natively supports an eventually consistent primary-replica model, i.e. if the primary node fails, Dragonfly automatically fails over to the replica.

3. Memcached

Memcached is a free and open-source, high-performance, distributed memory object caching system designed to speed up dynamic web applications by alleviating database load. It’s useful for caching small arbitrary data (such as strings or objects) from database results, API calls, or page rendering.

It follows a Client-Server Architecture where clients are given a list of available Memcached servers, and are then able to choose a server based on the “key.” Servers store values with their keys in an internal hash table, and evict old data (if out of memory) or reuse memory. The server doesn’t care about the data’s structure, it only stores a key, an expiration time, optional flags, and raw (pre-serialized) data.

It’s optimized for speed and lock-friendliness, and therefore queries execute in well under 1ms on slow machines – and serve millions of keys per second on high-end servers. It also uses a least recently used cache by default, i.e., items expire after a specified time, ensuring low latency and efficient memory usage. Its simplicity and efficiency make it a popular choice for caching data.

4. Hazelcast

Hazelcast Platform is a unified real-time data platform that allows companies to take instant action on real-time data. It combines high-performance stream processing capabilities with a built-in fast data store, enabling businesses to automate, streamline, and enhance critical processes and applications.

Hazelcast offers high-speed caching, resulting in improved throughput and lower latency – this allows you to process data quickly and efficiently. It also provides a high-performance, distributed, and parallelized environment that reduces the need for low-level infrastructure management.

5. Key DB

KeyDB is a fully open-source database that serves as a faster drop-in alternative to Redis. It’s backed by Snap Inc., and is designed for scalability and high performance which allows it to handle heavy workloads – benchmarking at over 1 million ops/sec.

KeyDB supports various data structures, including:

• Strings
• Hashes
• Lists
• Sets
• Sorted sets
• Bitmaps
• Hyperloglogs
• Geospatial indexes
• Streams.

To store the data on disk, you can either periodically dump the dataset to disk, or append each command to a disk-based log.

KeyDB scales both vertically (single node) and horizontally (active-replication or sharded cluster-mode) to meet larger workloads. You can set-up active-replica nodes to simplify high availability setups without requiring sentinel nodes for failover. Additionally, its multithreaded architecture outperforms Redis on a per-node basis.

6. MongoDB

MongoDB offers an in-memory storage engine that allows for more predictable latency of database operations by avoiding disk I/O. Unlike other storage engines, the in-memory storage engine doesn’t maintain any on-disk data, including configuration data, indexes, or user credentials, which makes it comparable to other in-memory databases.

To use the in-memory storage engine, you can either specify –storageEngine inMemory as a command-line option, or include the storage.engine: inMemory in the YAML configuration file. Additionally, you need to specify the data directory (–dbpath or storage.dbPath) even though the in-memory storage engine doesn’t write data to the filesystem.

By default, the in-memory storage engine uses 50% of physical RAM minus 1 GB, and if a write operation would exceed the specified memory size, MongoDB throws an error. Since the in-memory storage engine for MongoDB doesn’t persist data after process shutdown, it should only be used for scenarios where data persistence is not required.

7. RethinkDB

RethinkDB is an open-source, JSON database specially built from the ground up for the realtime web with scalability and performance in mind. It has a unique approach where, instead of polling for changes, the developer can configure RethinkDB to continuously push changes and update query results to applications in real-time. This push architecture dramatically reduces the time and effort necessary to build scalable realtime apps.

In RethinkDB, every database process uses memory to store intermediate results and maintain internal state. The memory used varies significantly depending on the type of queries run, and the size of documents stored in the database. However, RethinkDB’s page cache keeps recently used data in memory to minimize disk access.

It’s important to note that RethinkDB can handle databases much larger than the amount of main memory available on a server. However, the management of memory is crucial for the performance of the database and the applications that rely on it. Check out the benchmarks on RethinkDB website to get a better understanding of how performance scales with the hardware.

8. Amazon MemoryDB

Amazon MemoryDB for Redis is a powerful in-memory database service that provides ultra-fast performance and durability for low-latency applications. It maintains compatibility with Redis, allowing you to use the same flexible data structures, APIs, and commands without worrying about the underlying infrastructure.

MemoryDB stores your entire dataset in memory, resulting in microsecond read latency and single-digit millisecond write latency. It is built with enhanced IO Multiplexing to improve throughput and latency at scale that allows it to handle over 13 trillion requests per day, and support peaks of 160 million requests per second.

It also supports horizontally scaling databases by building clusters, or vertically scaling by adjusting the machine type. You can store your data across multiple availability zones for fast failover, and take advantage of its distributed transaction log for data durability, consistency, and recoverability.

9. SAP HANA

SAP HANA (High-performance Analytic Appliance) is a multi-model database that stores data in its memory instead of on a disk. Similar to other databases discussed in this post, HANA offers split-second response times – which is useful for applications requiring fast compute speed and the ability to handle large spikes in traffic.

It supports column-oriented in-memory design which allows running advanced analytics alongside high-speed transactions in a single system. Moreover, it supports both structured and unstructured data, and offers advanced search, analytics, and data integration capabilities.

It is ACID complaint, i.e., one transaction either fails completely or succeeds – there is no-inbetween. You can use it to either host multiple tenant databases in one system to pool resources, or distribute your database across multiple machines in a cluster to scale it up without compromising on security.

Wrapping Up

In this post, we have discussed some of the popular in-memory Redis alternative databases available for building web applications. Each database has its own strengths and weaknesses, so the choice depends on specific use cases and requirements.

Running your own Redis alternative? Don’t let server management slow you down.

If you’re testing or deploying Valkey, Dragonfly, or any other in-memory database, you’re likely juggling SSH sessions, tweaking config files, and firefighting performance issues.

That’s where RunCloud steps in.

With RunCloud, you can:

• Spin up and manage servers on any major provider without touching the command line
  
• Deploy your apps using Git or your workflow of choice
  
• Monitor system resources and process logs with built-in tools
  
• Automate routine tasks like SSL setup, security updates, and backups
  

Whether you’re building side projects or production-grade infrastructure, RunCloud simplifies the entire ops layer – so you can stay focused on your code.

See what server management should feel like. Try RunCloud today

Out of the top one million websites globally, 293,000 are powered by WordPress. And with 500+ new WordPress sites built every single day, it’s fair to say it’s a popular choice as a CMS. In fact, as of July 2023, WordPress holds a 64.2% market share of CMS sites.

One of the factors that makes WordPress such a popular choice is the ability to almost endlessly customize and personalize it, through themes, plugins, and editors.

But this can come at a price, since plugins, themes, and images all consume resources, and this can seriously impact your site’s speed and responsiveness.

And this is bad news for two reasons.

Of course, your user experience is going to rapidly decrease, which will certainly harm your business. But Google’s assessment of your site will also be impacted, with your Core Vitals and Lighthouse score spiraling into the oblivion that is lurking way down in the bowels of the search results pages no one ever finds.

So, what’s the secret to keeping WordPress fast and responsive?

In this article, we’ll reveal the techniques, strategies, and methods you can use to make sure your WordPress site puts performance back at the top of the agenda. We’ll identify the specific factors that affect speed, and exactly how you can optimize your WordPress site to keep both your visitors and the search engines happy.

Ready to supercharge your website? Then, let’s get started!

The Importance of WordPress Speed Optimization

Regardless of whether you have a basic blog or an e-commerce store, it’s essential to pay attention to user experience and loading speed.

How long do you think it takes for a visitor to form an opinion about your website? A minute? 20 seconds? 5 seconds?

In fact it takes the average visitor to make up their mind about a website in just 0.05 seconds. And if your site takes 3 seconds to load, then 40% of visitors will leave. The fact that bounce rates are between 41%-55% is perhaps an indication of either how slow many websites are, or how impatient we as internet users have become.

With 51.3% of traffic now coming from mobile devices, visitors are increasingly looking for information on the fly, and demanding results almost instantly.

Here’s the problem: you may not even consider your website to be especially slow. But those statistics should be enough to make any website owner take notice – and take action. What may have once been considered fast, is no longer acceptable.

Measuring Your WordPress Loading Speed

To truly gaugе thе spееd pеrformancе of your WordPrеss sitе, using a reliable page testing tool is imperative. Thеsе tools not only providе insights into thе actual loading timеs of your sitе, but also offеr invaluable recommendations to help increase your site’s sрееd.

Sеlеcting a Tеsting Tool

Thеrе’s a wide range of frее tеsting tools availablе. Some of the industry favorites include:

WеbPagеTеst: Offers a detailed performance analysis with a visual representation of your site’s loading process.

GTmеtrix: Gives a combined report using Google PagеSpееd Insights and YSlow scorеs, with actionable recommendations.

Googlе PagеSpееd Insights: Dirеctly from thе tеch giant itsеlf, this tool providеs insights into both dеsktop and mobilе vеrsions of your sitе, with suggеstions for improvеmеnts.

Analyzing Your Data with Prеcision

Dеvicе Tеsting

Always ensure you test for both desktop and mobile devices. Thе usеr еxpеriеncе can vastly differ due to variations in both dеvicе responsiveness and іntеrnеt spееds.

Gеographic Rеlеvancе

Choosе tеst locations based on where your core audiеncе is based. If your sitе catеrs to a global audiеncе, use multiplе tеst locations for a better undеrstanding.

Connеction Spееd

Consider testing using various connection speeds, ranging from high-spееd broadband to slowеr connеctions. This gives you insights into thе actual еxpеriеncе of a broader segment of your audience.

Kеy Mеtrics to Focus On

The ultimate goal is to enhance the usеr еxpеriеncе, which is directly linkеd to how quickly thеy can accеss thе primary contеnt. Therefore, an essential mеtric to track is thе Largеst Contеntful Paint (LCP). This measures thе timе taken for the main contеnt of your sitе to bе fully visiblе, giving you an idea of the initial user еxpеriеncе on your site.

In еssеncе, optimizing your WordPrеss sitе’s spееd isn’t just about fast loading timеs – it’s about ensuring a seamless еxpеriеncе for all users, irrespective of their dеvicе, location, or intеrnеt connection.

Read our complete guide on How to Optimize Your Site for Google’s Core Web Vitals to learn more.

How Fast Should Your WordPress Site Load?

You should aim for a loading time of not more than 2.5 seconds, particularly if you’re managing an ecommerce business.

To achieve a faster loading time, pay close attention to the Largest Contentful Paint metric. This is a load speed metric indicating how quickly visible page content can be displayed, even when the website is still loading. Google uses LCP time as one of its major SEO ranking factors, and from this Google directly encourages developers to achieve an average load time of 2.5 seconds or less.

16 Ways To Optimize WordPress Page Load Speed

Sometimes, the changes you make when building a WordPress site directly cause page loading speeds to decrease. Here’s a 16-point checklist that can help you squeeze out every last bit of performance.

#1 – Use A Page Speed Diagnostic Tool

To еnsurе an optimizеd, sеamlеss, and high-performing WordPress wеbsitе, it’s essential to make data-driven decisions. This requires understanding your website’s basеlinе pеrformancе, and thеn carefully and accurately assessing the impact of each change you make. Using a reliable pagе spееd diagnostic tool makes sure that you are able to make the right decisions and take the right action at each step in the process.

Before implеmеnting any optimization stratеgiеs, you must assess your website’s current speed. This initial assessment forms the bedrock, allowing you to gauge thе effectiveness of the changes you make.

While tools such as WеbPagеTеst, GTmеtrix, and Google PagеSpееd Insights are highly recommended, it’s essential to select one that aligns with your spеcific nееds. Consistеncy is crucial: stick with your chosen tool for subsequent assessments to ensure the comparisons are meaningful.

Plugins, thеmе ovеrhauls, and major contеnt rеvamps can dramatically influеncе load timеs. Evеry timе you introducе such changеs, revisit thе diagnostic tool to assess the impact on performance.

The beauty of most modеrn diagnostic tools lies in thеir simplicity. Typically, entering your website’s URL provides you with a whole heap of data points, with clear recommendations that allow you to addrеss any idеntifiеd performance issues.

The addition of new themes or fresh content can also impact your website’s performance. A diagnostic tool provides clear feedback on this by calculating thе anticipated page load time after you’ve finished making the changes.

If your diagnostic tool flags slow loading timеs or othеr pеrformancе mеtrics arе off-kiltеr, taking immediate action is essential. Divе dееply into both thе intеrnal and visiblе parts of your website. Identify the key bottlenecks, and carry out the necessary optimizations to ensure your audience enjoys a seamless browsing еxpеriеncе.

#2 – Choosing Reliable WordPress Hosting

An effective way to improve your page speed is to choose a reliable and high-performing WordPress hosting company. You’ll need either to sign up or secure a subscription plan to help you manage your WordPress site. There are three popular types of WordPress hosting available – shared hosting, DIY-VPS, and managed hosting. Your final choice will depend on your budget, the comprehensiveness of the hosting service, and the customer care experience.

Shared hosting is often the initial choice for start-up WordPress developers, or those with limited resources. While you can save a lot from low-priced subscription packages, you will eventually experience inevitable problems in the future, since you’re sharing the server space with other paying subscribers. As a result, you may encounter 500 errors, suspensions or – even worse – page downtime, all because the hosting company has to set certain limitations on their resources. Aside from slowness and overcrowding issues, you may also encounter hidden charges related to migration, SSL certificates, and domain registration.

In a DIY-VPS hosting, referred to as Do-it-yourself on Virtual Private Server, you can optimize and manage data without too much restriction. You can directly rent servers from cloud providers such as UpCloud, Vultr, and Hetzner to host your website. With the help of tools such as RunCloud, you don’t even need to have server management skills, because RunCloud makes managing your server very easy.

With managed hosting, you can rent your own server, and manage your data without sharing the server with other site owners. The hosting company will handle all of the backend server-related work, since they only deploy service professionals assigned to handle all your CMS needs. Popular examples of managed hosting businesses include Kinsta, WP Engine, Pressidium, Flywheel, Pressable, and Media Temple.

#3 – Deleting Unnecessary Plugins, Themes and Media Files

Ensuring your WordPress sitе operates efficiently oftеn involves decluttering unnecessary components. Rеdundant plugins, thеmеs, and mеdia filеs, even when inactive, can reduce your site’s speed and reliability by consuming precious sеrvеr space. To remove these unnecessary files, follow the following steps:

❌ Plugins:

Navigatе to ‘Plugins’, dеactivatе thе unwantеd onеs, thеn dеlеtе these from the inactive list.

❌ Thеmеs:

Undеr ‘Appеarancе’, identify and dеlеtе unwanted thеmеs, keeping both your active theme, and a default theme (just in case your main theme ever develops a problem).

❌ Mеdia Filеs:

Visit ‘Mеdia Library‘, usе the ‘Unattachеd’ filtеr, and rеmovе unusеd filеs.

Optionally, you can choose to usе the Media Cleaner plugin for automating this kind of clean-up.

It’s important to be proactive when it comes to keeping your WordPres site lean and efficient. Make sure you periodically assess every plugin and thеmе, and check your media files. This practice of carrying out a rеgular audit and cleanup guarantees better site performance – and a morе sеcurе website too.

#4 – Using A Content Delivery Network

Using a Contеnt Dеlivеry Nеtwork (CDN) can greatly improve your WordPrеss site’s loading time by caching its contеnt across a global nеtwork of sеrvеrs. This means that when a visitor accеssеs assеts from your sitе, the request is met by a geographically nearby еdgе sеrvеr, rathеr than taxing your main sеrvеr. This enables a quicker information exchange – and improved loading speed.

Among thе wide range of CDN providеrs, Cloudflarе has carved out a reputation for reliability and efficiency, becoming a prеfеrrеd choicе for a large number of web developers. It offers a range of plans and services, each offering various features and capabilities.

Onе standout sеrvicе from Cloudflarе is thе Automatic Platform Optimization (APO) sеrvicе, which substantially improves WordPrеss sitе pеrformancе by caching both static and dynamic contеnt at Cloudflare’s еdgе sеrvеrs. This reduces the burden on origin servers, making sure that both images and dynamically generated pages are sеrvеd rapidly, improving the usеr еxpеriеncе.

Cloudflarе’s Pro Plan delivers additional pеrks, such as enhanced security via Web Application Firewall (WAF), optimized delivery through features such as Polish and Mirage, and round-thе-clock customеr support – making it a comprehensive solution for businesses with a larger wеb prеsеncе.

It’s essential to considеr thе diffеrеncеs when optimizing various typеs of wеbsitеs, from simplistic brochure sitеs to complex ecommerce platforms. For simple, largely static sitеs, Cloudflarе provides full-pagе caching, allowing thе entire sitе to be cached and delivered directly from its еdgе sеrvеrs worldwidе. This makes sure that visitors receive a fast delivery of content, improving the user experience.

In contrast, еcommеrcе websites represent a more complex challenge due to their transactional nature, and thе necessity for real-time data processing, such as order processing and user account management. Cloudflarе addresses this increased complеxity by providing a range of configurations, enabling developers to cachе contеnt that is static, whilе also еnsuring that dynamic contеnt (such as shopping carts and usеr profilеs) is served in real-time – all without impacting on either the usеr еxpеriеncе or data accuracy.

#5 – Clear Out Your Database

Your WordPrеss sitе’s databasе is used to store your contеnt, sеttings, and plugins. As you carry out content revisions, plugin installations, and updatеs, your WordPress site gradually accumulates resources on the server. Whenever a visitor carries out a search query, accesses a resource, or downloads a file, the server has to keep diving into the database to access the necessary information. If the database is cluttered, this will require additional processing time, slowing down the user’s experience.

In some cases it’s even possible that, where multiple revisions of old posts are carried out, new resources on the server are built on existing resources, and eventually this progressive build up of changes, updates, and modifications clutters the database, and slows the whole site down.

To restore your sitе’s loading speed to pre-clutter speeds, carrying out regular databasе clеansing is essential. Ensure you completely remove unused files, spam commеnts, and old rеvisions. You can manually clеar out such unwanted data entries via PhpMyAdmin, although this will require a certain level of technical knowledge in order to avoid impacting the site, or even taking it down.

If you’d rather not risk using PhpMyAdmin then you could consider using plugins that are designed to streamline this process. Plugins such as Advancеd Data Clеanеr, WP-Optimizе, and WP Sweep are popular choices for removing old, redundant data from servers, helping to improve the efficiency of the database, and thereby boost the site’s speed and responsiveness.

#6 – Enable Caching

If you’re using a Content Delivery Network (CDN), it will automatically cache the static assets on your site such as images and CSS files. However, you can take this one step further by enabling both object caching and full-page-caching in WordPress.

Page caching is the process of storing the HTML code of a page in a cache, and is essential to maintain the speed performance of your WordPress site – especially if you’re serving a lot of traffic.

Whenever a visitor submits a search query or requests a file download, the server needs to assemble the entire page from scratch using PHP, and this involves retrieving the information in your database before the finished HTML page can be delivered to the visitor’s browser. Regardless of whether your WordPress site needs to build one page or simultaneous pages, page caching will definitely help improve your page speed.

Read our in-depth article on How To Use Redis Full-Page Caching To Speed Up WordPress and Redis Full-Page Cache vs. NGINX FastCGI Caching to understand how caching works, and which caching option is right for you.

Once you enable Redis caching, you can either check the HTTP headers of your site, or use tools such as Browser Caching Checker to evaluate the cache settings of your site.

You can also check the cache headers via the DevTools menu – just go to the Network tab and right-click, then in the menu that appears, find “Response Headers”, and make sure “Cache Control” is enabled. This will add a new column to your screen that will display the cache headers for all requests.

#7 – Consider Using Lazy-Loading On Long Pages

If your homepage is long and contains a lot of images, you should definitely consider lazy-loading images. This optimization method allows you to load some visible content, but temporarily delays the loading of content appearing in the bottom portion of the page. This is very helpful for when visitors have a slow bandwidth.

Many WordPress themes automatically add lazy loading to images – check the documentation of your theme to find out how to enable it. If your theme doesn’t add lazy loading functionality, you can use plugins such as Lazy Load Image Filter to add this functionality to your site.

#8 – Optimizing JavaScript And CSS

When you use a page testing tool, you’ll likely encounter recommendations that suggest you should remove JavaScript. When you use popular tools such as Pingdom or WebPageTest, you will notice the number of JavaScript files before you reach the “Start Render” line. This enables your WordPress site to perform necessary tasks such as launching a pop-up, or rotating images in a slideshow.

But these actions won’t load until the entire content is completely loaded. In order for the loading time to not slow down, you need to temporarily delay the JS files with the help of plugins such as WP Critical CSS.

Minification is another popular optimization technique used to speed up your WordPress platform. This involves reducing the file size of HTML, CSs and JS code, since they can consume valuable database resources over time.

For example, you can minify CSS codes by eliminating line breaks, white spaces, excess characters, and unnecessary comments. CSS Compressor is a popular choice for simplifying CSS code, and is readily accessible from hosting providers. Use tools such as CSS Delivery Test to quickly find out if your WordPress theme compresses CSS.

You can also use Tree shaking algorithms to reduce the size of your JavaScript files. However, this is only useful if you have the source code of the JavaScript file.

You can also combine CSS files to reduce the number of separate HTTP requests, and make information transfer more efficient. Consider using performance plugins such as Autoptimize or WP Rocket to perform the necessary optimization process.

The end goal of minification is to reduce the amount of data that needs to be transferred, and help speed up file movement within the website.

#9 – Choosing Lightweight WordPress Theme

The choice of your WordPress theme really matters when it comes to customer engagement and traffic generation. However, you can’t ignore that themes also accumulate database resources over time.

Although it might be tempting to have an endless selection of Google fonts, icons, sliders and parallax scripts, most websites won’t use all these features.

It might be a better idea to use a lightweight theme and build-off from that. Some examples of lightweight options include GeneratePress, OceanWP and Astra – all of which will allow you to preview your work before publication.

As a precaution, take note regarding the page builder plugins which come as part of theme brands, such as OceanWP and Astra, especially if you will access their theme library. A theme library often consumes additional resources as developers need to generate corresponding CSS and JS files for page builders to work on your site. For every theme you explore, make sure to run a page test to find out if any changes will have a significant effect on loading speed.

#10 – Controlling Your Blog Feeds

If you have a homepage that you use for blog feeds, consider reducing thumbnails and other media icons to speed up the loading time, even though the homepage is one of the most valuable pages of your website. The page loading becomes more efficient when the site processes fewer requests.

#11 – Compress Images

Image compression is one of the easiest WordPress optimization methods you can use. Research has found that over 34% of the total page weight is generated by images. Large images especially tend to slow down your site, which may result in poor user experience and high bounce rate.

To combat this, you can compress images to reduce the file size, while keeping the balance between quality and compression rate in check. You can use popular image editing tools such as Adobe Photoshop or Affinity Photo, or you can use WordPress plugins such as Optimole, Imagify and WP Smush that automatically do this for you.

However, if you compress your images too much, they won’t look as good on big screens. When formatting the images, experiment a little to find the right balance between quality and the lowest compression rate. A generally acceptable file size may range somewhere between 100 and 200KB. You can use tools such as Image Delivery Test to assess the images on your site.

We also recommend you explore newer encoding formats such as WebP and Avif to encode your media files. These newer formats provide better compression, while maintaining the same quality. However, some older browsers don’t support these, so your visitors might have a hard time browsing your site.

You can also compress your HTML, JavaScript, and CSS files during transmission to save bandwidth and reduce the load times. GZIP compression can greatly reduce the size of your website’s files and speed up your website’s load times. This is enabled by default on most web servers – you can check the HTTP headers of your site, or use tools such as GZIP Compression Test to know if your site does employ this.

#12 – Paginate The Comments

When a WordPress site displays hundreds of comments, it shows that the page is highly interactive and engaging. Unfortunately, when excessive comments are displayed on a page, it hurts the page loading speed.

Breaking the comment section into multiple pages is recommended, especially if the older comments don’t provide any value to the visitor. This will reduce the memory consumption and improve the loading time. To do this, go to your WordPress Admin dashboard, click on Settings, look for Discussions, and then select Break comments into pages, before setting up the maximum number of comments per page.

#13 – Disabling Trackbacks and Pingbacks

While receiving trackbacks and pingbacks is an indication that a blog or external website has linked to you, this may take up memory resources and fill your page with additional spam and irrelevant queries later on.

To turn this off, go to Settings, look for Discussion, and then disable link notifications from other blogs to stop receiving pingbacks. You can use plugins such as No Self Pings, which is a free plugin that disables self-generated pingbacks.

You should also reduce the number of redirects on your website. Redirects can slow down your website by adding additional HTTP requests. Minimize the number of redirects on your website, and use 301 redirects instead of 302 redirects wherever possible.

#14 – Clearing Out Old Posts

WordPress enables you to draft and revise your content when you need to release an updated version. Rolling back to your previous posts becomes easier, since all published posts are usually stored on the platform. However, for every revision you make on each post, you will need a corresponding space on the server – something you need to pay attention to once the loading speed of your site has slowed down.

You can limit the number of revisions you can make per post. Consider releasing a new post once you have reached a set number of revisions, and then delete the old post. Access the wp-config.php file and add the following code to set the number of revisions to 10:

define ('WP_POST_REVISIONS', 10); 

#15 – Use A Transactional Email Service

If you need to send emails, using your own server may seem like a cost-effective option, but it can have serious consequences on email deliverability. WordPress servers are not designed for mass email sending, and their IP addresses can easily get blacklisted by email providers if they aren’t configured correctly. This can lead to emails being marked as spam – or not delivered at all.

Moreover, sending emails from your own server can also impact the performance of your website or application. Sending large volumes of emails can consume significant server resources, which can slow down your website or even crash it during peak periods.

By using a transactional email delivery service, businesses can take advantage of specialized infrastructure and expertise to handle email sending reliably and efficiently. Using an email service also ensures that your emails are delivered promptly, and provides insights on user interactions.

Read our in-depth research on the best and most reliable transactional email services to find out which one suits your needs best.

#16 – Identify Performance Bottlenecks

If you’re looking to squeeze out every last bit of performance from your server, then you need to identify and resolve performance bottlenecks. Here are three key methods for identifying performance bottlenecks:

1. Using Infrastructure Monitoring: You can monitor your server infrastructure and keep an eye on resource usage to identify what can be improved. We recommend using New Relic, a popular application performance monitoring (APM) tool that can help you identify performance bottlenecks on your WordPress site. You can use it to get real-time insights into your site’s performance which can help you identify slow queries, memory usage, and other performance metrics.
2. Using the Query Monitor plugin: Query Monitor is a popular WordPress plugin that provides a detailed overview of your site’s database queries, hooks, HTTP requests, and other important performance metrics. This plugin can help you pin-point slow queries and other bottlenecks that are affecting your site’s performance.
3. Check error logs: WordPress logs errors and warnings to a debug log file. By enabling WP_DEBUG mode, you can see these errors and warnings on your site’s front end or by checking the debug log file. This can help you identify any coding or configuration issues that are impacting your site’s performance.

Benchmark Performance to Quantify Improvements

Performance testing is an essential step in identifying issues and improving the speed and overall performance of your website. You should avoid making changes blindly without first understanding their impact on your site’s performance. While some changes, such as adding caching or switching to a different web server, may have a positive impact on your site’s performance, others may have no effect – or even a negative impact.

By conducting performance tests, you can benchmark the current state of your site and measure the impact of any changes you make. Here are two key steps to consider when conducting performance tests:

1. Establish a baseline: Before making any changes, it’s important to establish a baseline for your site’s current performance. This can be done using either simple tools such as Google PageSpeed Insights or more specialized tools such as Loader.io and Grafana k6.
2. Test before and after changes: Whenever you make changes to your site, run the performance tests again. It’s important to conduct performance tests before and after the changes – this will help you determine whether the changes made a positive or negative impact on your site’s performance.

Performance Difference Between OpenLiteSpeed and NGINX

OpenLiteSpeed and NGINX are both popular web servers that can be used to run WordPress websites, and in terms of WordPress performance and speed, both are highly capable servers.

OpenLiteSpeed is designed to handle a large number of concurrent connections with low resource consumption. It uses an event-driven architecture that allows it to handle thousands of simultaneous connections without consuming excessive server resources.

On the other hand, NGINX is also a highly performant web server that is used by many websites worldwide. It is known for its ability to handle high traffic loads with low resource consumption.

We compared OpenLiteSpeed and NGINX in real world settings, which you can read about in our report, “OpenLiteSpeed vs. NGINX vs. Apache – Which is the Fastest Web Server?”. In general, our results showed that both OpenLiteSpeed and NGINX are equally performant when caching is enabled.

Conclusion

Optimizing your WordPress site for speed is crucial for providing a better user experience and improving search engine rankings. This guide has provided valuable insights on how to optimize your site for speed, including using a fast web host, optimizing images, using a content delivery network, and reducing the number of redirects.

To make server management easier and more efficient, we highly recommend using RunCloud (yep, that’s us!), a server management tool that offers features such as caching, SSL certificates, and automated backups. By using RunCloud, you can optimize your site for speed while minimizing the time and effort needed to manage your server.

RunCloud is built for developers that want to focus on shipping great work, not on managing their infrastructure.

RunCloud provides you with one-click WordPress installations and painless server configuration, so you don’t need to spend hours figuring it out. Get started with RunCloud today & get up and running in minutes.

Facing technical glitches like the dreaded HTTP Error 503 Service Unavailable can be frustrating, disrupting the seamless flow of online activities.

In this comprehensive guide, we delve into effective solutions to tackle this issue head-on. From understanding the root causes to implementing step-by-step fixes, empower yourself with the knowledge to swiftly resolve the HTTP Error 503 and ensure uninterrupted access to your online services.

Let’s dive in and conquer this challenge together!

What is HTTP Error 503 Service Unavailable?

HTTP Error 503, also known as ‘Service Unavailable,’ indicates that a website cannot be reached at the moment. This error is part of the HTTP status code family, specifically within the 5xx range, which denotes server-side errors.

It means that the server is temporarily unable to handle requests, and it is commonly caused by server overloads, maintenance activities, or other temporary disruptions in the server’s operation, such as misconfiguration in the firewall or an unsuccessful backup.

If you visit a website and see this error, then there isn’t much you can do apart from notifying the server administrator.

Web servers are complex systems, and there are a number of things that need to function exactly how they are supposed to in order for it to work. Let’s see some of the common reasons for HTTP 503 errors.

Suggested Reading: How To Fix the WordPress HTTP 500 Internal Server Error (Easy)

What Causes HTTP Error 503 Service Unavailable?

1. High Hosting Server Resources Overload

One of the primary culprits is server overload, a situation that arises when a server’s resources are stretched to their limits, often due to unforeseen traffic spikes or malicious DDoS attacks, thereby causing a service disruption.

2. During Server Maintenance & Upgrades

Another common cause is server maintenance, a necessary but disruptive process that can temporarily take a server offline. If the website administrator is upgrading the servers or applying a security patch, then this can inadvertently trigger a 503 error for the duration of the maintenance.

3. Coding Syntax Issues in .htaccess File

Syntax issues, particularly errors in the .htaccess file, can also cause HTTP errors and cause your WordPress website to become unavailable. If you recently edited a configuration file, then you might have placed an extra character somewhere where it was not supposed to be.

If you edit files via SSH, we recommend you read our post on how to edit files via Nano.

4. Poorly Configured DNS of your Website

DNS configuration problems are another potential source of 503 service unavailable errors. The DNS, or Domain Name System, is responsible for converting website addresses into the corresponding IP addresses.

If you have recently edited your DNS records, or if you are using a dynamic IP address for your website, then it’s possible that your website is pointing to someone else’s server – and since your website is not hosted on that server, it is showing an error.

5. Database Connectivity Issues due to Misconfiguration

Database connectivity issues can prevent basic tasks such as logging in to the dashboard and fetching information about products, leading to website unavailability. It is essential to monitor and maintain database connectivity to ensure seamless website functionality and user experience.

6. Poorly Configured wp-config.php File

Misconfiguration in the wp-config.php file can cause WordPress and WooCommerce to throw HTTP 503 errors because this file contains essential settings for the WordPress installation.

To understand more about this critical configuration file and how to fix common issues, check out this comprehensive guide: Everything You Need To Know About wp-config.php.

How to Fix HTTP 503 Service Unavailable Error?

As noted above, there are many reasons for the service unavailable error. Here are the recommended steps that you can take to try to fix 503 Server error:

Method 1. Check Your Server’s Resource Usage

If you are constantly receiving high traffic, then your server might crash and become unavailable. We recommend you monitor your server’s resource usage to ensure it’s not being overwhelmed, and vertically scale your server if necessary.

Method 2. Check for Ongoing Maintenance Or Upgrade Running

If your server is showing an HTTP 503 error, then it is possible that the server is being updated in the background. If this disruption is caused by an automatic update, then it usually resolves itself within a couple of minutes. But if you want to, you can update your WordPress manually.

Method 3. Verify for High Resources Consuming Active Processes

If there are a lot of background tasks on your server, then terminating some of the processes can relieve an overwhelmed server.

Method 4. Reset Your Server, Network, or Web Application Firewall

Incorrect firewall configurations or proxy settings can cause 503 errors. If you recently edited some firewall settings, then you should revert them and see if that fixes the issue.

If you don’t want such a headache in the future, you will be pleased to know RunCloud provides an easy-to-use firewall with an intuitive graphical user interface that automatically blocks threats.

Method 5. Check Website Server Logs and Amend the Fixes

Server logs can provide valuable insights into what’s causing the error. Read your HTTP access logs to quickly detect and fix programming errors that might be causing the outage.

The exact steps vary for each tech stack, but if you’re using RunCloud, you can check logs directly from the dashboard.

Also Read: What Are Linux Logs? What Are They & How To Use Them

Method 6. Verify Your Domain’s DNS Records

If your domain name is pointing to an incorrect IP address, then you might get service unavailable error messages. If you’re not using RunCloud’s automatic DNS functionality, then double check your DNS records and update records as necessary.

Method 7. Restart Your Server and Networking Equipment

Sometimes, gremlins cause a server crash. If you can’t find any explanation for your server crash, then a simple restart of your server and networking equipment can resolve the issue.

Read Further:

• How to Fix the 504 Gateway Timeout Error
• How to Fix a 502 Bad Gateway Error

Wrapping Up

Dealing with an HTTP 503 error and other server-related issues can be quite technical and may require a good understanding of server management. However, RunCloud can greatly simplify this process while still providing full control over your servers.

RunCloud offers an intuitive dashboard that allows you to manage your servers efficiently, set up error reporting, and resolve common errors like 502 and 503 with ease.

Whether you’re a seasoned developer or just starting out, RunCloud can help you streamline your server management tasks, so you can focus more on development and less on maintenance. 🚀

Start using RunCloud today!

Frequently Asked Questions on HTTP Error 503 Service Unavailable

If you have a server in the cloud, then the only way to connect to it is via an SSH connection. But occasionally, if you mistakenly mistype your password, or simply forget it, then the login process may result in a “Too Many Authentication Failures” error.

If this happens to you then – don’t worry! In this post we will discuss different ways to avoid this problem in the future.

Let’s get started!

What are “Too Many Authentication Failures”?

If you make multiple consecutive login attempts on your server, either using a wrong password or an SSH key, then you are likely to see the following error message:

Received disconnect from host: 2: Too many authentication failures for root

”Too many authentication failures” is an error message commonly encountered in SSH (Secure Shell) services. This is a security measure to prevent unauthorized access and prevent bots from repeatedly spamming your server.

3 Ways to Fix Too Many Authentication Failures

In this section, we will explain how using SSH keys can help in avoiding the “Too many authentication failures” error, but before we start, make sure that you have added the public SSH key on your server.

 If you are using RunCloud, you can configure SSH using our intuitive web interface.

Method 1: Use SSH Key with Command Line

A quick and easy way to avoid authentication failures is by using an SSH key and specifying the path of this SSH identity file directly in the login command to avoid any ambiguity.

By doing so, you bypass the SSH agent and force the use of the specified key, which can help resolve connection issues related to key confusion or agent problems.

Here’s how you can do it:

1. Restrict the Permissions for SSH key: Before using the identity file, make sure it has the correct permissions set. This can be done with the following command:

chmod 600 /path/to/your/identity_file

This command restricts the file so that only the owner can read and write to it, which is the recommended setting for SSH keys.

2. Specify Identity File in SSH Command: When connecting to the server, you can specify the identity file using the -i option in the SSH command:

ssh -i /path/to/your/identity_file username@hostname

Replace /path/to/your/identity_file with the actual path to your SSH private key, username with your username, and hostname with the server’s hostname or IP address.

Method 2: Use Unique SSH Key for Each Server (Recommended)

As we have discussed in our SSH service hardening guide, it is recommended to use a different key when connecting to different servers via SSH. Using a unique SSH key for each server can prevent cross-contamination between servers, and reduce the risk of accidentally leaking credentials for all the servers.

If you are using RunCloud, you can easily add a unique SSH key for each user account on your server using the “SSH” tab in your server settings page.

When using a new key for each server, it can be difficult to determine which key belongs to which server. To solve this problem, you can specify the keys in the ~/.ssh/config file on your local machine along with other necessary information.

Here’s how you can manage multiple connections by specifying an identity file and username for each server:

Open the ssh configuration file (located at ~/.ssh/config) on your local machine in a text editor. You can use any text editor such as notepad, VS code, or even a CLI-based editor such as nano. In that file, paste the following example:

# Server 1
Host server1
    HostName server1.example.com
    User myuser1
    IdentityFile ~/.ssh/id_rsa_server1

# Server 2
Host server2
    HostName server2.example.com
    User myuser2
    IdentityFile ~/.ssh/id_rsa_server2

In the configuration above, Host is an alias for the server, HostName is the actual hostname or IP address, User is the username for the SSH connection, and IdentityFile is the path to the private key file used for authentication.

Edit the example configuration and replace the dummy values with the actual values – the values for hostname, user, and identifyFile will be their respective values, but you can set the Host variable to anything descriptive.

In the above example, we have added a server in our configuration file and named it server1. To connect to this server we can simply specify its name in the SSH command, and your computer will automatically use the correct credentials for logging in.

ssh server1

In the above example, server1 is the name of the server that we specified in the configuration file.

This is the recommended way to do this, because by using the config file you streamline the process of connecting to various servers, making it more efficient and less prone to mistakes. System administrators and developers who frequently access multiple servers prefer this technique for the following reasons:

1. Simplified Connection Commands: Instead of typing long SSH commands with usernames and key paths, you can connect to a server with a simple ssh server1 command.
2. Organized Credentials: Each server has its own entry, making it easy to manage different usernames and keys for each connection.
3. Enhanced Security: By using unique keys for each server, you reduce the risk of a compromised key affecting multiple servers.
4. Automated Connection Parameters: The SSH client automatically uses the correct username and key when connecting, reducing the chance of errors.
5. Ease of Maintenance: Updating a server’s credentials or connection details is as simple as editing the corresponding entry in the config file.

Suggested read: Why Authentication Using SSH Public Key is Better than Using Password and How Do They Work? 

Method 3: Increase MaxAuthTries in SSH

Although you shouldn’t need to, you can optionally choose to change the number of allowed failed attempts by modifying the MaxAuthTries variable in the server configuration.

Here are the step-by-step instructions to increase the MaxAuthTries value in the SSH daemon configuration:

1. First, you need to connect to the server with the necessary privileges.
2. On the server, open the SSH daemon configuration file located at /etc/ssh/sshd_config with a text editor of your choice. You will need superuser privileges to edit this file. For example, you can use nano:

sudo nano /etc/ssh/sshd_config

1. Next, you need to locate the MaxAuthTries directive. If it’s commented out (preceded by a #), you will need to uncomment it by removing the #.
2. Change the value of MaxAuthTries to a number that suits your needs. The default is usually 6. Increasing it allows more authentication attempts before disconnecting.

MaxAuthTries 10

1. Save the Configuration File. After making the changes, save the file and exit the text editor. In nano, you can do this by pressing CTRL + X, then Y to confirm, and Enter to save.
2. Restart the SSH Service Apply the changes by restarting the SSH service. The command to restart the service may vary depending on your system’s init system. Here are two common methods:

#Using systemctl command
sudo systemctl restart sshd
#Using service command
sudo service sshd restart

By following these steps, you will have successfully increased the MaxAuthTries value, allowing more authentication attempts and potentially resolving issues with multiple keys in your SSH agent. Remember to use this setting judiciously, as allowing too many authentication attempts can be a security risk.

Although this method works well for most people, if you want additional security and flexibility, we recommend configuring Fail2ban to automatically block IP addresses which repeatedly login using incorrect credentials.

Wrapping Up

Navigating the complexities of server management and SSH authentication can be daunting. By implementing the methods outlined in this article, you can effectively resolve the “Too many authentication failures for user root” error, and streamline your server management process.

After setting up the SSH authentication, you can start using your server and perform simple actions such as editing files via nano or transferring files via SFTP. Or if you are feeling adventurous, you can perform some advanced tasks such as finding large directories and files in Linux, Copying Files in Linux, or master the echo command.

A secure and efficient server setup is crucial for smoothly managing web applications, but you don’t need to be a Linux expert anymore to deploy websites on the internet.

With RunCloud, you can effortlessly control your server environment, allowing you to focus on building your application without the backend worries. And if you ever encounter any server issues, our professional technical team is always ready to assist you.

Join RunCloud today and experience the peace of mind that comes with one-click web application installations.