How to Reduce Server Response Time in Wordpress or Blogspot (TTFB)
Server response time is one of criteria on blog loading speed issue in Google PageSpeed Insights. And another name of this problem is the Reduce Server Response Time.
 |
| Google Source Image |
The Server itself has many meanings, which are ranging from domains, blog resources, to the hosting that we use. So, the server response time means that how long the response time / overall loading of our blog or website.
Google PageSpeed Insights will judge a blog which has a slow server response time if the response time exceeds 200 billion, while the 200 millisecond is equal to 0.2 seconds.
This suggests that Google is very attentive to the loading of a blog and the convenience of its users.
If you still have the subdomain such as Blogspot from blogger.com, I'm not surprised if you get this problem, because the blog that has been used for a long time but you do not buy the domain itself.
If you do not believe, please check the loading speed of big and famous blogs that still use the blogspot domain in Google PageSpeed Insights. Most of them definitely get this problem.
One drawback of this problem is the loading of a blog that is getting longer (not heavy), because the old server is just being responded. When usually load time a blog is 3 seconds (load blog) + 200 milliseconds (load server), then it could be 3 seconds + 2 seconds, so the total to 5 seconds to full load a blog.
It is not very felt for you who have a laptops / handphones that has great specifications. But for those who access it on laptops / mobile phones that are low-spec, they will be very disturbed on this situations.
Then Why?
It could be that their laptops or mobile phones lag while loading process. Because as I've read on an online book about computers, there is mentioned that the Web browser takes up a lot of RAM uses, most of the time when the Web / blog that is opened has a slow server response.
Google PageSpeed Insights will judge a blog which has a slow server response time if the response time exceeds 200 billion, while the 200 millisecond is equal to 0.2 seconds.
This suggests that Google is very attentive to the loading of a blog and the convenience of its users.
If you still have the subdomain such as Blogspot from blogger.com, I'm not surprised if you get this problem, because the blog that has been used for a long time but you do not buy the domain itself.
If you do not believe, please check the loading speed of big and famous blogs that still use the blogspot domain in Google PageSpeed Insights. Most of them definitely get this problem.
One drawback of this problem is the loading of a blog that is getting longer (not heavy), because the old server is just being responded. When usually load time a blog is 3 seconds (load blog) + 200 milliseconds (load server), then it could be 3 seconds + 2 seconds, so the total to 5 seconds to full load a blog.
It is not very felt for you who have a laptops / handphones that has great specifications. But for those who access it on laptops / mobile phones that are low-spec, they will be very disturbed on this situations.
Then Why?
It could be that their laptops or mobile phones lag while loading process. Because as I've read on an online book about computers, there is mentioned that the Web browser takes up a lot of RAM uses, most of the time when the Web / blog that is opened has a slow server response.
1. REDIRECT Problem
The first way is to solve this problem called redirect. Blogs that have redirects therein will slow down server response due to request again.
For example, you're going to onetwo3.com, and you redirect to onetwo3.com/test. Of course, it can slow down because you open 2 pages at once, onetwo3.com and onetwo3.com/test. So, it's a good idea to eliminate redirects like this. Usually by deleting a static homepage.
Or another way that you can do that is by adding/? m = 1 behind the blog URL when checking the loading speed of the blog in Google pagespeed Insight.
This way is quite potential, can you check both of the speed score of my blog loading below:
For example, you're going to onetwo3.com, and you redirect to onetwo3.com/test. Of course, it can slow down because you open 2 pages at once, onetwo3.com and onetwo3.com/test. So, it's a good idea to eliminate redirects like this. Usually by deleting a static homepage.
Or another way that you can do that is by adding/? m = 1 behind the blog URL when checking the loading speed of the blog in Google pagespeed Insight.
This way is quite potential, can you check both of the speed score of my blog loading below:
Without/? m = 1
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.latetechno.xyz%2F
With/? m = 1
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.latetechno.xyz%2F%3Fm%3D1
How to get a score 100 on Google PageSpeed Insights
I get a perfect score on the mobile device when using/? m = 1 behind the URL, because when accessed via mobile / mobile browser does not need to be exposed to redirect anymore.
I get a perfect score on the mobile device when using/? m = 1 behind the URL, because when accessed via mobile / mobile browser does not need to be exposed to redirect anymore.
2. Buy a TLD domain
Yup, buy a domain. That's the main thing I emphasize. Somehow, when you still use blogspot frills on the URL of your blog, it often comes up with this issue of Reduce Server Response Time on Google PageSpeed Insights.
Not enough to buy a domain, you should also be selective in choosing a suitable domain for your blog. As I've read in an article on Rigor's blog, a cheap domain could instead add to the problem at the speed of server response time.
Therefore, do not let you be distract at the price of a cheap domain, especially to be shared for free. Because there is definitely a shortage behind it.
If you do not believe, please see my blog speed report while still using subdomains.
Not enough to buy a domain, you should also be selective in choosing a suitable domain for your blog. As I've read in an article on Rigor's blog, a cheap domain could instead add to the problem at the speed of server response time.
Therefore, do not let you be distract at the price of a cheap domain, especially to be shared for free. Because there is definitely a shortage behind it.
3. Turn off the HTTPS Redirect
For those of you who still use the blogspot domain and get the problem of reduce server response, you can handle it by turning off the redirect to HTTPS. Somehow, HTTPS redirect can make automatic score to be red in PageSpeed Insights...
Do not forget, after you turn off the redirect, if the speed check in PageSpeed use HTTP instead of HTTPS, for example:
http://intricksseo.blogspot.co.id
Do not forget, after you turn off the redirect, if the speed check in PageSpeed use HTTP instead of HTTPS, for example:
http://intricksseo.blogspot.co.id
4. Don't forget Hosting
For those of you who still have slow response server, it could be because the hosting that you use is still free or the ' bottom class '.
As we know, the more traffic coming to our blog, the slower the server response time, which resulted in some visitors ' delay ' time of their visit.
So the solution to this third problem is to upgrade the hosting you are using to better. Here are some hosting options that you may be able to use, sorted from the most economical first.
As we know, the more traffic coming to our blog, the slower the server response time, which resulted in some visitors ' delay ' time of their visit.
So the solution to this third problem is to upgrade the hosting you are using to better. Here are some hosting options that you may be able to use, sorted from the most economical first.
Free Hosting
Free hosting is a complimentary hosting that is usually widely spread over the internet. The hosting of this type is shared, with the meaning of each user hosting has been given a share of each.
The advantage of hosting is that you will not spend any penny
The drawback is that servers are often down, slow server response, sometimes ads appear, limited features, etc.
Shared Hosting
Shared hosting is a type of paid hosting, but used together. Suppose 1 hosting is used for 5 websites, and so on.
The advantages are cheap price and no ads
The drawback to hosting this is that a little limited feature, sometimes experiencing down when half of other blogs are crowded, and so on.
Personal Hosting
Personal hosting is the most excellent type of hosting, because you are the one who holds 100% control over your hosting and you are wearing it.
The advantages of hosting is certainly because of the many features, not easy to down, no ads, and much more
The drawback is that the costs must be incurred large.
But the second way is not very important, because hosting Blogger I think is quite strong.
But the second way is not very important, because hosting Blogger I think is quite strong.
5. Reduce the Resource
Without notice, the more your blog uses scripts from outside, the slower the server response is. Why this could be happened?
Obviously due to the number of resources or needs to be accommodated and the number of outgoing requests. This resulted in the blog getting slower loading even though the network that the visitors were wearing included quickly.
So my suggestion, use that needed only for your blogs / website
Another way that you can use is to reduce the number of images on each post and reduce the number of posts displayed on your blog's homepage, it'll make your speed increased on Google PageSpeed Insight.
Obviously due to the number of resources or needs to be accommodated and the number of outgoing requests. This resulted in the blog getting slower loading even though the network that the visitors were wearing included quickly.
So my suggestion, use that needed only for your blogs / website
Another way that you can use is to reduce the number of images on each post and reduce the number of posts displayed on your blog's homepage, it'll make your speed increased on Google PageSpeed Insight.
