Google page speed. PageSpeed ​​Insights: loading speed as a ranking factor

As a website owner, you know that it has to be fast. And you have already read various articles on how to speed up your site, perhaps you have already implemented something. Then it becomes interesting how quickly the site loads. This is where you go to Google PageSpeed ​​Insights as the most popular tool, get an assessment and a list of recommendations from Google. And this is where most of us get lost:

  • Is PageSpeed ​​Insights important for SEO?
  • Why is my site not rated at the maximum?
  • What do all these recommendations mean?

Previously, you turned on caching on your site and expected the PageSpeed ​​score to be nearly perfect, but now you wonder why this plugin didn't fix all the speed issues? Maybe he's not very good? The short answer is that:

Google PageSpeed ​​is irrelevant.

Yes, it does ... but why doesn't it matter?

Page speed vs PageSpeed ​​Insights

Speed ​​(website load time) matters and is an important metric in SEO and also affects user experience. When a Googlebot indexes a site, it does not see the PageSpeed ​​indicator, but only knows the speed itself. Did you know that Google PageSpeed ​​Insights does not measure your site's speed? Yes, read this again:

Google PageSpeed ​​Insights does not measure website speed.

Hello dear readers of the blog site! Today's post will be devoted to the wonderful Google Page Speed ​​tool, which allows you to test any page to explore the possibilities of speeding up its loading ().

It's no secret that search engines, especially Google, have been paying serious attention to this aspect lately, so fast websites get a certain advantage in ranking and higher positions in search results.

Google Page Speed ​​Insights not only detects and indicates all the reasons why the page does not load quickly enough, but also offers specific ways to eliminate them, and some of the problems found can be easily eliminated by the service itself in automatic mode.

What kind of optimization tools does Google offer to speed up websites?

In principle, for each of my projects, I devote a lot of time to page optimization activities that contribute to their fast loading. The only thing that really didn’t get to them was the blog site, which is essentially a visual aid for novice webmasters who are not devoid of healthy ambitions and charged to achieve their goals.

But, since I am a perfectionist by nature, I could not admit that an information web resource, carrying, so to speak, knowledge to the masses, would be in some aspect among the laggards. Therefore, it was decided to make every effort to optimize it, including the recommendations of Paige Speed.

Therefore, I immediately pass on to the description of this tool so that you can evaluate its functionality and apply it in practice for the benefit of your web resources.

Previously, Page Speed ​​Insights could be used as browser extensions and download links were present on a dedicated Google page. Moreover, in order to use it in Mazil, it was first necessary, where Paige Speed ​​was present as its addition:


Now it is no longer possible to use extensions for browsers from Google, although the same plugins, but in a slightly different interpretation, are available on the official web pages of Chrome and Mazila (s). In addition, there is a fully functional eponymous online service Google with exactly the same functionality and no less capabilities. If you go to the Developers section, you will see a link to the Page Speed ​​tool there:

By the way, on the same page PageSpeed ​​Tools All Google site acceleration suggestions are located It seems that the developers of the "empire of good" have taken seriously the optimization and acceleration of the entire Internet space, since in the Developers you will find a link to the Optimization Library ( Integrate the PageSpeed ​​Optimization Library) open source.

Availability of open source software of this project, based on the module " mod_pagespeed", Which is installed on Apache servers (of which, by the way, the overwhelming majority), means that anyone can improve or update it.

That is, in this way it is quite possible, at the expense of the Internet community, to create an acceleration tool close to perfect. How all this will look in practice, time will tell. Naturally, in order to make a full-fledged contribution and achieve success in this good cause, you need to be a sufficiently qualified programmer.

If you take a look at the top screenshot (the information is surrounded by a green frame), you will see there a link to install the latest version of the ready-made module. It may well be interesting for owners who can install it on their servers, providing automatic acceleration of the sites located there.

Moreover, there are two modifications of the Page Speed ​​module: directly for Apache servers and for the Apache + Nginx bundle, where the second plays the role of a proxy server:


By the way, the option of sharing Apache and Ngnix in modern conditions is most in demand and is used by most advanced hosters (including, for example, Sprinthost), since it provides efficient use of resources. So, if you are interested in this method of automatically speeding up sites, you can put your hand to it yourself or strain your hoster.

Google "s PageSpeed ​​recommends (ways to increase the speed of loading site pages)

Above, we considered the possibility, so to speak, of a global increase in the speed of loading websites, which requires specific knowledge (it is likely that this information will be useful to someone, at least in the future).

But for the main part of readers, that is, simple webmasters, the option that is understandable and accessible "here and now" is more relevant. The PageSpeed ​​Insights service fully complies with such conditions, which we will talk about in more detail. For analysis specific page site, enter its URL () on this page:



After the analysis, you will see the Google rating, and both in relation to mobile devices and PC, which is especially valuable. In this example, for the home page of this blog, 76 out of 100 credit for mobile is an average score that can be significantly improved by following the guidelines below.

Moreover, to optimize each resource that slows down page loading, links are given to the relevant sections (in order to get them, click the link "How to fix?"), where you will find descriptions of the necessary corrective actions.

But there is an important point to make here. Necessary analyze pages different types to achieve faster loading times for the entire site. For example, for a standard WordPress blog, the level of optimization in this aspect for the main, categories, static pages and posts can be completely different.

Above, I gave an example of a home page that displays post announcements, but in one of the articles, Paige Speed ​​gave a much lower rating:


This happened because posts are usually much more voluminous and include many different kinds of resources and content (images, videos, scripts). Therefore, it is better to start checking for optimization with them. By the way, from this point of view, start from the assessment that Page Speed ​​provides mobile phones as achieving a decent download speed on such devices requires a lot more body movements.

But even different pages of records may differ in quality. This is also due to the fact that some of them run additional scripts that slow down the loading. For example, the level of optimization of one of these web pages caused me not only surprise, but a real shock:


It is quite obvious that 62 points out of 100 possible is not the result to which one should strive. And all because on this and a number of pages of posts I have a script of the SyntaxHighlighter plugin that initiates beautiful design backlit codes.

There may be several such extensions on the site. In each specific case, you need to decide for yourself how important the plugin is for your resource in terms of the functionality that it provides. And depending on this, you either need to remove it, or take steps to optimize that will help speed up page loading.

The above is especially true for the world's most popular CMS, which is used by the overwhelming majority of webmasters. This multifunctional engine is good for everyone, but it needs to be constantly debugged in terms of reducing the load on the server and reducing the page load time. Therefore, the owners of web resources working on WP should take note of this. And the presence of such a service as Page Speed ​​is very useful here.

Be sure to read all these articles at least in view mode by clicking on the links provided above, perhaps you will find a lot of useful things for yourself. In the future, I plan to return more than once to the problem of speeding up web resources, and therefore you can subscribe so as not to miss the release of fresh publications on this topic.

Finally, watch a helpful video to learn why Page Speed ​​tips are advisory and why you shouldn't follow them fanatically.

Google PageSpeed ​​module for a website: what it can do and how to use it

We decided to experiment and add an accelerator from Google to three projects. What came of it - we find out.

Websites should load instantly. Oh no, sites don't owe anything to anyone? Get on the trolley bus and sit next to the student who is sitting with an iPhone. See if he's ready to wait for some online store to load. Let's just say: three seconds - and the tab is closed. The next result from the search results is used.

By the way, about search results... Website loading speed affects search engine rankings. Proofs and. Sites that “slow down” are less frequently visited by robots, which means they are less likely to be indexed. The place in the search results and the convenience of finding the necessary information suffer from this.

Constantly think about whether your page will load slower on a smartphone than on a PC. And if so, then we will most likely downgrade it in the SERP.

- Matt Cutts, Google

Google has worked hard and released its own speed test tool - PageSpeed. It is easy to find elements slowing down the loading - go here and in the only field we indicate the address that you want to test. A detailed performance report will be ready in a minute. The result will be shown in parrots. Ideally, there are a hundred of them, but try and get it! Even Google itself can't do it: check its services :)

Tests are carried out for both desktop and mobile versions of the site. It is better to navigate by the color scale: the yellow zone will indicate that there are elements that are worth optimizing, the green one will tell you that everything is ok. If the site is in the red zone, speed up and optimize. Otherwise, there is an abyss ahead: while the page is loading, the user will already go to another site :)

There are two ways to optimize your site.

Manual optimization

1. Compress pictures with Photoshop or run them through Optimizilla, For example

The less the pictures weigh, the more jackals, the faster the site loads. We do compression, hide multi-megapixel photos under the cat. Enough 640 × 480 previews. The smaller the picture, the faster the site.

Even on start page Google Developers graphics can be compressed up to 71%.

2. We connect fonts from the site itself, and do not pull them from googlephones

Minus - until the browser has loaded the font, the user will see the annoying Arial or Tahoma.

3. Using the browser cache to the maximum

When the site has already been partially saved by the client, loading will go much faster.

4. Minify JavaScript and CSS

Scripts are not edited every day after release - there is no point in compressing them on the fly. Stop optimizing once after code changes. JS templates are better handled on the server, embed the results in HTML, and use the templates on the client after upload.

5. Shrinking HTML

In practice - removing extra spaces, tabs, line breaks.

6. Remove unused code

You can use the built-in "Chrome" audit. Press F12 and go to the Audits tab. There is a single Run button at the bottom. Does basically the same thing as PageSpeed. Only in real time.

Automatic optimization

Any site consists of dynamic and static elements. Dynamic elements are the HTML code itself, derived from php work and database queries. The rest is static. These are images, JavaScript and CSS.

Automatically optimizing a site can be done with a cool thing from Google - PageSpeed ​​Insights. This module is installed on the nginx server and, after settings, compresses in real time dofiga info, including graphic.

PageSpeed ​​Insights can analyze HTML and optimize resources. Pinch, in short. In the source code, the resources will be located in a different path, not according to what the developer asked to compress the photo. This is worth considering. But the display of the resources will not change. Weight will decrease. This means that the page loading speed will increase and the visitors will become more satisfied :)

However, PageSpeed ​​Insights has limitations. It can only be installed on nginx running on or virtual server... No, a shared server rented somewhere in Germany will not work.

The second limitation has to do with the eternal browser war. Pictures compressed by PageSpeed ​​are converted to the .webp format, which only "Chrome" understands (in the popularly beloved Internet Explorer 6 such a thing will not work). IN latest versions Opera also learned how to display such pictures. Because the engine has changed.

Examples of using PageSpeed ​​Insights

We have installed the PageSpeed ​​Insights module on three projects - on our new site and on two client projects. The module sees which browser the request comes from, looks to see if it is trained to display the webp format and gives either an optimized image or a regular jpeg.

Setting up Sibiriks took about half a day. Something had to be done empirically: they changed it, watched what was happening. Sometimes the zone was green, and it could be completely unpredictable to fly into yellow.

Both versions are now in the green zone. This means that there will be no problems with speed. If the connection speed is good, not some EDGE :)

Within the framework of technical support of the online store of the Vitra factory, we decided to experiment and install the PageSpeed ​​Insights module on it:

Google PageSpeed ​​is a tool that allows you to check the speed of a website. It allows you to estimate the download speed for stationary PCs and mobile devices and provides recommendations that can be used for optimization.

The result of analyzing the site load speed looks like this:

Check site speed with Google PageSpeed ​​Insights and service recommendations

After analyzing the site load speed, you can often get the following recommendations:

Optimize images

The most common service recommendation is related to the best choice images for the site. The graphical content is very heavy and can greatly slow down the loading of resource pages. The most general guidelines are to choose the right format (most often it makes sense to use PNG), image size and quality. So too large an image used as a background can significantly slow down the site's loading speed. You should always check images and reduce their size and quality as much as possible (it makes sense to set the size and quality of images to the minimum acceptable for a particular resource).

Enable Compression

Compression by the web server is an important performance parameter. Enabled by the mod_deflate module in Apache or by the directive in Nginx.

Leverage browser caching

Determines whether the header is passed and data is cached in the user's browser. Caching can significantly reduce the number of requests to the server, which reduces the load on it and increases the speed of sending static data (which is the majority on any site) to the client

Eliminate render-blocking JavaScript and CSS in above-the-fold content

JavaScript code by default is executed as the page is loaded, similarly processed by CSS. Those. If a JS script is included in the body of a document, its rendering is interrupted each time until the script is executed. This can be avoided by adding JavaScript and HTML when connecting the body of the page will be rendered regardless of the executable code.

For example, JS in asynchronous mode can be connected like this: