How to improve website server response speed
Welcome to Gealena Tutorial. reduce server response time. This post discusses how to reduce the server response time of a website server that is deemed not to meet 1 second for mobile and 3 seconds for desktop. In a modern SEO era like this page loading speed is one of the 200 determinants of SEO because it relates to visitor satisfaction levels or user experience.
Website owners out there on average have optimized the response of their website servers. You must immediately optimize your website by reducing server response time. So that it doesn’t fall behind with low authority websites that slowly start adopting SEO standards. Such as using SSL, optimizing page speed mobile-first index, optimizing server response, quality content, etc.
Understanding of server response time speed
The server response speed is the amount of time it takes for the server to respond to a web browser request to display/load a website page to visitors. The web page tries to send a request to the server and the server task fulfills the browser request
It doesn’t matter how light the theme or website page you are optimizing is. If your server response time is slow then user requests will not be fulfilled within the time limit set by Google. The website will be slow to load even though the content elements are a few
To solve the problem of the slow server response, there are 2 ways you can use it
- Learn to use a more efficient hosting service, you can also upgrade the hosting specifications to a higher quality
- Optimizing the website starting from the theme selection, appearance, browser cache, etc.
- Rent hosting on a service that is already professional to minimize website downtime, usually supported by up to 99% uptime, nothing is 100% according to me
Factors affecting the speed of the reduced server response time
- The greater the website traffic, automatically the CPU users also increase so that which affects server performance when responding to page requests.
- Use of resources from plugins, widgets, other effects that require a lot of resources to load, iframes, advertisements, etc.
- Hosting packages, updating from shared hosting use in the congregation to dedicate or VPS helps speed up your server response time. So please upgrade if there is a fee.
- The configuration of the software settings on the server also affects the response time.
Website traffic affects server response
When our website was previously stable with the amount of traffic from 1000 to 2000 suddenly rose by 300%. There was a high use of resource resources depending on the hosting specifications. The server will focus the request to answer the browser and ignore the loading of the page. Even though your website is designed to appear as light as possible if the server is over then requests usually experience a long delay or even down. We often see website owners who are down because they are on Ddos by other parties
The analogy is like in a restaurant, if you order 3 special menus with 10 chefs. Your food will be brought in quickly on the contrary when the number of visitors explodes to 1000 people then you have to wait until your order is ready. As well as website visitors, the difference is only divided by the time for each visitor who is online on our web
To reduce server response time, The solution is not to reduce the number of your visitors, on the contrary. You can increase the number of chefs, or upgrade the hosting specifications to a higher level. So that all visitor requests can be fulfilled, just how to optimize the resources in terms of website page elements.
Full resource usage
Every time we add a resource or element to our website display to visitors, the server takes time to respond to each additional element. So that it can be displayed sequentially according to the instructions on the website. Usually, it has been set which elements should be displayed first and which are displayed later. Usually to play the content need by visitors. It will appear first compare to the ad frame when the page is loaded.
A WordPress website usually uses several stylesheets, scripts, and other resources such as images from within the server.
During the page loading process, there is a back and forth flow from the web browser to the server before all of our website pages display to visitors complete with trinkets.
If your server can serve 100 requests per second. It means that your website can only handle 4 visitors per second if one whole website page requires 25 requests that must be handled immediately.
How do I reduce server page requests? by reducing each element that is displayed to visitors. For example, removing thumbnail snippets on the homepage or removing ads. Which website owners really want to remove their ads because ads are a source of income to extend hosting leases.
Some tips for minimizing website page requests
- Combine multiple CSS files with the same function.
- Using a lazyload script, where page elements will be loaded/processed when a visitor views the page or scrolls the page.
- Using keep alive on a server can make your website pages open more files.
Selection of quality web hosting
We have to make sure the capacity of the website that we buy matches the needs of the website. If the visitors are less than 1000 – 1 GB shared hosting is enough. But if there are more than 30 thousand visitors every day then using a VPS becomes more stable.
Of course, we consider the price of hosting according to the contents of the pocket, if possible, the one that is being promoted is to save money. There is nothing wrong with it, but if visitors slowly start to go up, don’t hesitate to spend additional costs to improve the experience. Don’t let visitors start climbing your website instead. down or slow.
Using a CDN
CDN stands for content delivery network, CDN will store our various content in any part of the world so when a visitor comes from a country. The CDN tries to adjust the content so that it is displayed according to the visitor’s country so requests can be handled faster by the server.
This will help everyone in different parts of the world to access your web pages faster, Because of the closer storage location. So CDN becomes very important for your server response speed if your visitors come from various parts of the world. If visitors only come from Indonesia, just use a local server.
WordPress website or PHP users
Most websites that use PHP are definitely slow to load. We know every PHP has its own function, meaning that the more scripts, the more requests process, and the server slow down.
I often find this on online business websites that use graphic carts or online forms with PHP functions. So make sure every PHP function added to your website pages is important, and not just aggravate the server without providing any benefits at all.
WordPress website users should use the cache on their website. This will lighten the server’s work so that the server response speed can also increase. WordPress website users can use w3 total cache or wp super cache.
The use of cache must be adjusted to the website, if your website only updates content once a week it feels right to optimize cache storage. But if your website is a news model that updates every day you should not use the cache, why?. Some large websites sometimes don’t display the results of the latest posts. Load data according to the last store cache. So that visitors don’t know if there is new content until pressing reset this site in the browser settings, usually, the cache can be set to the normal HTTP protocol interval every 3 days.
Conversely, on online shop websites that use carts, most of the graphics, aka the typography, fail to appear when the cache is activated. So don’t use the cache, maybe it is because the URL is dynamic.
There is 3 server software that I know, LiteSpeed, Apache, and Nginx.
Apache is free and used on many web servers on the internet. It is very easy to use and good documentation too. Many tutorials on the internet assume that you are an apache user because it was used most recently.
Apache isn’t the best in terms of performance, but it has tons of modules and adds one that we can use.
Unfortunately for Apache server response speed problems, including normal, even with the best configuration.
Many website developers like Nginx because it performs better than Apache even with the default configuration. Nginx uses fewer resources so it can handle more traffic than Apache.
There is a free version and there is a paid version. Litespeed works faster than Apache, and luckily LiteSpeed is compatible with apache, so apache users can switch to LiteSpeed very easily. PHP runs faster on LiteSpeed when compared to Apache and Nginx.
In its basic state. Apache can handle 11 requests per second; Nginx handles 12 requests per second, and Litespeed handles 13 requests per second.
But by entering the Cache system, it turns out that Apache and Nginx can only be 3x faster, while LiteSpeed with the cache system can be almost 40x faster. The number of requests can go up to 440 to 500 requests per second.
This is the post about how to optimize server response times. Consider the four points above, starting from the number of visitors that match the hosting specifications. Optimizing page resources to the server software configuration.