it draws a series of conclusions and organizes the advice into three different blocks identified by colors: Red: Things that must be solved and that by doing so the score will improve considerably. Yellow: Things that can be solved if they are easy to solve but. by doing so. the score will not vary significantly. Green: Rules that are already fulfilled and in which it is not necessary to do anything. Regardless of that. in the Google Page Speed Insights interface we have two sections. one for mobile devices and another section for desktops and laptops. Google page speed test – Sections in insights The rules of one section do not have to have anything to do with those of the other section.
They are almost independent and must be “treated” separately. Of course. it may be that if you solve problems in “Desktop”. for example. problems in “Mobile” will also be solved. although it does not have to be that way. From here. we are going to go part by part gutting the official documentation of Google Page Speed Insights and the rules that appear there to improve the score in it . Avoid excessive redirects Despite the fact that Google Page Speed rarely gives this error. when it does. it is a “major reform”. since we will have to modify the behavior of our blog or website so that it does not make so many redirects. An example of excess in this practice is. for example. if our site when entering without WWW made the following redirects:
Brainstorm With Your Team
On responsive websites where there are Vietnam phone number no redirects and there is only one version of the website. This error does not usually appear in Google Page Speed Insights. It is impossible to clarify how to solve this point. Since it depends on the website and how you have it set up. What is possible is that you have to rethink some things about your website. especially how it works. enable compression Most web servers on the Internet are configured to compress website resources with GZIP before they are sent to visitors’ browsers. To compress the content before sending it to the visitor. web servers can use various methods. in fact. Apache can use GZIP or Deflate.
Clarify that. although GZIP is more effective. it is usually more compatible with Deflate. Solving this is easy. although it depends on the web server that we have on our server or hosting. On Apache servers. it is enough to modify the to activate GZIP or Deflate. while on Nginx servers. We will have to modify the configuration files. The only thing we need to keep in mind is that we will. Only be able to compress website resources hosted on our web server. And we will not be able to do anything to compress. The resources from external servers such as those of Facebook for example. Improve server response time This is the only point where the Google Page Speed score and the loading speed of the web are unified. Since. by improving the response time of the server.
A Different Search Almost
We will be able to lower the loading times. And the time it takes for the server to serve the contents. To comply with this Google Page Speed rule. Our web server must have a response time of less than 200 ms (0.2 seconds). This is practically impossible if we use a CMS like WordPress and without using any type of cache. On the contrary. with an effective cache it is possible to comply with this rule without problems. If your website fails this rule. you have to check the optimization of the website. Install a cache plugin and. if you still fail to pass this rule. Contact a professional who can guide you better on the subject or the hosting provider if it is managed.
Specify browser cache The browser cache is another of the easy rules to comply with in Google Page Speed Insights. Although as with compression. the changes that we must make vary depending on the web server that we are using. In Apache. the process of activating the browser cache is similar to that of compression. We only have to edit the . but on other servers like Nginx we will have to modify the configuration files. You must be careful with the browser cache. since. at certain times. We can have problems with the content update if we configure a very high TTL. In any case. the minimum TTL imposed by Google Page Speed are quite low. So they do not usually cause any problems.
