{"id":51995,"date":"2020-01-28T09:46:39","date_gmt":"2020-01-28T08:46:39","guid":{"rendered":"https:\/\/www.humanlevel.com\/sin-categorizar\/como-interpretar-el-nuevo-informe-de-velocidad-de-google-search-console.html"},"modified":"2020-01-28T09:46:39","modified_gmt":"2020-01-28T08:46:39","slug":"how-to-interpret-new-google-search-console-key-web-metrics-report","status":"publish","type":"post","link":"https:\/\/www.humanlevel.com\/en\/blog\/seo\/how-to-interpret-new-google-search-console-key-web-metrics-report","title":{"rendered":"How to interpret the new Google Search Console key web metrics report"},"content":{"rendered":"

The new top web metrics report<\/strong> from Google Search Console <\/strong><\/a>(also called Core Web Vitals<\/strong> metrics) provides us with very interesting aggregate data that lets us know whether the perception of web performance<\/strong> is good or bad for users. In addition, it also serves to detect the worst optimized parts of the web and thus be able to attack the points that have the greatest impact on performance. Let’s see what information this type of report presents and how to interpret it.<\/p>\n

To access this report, go to the side menu and click on the option “Main web metrics” (formerly called “Speed (experimental)”) in the “Improvements” section:<\/p>\n

\"Experimental
As it was seen in the past<\/figcaption><\/figure>\n

 <\/p>\n

\"Key
As seen now<\/figcaption><\/figure>\n

 <\/p>\n

Here we will see a screen similar to the following one:<\/p>\n

\"experimental
New speed report (experimental) in Google Search Console<\/figcaption><\/figure>\n

On the X-axis of the graph we have the number of URLs that are slow, normal or fast <\/strong>and on the Y-axis the date. In this way, we can observe how the performance of URLs evolves. Normally, when there is a change (e.g. from normal to slow URLs), the total number of URLs analyzed remains more or less stable, as in the mobile section of the example above.<\/p>\n

Where do you get the data you show?<\/h2>\n

Google Search Console needs to obtain the FCP and FID performance metrics to know if a URL is normal, fast or slow<\/strong>. These are collected by Google Chrome from users and stored in a public database named Chrome User Experience Report.<\/a><\/strong> To launch queries to this database it is necessary to know how to program multidimensional queries, so it is easier to consult the historical data of our domain in this new screen of Google Search Console or to obtain this same performance data directly from Google PageSpeed Insights<\/strong>:<\/p>\n

\"FID
User data or field data, from the FID and FCP metrics in Google PageSpeed Insights, for the analyzed page and the entire domain (source data).<\/figcaption><\/figure>\n

In Google PageSpeed Insights we can see the aggregated values obtained from users in the last month for the FCP (First Contentfull Paint) and FID (First Input Delay) <\/strong>metrics , <\/strong>both on the analyzed page (field data section) and for the entire domain (source summary). These metrics have the following meaning:<\/p>\n