class= " post-template-default single single-post postid-1398 single-format-standard colour-0 to wpb-js-composer js-comp-to see-5.0.1 vc_responsive " >
27 Abr 2017



Google Page speed test €“ From A to Z

the news by Social

You have good score in Google Page Speed test?

More and more webmasters is interested in that their websites have the one best one in this Test.

And this, partly, is because the finder has given to understand in several occasions that its score of this Speed test influences actively in the internal SEO of a website.

We must consider, that the rules that Google Speed Page Insights marks to us that we can improve, are simply good practices that will help to secure one better score us and a better positioning SEO but than in the majority of the occasions does not have why to improve the speed of load.

I make this explanation because I on a daily basis am many clients who confuse both concepts: speed of load with score of Page Speed test.

In the last Google updates it has oriented his algorithm in securing to one better experience and usability (UX) in movable devices as smartphones and tablets.

This usability causes that every time it is more difficult to create showy and dynamic websites simultaneously, since, we were with a neck of bottle imposed by the algorithms of the finder if we want to have a high score in the test of Google Page Speed.

When the Page Speed Insights analyzes a website, removes a series from conclusions and organizes the advice in three different blocks identified by colors:

  • Red: Things that are due to solve and that when doing it the score will improve considerably.
  • Yellow: Things that can be solved if they are easy to solve but that, when doing it the score is not going to vary significantly.
  • Green: Rules that already are fulfilled and that are not necessary to do nothing.

Independent of that, in the interface of Google Page Speed Insights we have two sections, one for movable devices and another section for portable computers and.

The rules of a section, must not why have nothing to do with the other section, are almost independent and must €œtreat separately€.

That yes, perhaps if you solve problems in €œDesktop€, for example, also problems in €œMobile€ are solved, although it thus does not have why to be.

From here, we are going to go part by part gutting the official documents of Google Page Speed Insights and the rules that appear there to improve the score in the same.


Although Google Page Speed usually gives this error not very often, when it gives it, is a €œreform of importance€, since, we will have to modify the behavior of our blog or website so that it does not make so many redireccionamientos.

An example of excess in this practical one is, for example, if our site when entering without WWW made the following redirections: ‡’ ‡’

The ideal would be that it did it of direct way: ‡’

In websites responsive where they do not exist almost redirections and only exists a version of the Web, this error usually does not appear in Google Page Speed Insights.

It is impossible to clarify as solving this point, since, depends on the website and of how you have it mounted.

What yes it is possible is that you must reframe some things to you of your website, mainly of operation.


The majority of the Web servers of Internet is formed to compress the resources of the websites with GZIP before being sent to the navigators of the visitors.

In order to compress the content before sending it to the visitor, the Web servers can use several methods, in fact, Apache can use GZIP or Deflate.

To clarify that, although GZIP is more effective usually is more compatible Deflate.

To solve this is easy, although that we have in our servant or hosting depends on the Web server.

In servers coarse Apache with modifying .htaccess to activate GZIP or Deflate, whereas in Nginx servers, we will have to modify the configuration files.

The only thing that we must consider is that we will only be able to compress the resources of the website lodged in our Web server.

And we will not be able to make nothing to compress the resources from external servers as those of Facebook or Google Plus.


This it is the only point where Google score of Page Speed of load of the Web are unified the speed and, since, when improving the response time of the servant we will be able to lower to the times of load and the time that the servant in serving the contents takes.

In order to fulfill this rule of Google Page Speed our Web server must have a response time inferior to 200 ms (0.2 seconds).

This is practically impossible if we used a CMS as WordPress and Prestashop and, without using no type of cache.

On the contrary, with an effective cache yes one is able to fulfill this rule without problems.

If your Web fails in this rule, you must review the optimization of the website, to install plugin of cache and, if nor even so you are able to pass this rule, it contacts with a professional who orients to you better on the subject or with the supplier of hosting if she is administered.


The navigator cache is another one of the rules easy to fulfill in Google Page Speed Insights, although as with the compression, the changes that we must do vary following the Web server that we are using.

In Apache the process of activation of the navigator cache is similar to the one of the compression.

We only must publish the file .htaccess, but in other servers as Nginx we must modify the configuration files.

You must have well-taken care of with the cache of the navigator, since, at certain moments we can have problems with the update of content if we formed some TTL very high.

In any case, TTL minimum imposed by Google Page Speed is quite low reason why usually they do not give any problem.

Really this subject can give much €œgame€, but you look for by Internet which you must put in him .htaccess or in the corresponding configuration file you will find it without complications.


Within this section is the minificación of archives HTML, CSS and Javascript and that are the three archives of type text which they are served the visitors.

Minificar is the process by means of which the archives are optimized, for it, elements as the commentaries remove and the line jumps, everything is brief so that the final file weighs less possible and, therefore, the archives unload something faster to the navigator.

The minificación can become of several ways, even can make it a module installed in the Web server but, in normal conditions in a CMS as WordPress usually becomes by means of plugin of the type €œAutoptimize for WordPress€.

We must have special well-taken care of with the minificación of CSS and Javascript, since, if we do it without thinking and without control we can disturb the appearance of the website.

The same configuration not always is right for all the Web sites, depends on theme used and the elements that they have.


The images usually are the part that more weight in a website, therefore, we needed to optimize the images to be able to lower to the times of load when reducing the time that takes the navigating Web in unloading the resources.

If Google Page Speed Insights marks this error to us, which we must do is easy, we must optimize the images of our website.

We can optimize the images of several ways: from the servant, with plugin, an external service, a local application, etc€¦

The most automatic form to do it is through plugin.

In the case of WordPress we can do it with EWWW Image Optimizer or if we resorted to a Premium option, we can use plugin of with the corresponding Premium service.

This last option is much more efficient that the option of EWWW Image Optimizer.

Some images although are optimized with plugin will continue marking that are not optimized, these images we must optimize them manually with another type of local application or reduce his size with the purpose of to lower his weight.


This error at the moment usually does not appear much in present websites, since, normally all the styles put within a single style sheet CSS.

In fact, it is therefore more probable that it appears an error that it indicates to you €œPrioritizes the visible content€.

If your Web this created with a CMS and appears to you €œTo optimize the delivery of CSS€ in Google Page Speed, the best thing than you can do is to change theme.

In case it is an own development in HTML and CSS, the best thing than you can do is to return to give form him to the website.


This it is another error that usually appears in themes present enough that they overload much the part of above of the Web, since, is first which they see the visitors when entering.

Technically, this message usually appears when there are so many elements inserted in the part superior of the page that the navigating Web must realise more requests to the servant of whom it would have and, for that reason, slows down the load of the page.

If it leaves this error to you and you are using a CMS, it changes of theme or it reviews if some plugin is inserting additional elements.

If it leaves this error to you and your Web is developed by you, you are going to have to manually remove elements from the code.


Lately this error usually appears enough because of sliders in Javascript that usually is inserted in the part of above of the pages.

The error appears when the HTML loads code Javascript from external origins and the navigator must hope to unload the Javascript, therefore, the speed of load of the website slows down.

Which is the solution in this type of situations? Then the suitable solution is to move the Javascript at the end of the page or to cause that they load of asynchronous form.

In any case, if you are a nascent user costs to understand this process to you, reason why, you will have search which realises the necessary modifications, since, nor with plugins in the CMS it is able to solve this problem efficiently.

If you look for script/plugin that it allows you to insert an asynchronous slider you can prove with Revolution Slider.

At least in WordPress with the suitable configuration usually it loads well of asynchronous form.

External others exist scripts of Javascript that we can cause that they load of asynchronous form, as for example, the Javascript of Adsense or the one of Google Plus between many others.


The Internet giant also has developed modules to integrate the optimizations of Google Page Speed in the used Web servers more: Apache and Nginx.

In the case of Apache unit is called mod_pagespeed and in the case of Nginx ngx_pagespeed is called.

In either cases the module detects what rules can apply to your website and realises the necessary optimizations in the code served to the visitors.

These modules usually accelerate something the Web, since, also implement cache and realise the optimization of images to the flight following the rules of Google Page Speed, that usually are quite effective.

Although to have installed these modules of Page Speed it is good, there are servers who do not have it installed, for example, those of hosting shared.

This is because, the configuration that can be good for a Web can completely destroy the appearance of another similar Web.