How To Use Google‘s New ‘Speed Report‘ In Search Console

Google has released a new feature in Google Search Console that is designed to help marketers understand performance across search channels. A speed report will allow you to see how fast your website loads on mobile devices, what percentage of traffic comes from organic searches and much more data about the overall performance of your site.

Google has recently released a new feature in their search console called “Speed Report”. The “Speed Report” allows users to see how fast or slow Google is crawling specific keywords and phrases. Read more in detail here: google search console.

Google stated in early November that a beta version of the Speed Report had been introduced to Search Console. We’ve known for a long that this was coming since it was featured in many images shared by Google.

For a long time, speed testing has been a challenging undertaking since there is no single location where an SEO can assess page speed. To grasp the vast dataset that Google uses to rate our websites, we’ve had to depend on either a big number of Page Speed Insights tests, 3rd party tools (which still have their purpose), or sophisticated Big Query queries.

This article will show you how to utilize this new tool to speed up your website and get actual, quantifiable results.

Where Can I Get A Speed Report?

The report may be seen in Search Console under the ‘Enhancements’ tab:

How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

By selecting this option, you will be taken to the report, where you may begin digging.

Where did this information come from?

First and foremost, it’s critical to comprehend where this data originates from and how it varies from other speed tools available.

The information comes from Google’s massive collection of user experience measurements for how real-world Chrome users interact with popular locations, known as the Chrome User Experience Report. Rather than isolated tests done by bots, this data source is a real-time user measurement that displays how people are interacting with your website.

The data in the report was previously only accessible via the use of BigQuery, which was complex and costly, or by depending on Page Speed Insights having your data in the ‘Field’ tab.

We can conduct a speed test on a page from the Impression site, but it doesn’t return any ‘Field Data,’ indicating that nothing is arriving from the CrUX data.

1636674123_203_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

We don’t have any real-world measurements to compare this to outside of Big Query. However, if we look at the new ‘Speed Report,’ we can see that this URL has CrUX data.

1636674124_211_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

This is a significant bonus for the tool, as it gives us another data point to work with that we didn’t have before.

Get a 7-day trial for free.

Over 120 tests are available to verify the technical health of your website.

ADS illustration

Making Use Of The Speed Report

When you click on the report, you’ll be sent to the primary dashboard for the speed report, which has two tabs:

Mobile

1636674129_933_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

Desktop

1636674130_151_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

Both of them are quite self-explanatory. It’s worth noting that they don’t contain a ‘tablet’ field, which we know is reported independently in CrUX. It is unknown whether this has been included into any of these areas, therefore it is possible that it will be when the tool is released from beta.

Each graph is divided into three parts, each of which follows a traffic light scheme that corresponds to CrUX’s color coding:

  • Slowly (red)
  • Moderately difficult (yellow)
  • Quickly (green)

The distinction between mobile and desktop is useful since we all know that they may have various items, menus, and interaction. You can see in the following example that the desktop version has a bigger problem with slower URLs than the mobile version.

In this Speed Report, you’ll learn how to decipher the metrics.

By clicking ‘Open report,’ you may access these tabs. Anyone who uses Search Console on a regular basis will notice a familiar-looking tab.

1636674133_709_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

The first is a customizable graph that allows you to see patterns in where your URLs are located as well as filter out certain categories. Looking at the above example, we can see that something happened in the beginning of August, when a big number of URLs began to be classified as sluggish – naturally, this is the place to start looking.

1636674135_671_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

The second ‘Details’ page details the concerns with the amount of URLs that have been submitted against it. This page also shows the sort of problem that Search Console has identified.

There are just two metrics in use right now. However, they are undoubtedly the most essential website metrics, since they represent how real-time viewers will perceive the page load.

  • FCP (First Contentful Paint) – This is the time it takes for the browser to load the first piece of content. This might be a banner, a menu, or something else entirely. People may bounce right away if the FCP is too lengthy.
  • First Input Delay (FID) – This is the time it takes for a user to click on the first element on your site and for the browser to respond. Even if the page is just partly loaded, a lengthy FID might annoy users and make the website seem sluggish.

The traffic light system is used to classify both of these measures. The times are assessed using the same criteria, with no distinction made between desktop and mobile levels.

 

Slow

Moderate

Fast

FCP (Financial Control Panel) (Mobile)

More than three seconds

More than one second

Under 1s

FCP (Financial Control Panel) (Desktop)

More than three seconds

More than one second

Under 1s

FID (Foundation for International Development) (Mobile)

More than 300 milliseconds

More than 100 milliseconds

Under 100 milliseconds

FID (Foundation for International Development) (Desktop)

More than 300 milliseconds

More than 100 milliseconds

Under 100 milliseconds

For FCP, the scores are sorted by 75 percent of total traffic, while for FID, the scores are arranged by 95 percent of total traffic.

The Speed Report Is Being Analyzed

We now know how to utilize the dashboard to detect problem areas, and we can retrieve a list of URLs by clicking on one of these concerns.

Here’s an example from the Impression site, where the First Contentful Paint takes longer than 1s on the desktop site:

1636674136_288_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

Under the ‘Similar URLs’ tab, the bottom tab aggregates URLs, which is very important if you have issue regions because it helps you to discover specific sites.

Starting with the slowest URLs, we may click on the problem to bring up a popover on the right-hand side of the screen with a list of the following URLs:

1636674138_272_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

This only returns 20 similar URLs; given that the problem affects 575 similar URLs, we can understand why this isn’t the most relevant sample size to start with. Nonetheless, we can tell that our blog is the cause of this on a regular basis.

Putting the Speed Report’s Recommendations into Practice

We’ve gone through the speed report and created a list of problematic URLs that need to be fixed. The next step is to import them into Page Speed Insights (the report lets you do this for each URL).

1636674141_381_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

When we use Page Speed Insights to evaluate the page, we get a score of 98 on desktop. This instantly stands out as being inconsistent with the scores we can see on the dashboard.

This is why the new page speed report is so useful: it’s more than just a collection of Page Speed Insights ratings; it’s also real-time user data. As a result, we need to make these pages even quicker than they are now.

1636674143_949_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

Two areas where we can improve are by compressing some of our pictures, particularly the main banner image, which might save 66kb. Another option is to use some additional slow loading on some images that doesn’t need to display right away.

At this stage, we’d write up our suggestions and send them to the development team to address.

It’s evident that there’s not a lot of room for improvement on this page, so we’ll have to take the URLs in moderate with a grain of salt.

Other Ways to Measure Page Speed

I’ve merely detailed how to use Page Speed Insights to test the tool in the example above. As you may be aware, there are a variety of different techniques available to assist us in our quest for incredible site performance, including:

  1. GTMetrix
  2. WebPagetest
  3. Pingdom

Each of these technologies has its own set of measures, and we always recommend gathering as much information as possible. Having each of these tools validate your difficulties provides you a much stronger hand when attempting to push changes through, especially if your actions would eat up any of a client’s or internal team’s development resource.

Always keep track of the ratings you get from these tools so you can compare them later when evaluating the effectiveness of the adjustments.

Observing Changes

We utilized the report to identify the problems, and the developers responded to say they had resolved them. Before we start submitting these URLs to be verified, we need to double-check this.

We would then go back into the speed report and hit ‘Validate Fix’ after rerunning the tests with all of the tools recommended before to check whether the problems had ceased coming through.

1636674145_118_How-To-Use-Google%E2%80%98s-New-%E2%80%98Speed-Report%E2%80%98-In-Search-Console

After that, Google will monitor the usage statistics for this set of URLs for 28 days, creating a’verification window.’ They’ll use this information to determine which URLs in the bucket have been repaired.

Because the process is based on visitors viewing the website, it may take a bit longer for certain URLs with lower traffic.

Important Points to Remember

You should now have a solid understanding of what the ‘Speed Report’ is and how it may assist you enhance your website’s organic search results. Here are some crucial points to remember:

  1. The tool is still in development, so we anticipate it to grow over time, since it now only has two metrics.

  2. This is information from Google that we haven’t received previously; it’s presented in a very straightforward manner and is really helpful in determining the overall performance of a website.

  3. When there are so many URLs in a single bucket, a sample size of 20 isn’t particularly helpful.

  4. With URLs, the report seems to be unduly severe at the moment: sites with high Page Speed Insights ratings appear in the report as moderate.

Get a 7-day trial for free.

Over 120 tests are available to verify the technical health of your website.

ADS illustration

Google has recently released a new feature in their search console called “Speed Report.” This report is designed to give you the most accurate and up-to-date information on how your website performs. Reference: google performance report.

Related Tags

  • google search console speed report
  • google search console queries
  • google web vitals
  • web vitals chrome extension
  • google.com preferences

Leave a Comment

Your email address will not be published.