Avoid excessive redirects
Posted: Sun Dec 22, 2024 6:38 am
Although 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 an excess in this practice is, for example, if our site, upon entering without WWW, made the following redirects:
Ideally, you should do it directly:
Domain.es ⇒ m.domain.es
On responsive websites where there are almost no redirects and there is only one version of the website, this error usually does not 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 will have to rethink some things about your website, especially its operation.
Enable compression
Most web servers on the Internet are configured to compress website philippine cp number resources with GZIP before they are sent to visitors' browsers.
To compress content before sending it to the visitor, web servers can use several methods, in fact, Apache can use GZIP or Deflate.
Please note that although GZIP is more effective, Deflate is usually more compatible.
Solving this is easy, although it depends on the web server we have on our server or hosting.
On Apache servers, simply modify the .htaccess 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 can only compress the website resources hosted on our web server.
And we won't be able to do anything to compress resources from external servers like Facebook's for example.
Improve server response time
This is the only point where the Google Page Speed score and the website loading speed are unified, since, by improving the server response time, we can reduce loading times and the time it takes the server to serve the content.
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 this rule can be fulfilled without problems.
If your website fails this rule, you need to review the website optimization, install a caching plugin, and if you still can't pass this rule, contact a professional who can guide you better on the subject or contact the hosting provider if it is managed.
An example of an excess in this practice is, for example, if our site, upon entering without WWW, made the following redirects:
Ideally, you should do it directly:
Domain.es ⇒ m.domain.es
On responsive websites where there are almost no redirects and there is only one version of the website, this error usually does not 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 will have to rethink some things about your website, especially its operation.
Enable compression
Most web servers on the Internet are configured to compress website philippine cp number resources with GZIP before they are sent to visitors' browsers.
To compress content before sending it to the visitor, web servers can use several methods, in fact, Apache can use GZIP or Deflate.
Please note that although GZIP is more effective, Deflate is usually more compatible.
Solving this is easy, although it depends on the web server we have on our server or hosting.
On Apache servers, simply modify the .htaccess 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 can only compress the website resources hosted on our web server.
And we won't be able to do anything to compress resources from external servers like Facebook's for example.
Improve server response time
This is the only point where the Google Page Speed score and the website loading speed are unified, since, by improving the server response time, we can reduce loading times and the time it takes the server to serve the content.
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 this rule can be fulfilled without problems.
If your website fails this rule, you need to review the website optimization, install a caching plugin, and if you still can't pass this rule, contact a professional who can guide you better on the subject or contact the hosting provider if it is managed.