Now let’s get to know the main features of the tool and how they can help maintain and optimize navigation on a website.
1. Speed Score
PageSpeed Insights will rate speed on a score that will range between 1 and 100. The higher this score, the better the site’s performance. In the tool panel, in addition to the grade, colours are used to flag and rank performance metrics.
The grade is measured by comparing your page’s load speed with the average load time of other pages. From 80 points onwards, speed is considered good, within Google’s criteria.
2. Field Data (Field Data)
This section of the tool demonstrates the website’s performance over the last 30 days also comparing it to other websites. The generated document is Chrome’s user experience report, which displays a series of metrics from actual user browsing.
3. First content display (FCP – First Contentful Paint)
This metric is concerned with measuring the time spent navigating to the page, as well as when the first bit of content is rendered in the DOM. That is, it is a metric that defines the speed of the first content displayed on the page to the user.
4. Input latency (FID)
This data, created from Core Web Vitals, indicates the page’s responsiveness to user commands. Thus, a low number means that the page responds quickly to user interaction when clicking on the contents.
5. Laboratory data (Lab Data)
Unlike field data, laboratory data is information that simulates reality but is not precisely real data. PageSpeed Insights generates such data to indicate the nuances of the site’s performance, classifying it in colours, green, yellow and red, where green is good, yellow is regular and red is bad.
6. First Important View
This metric, FCP (First Contentful Paint), is also related to content display speed. The smaller it is, the faster the content loads for the user. Precisely defines how long the main content has been displayed.
7. Speed index
Here we have the average speed that the content on the page becomes visible to the user, regardless of being the main one or not. So, the lower the rate, the better the performance.
8. First idle CPU
The first idle CPU is data on the page’s ability to respond to most user input without delay. Furthermore, it demonstrates whether most elements of the page are user-interactive.
9. Time to get interactive
Here we have data to understand the time it takes the page to become interactive to the user. It is an important fact, as some sites may invest in improvements in visibility at the expense of interaction elements, which can make the experience unsatisfactory for the user.
10. Possible maximum latency on first input
Related to lab data, it is the maximum possible delay of the first entry, showing the longest task duration, after the FCP, that can be experienced by the users.
In this field, PageSpeed Insights suggests the possibility of several improvements for loading the page, based on the various data presented above.
The diagnosis, in addition to showing the current status of the page in different metrics, also demonstrates practical recommendations to apply on the website.
Is a good PageSpeed Insights score only a 100?
The maximum PSI score, besides being almost unattainable, does not by itself determine the quality of the page speed. As we mentioned, it’s an important tool to understand the site’s performance, but you don’t need to focus your efforts on the maximum score.
Trust the process of running the analysis periodically and implementing the suggestions that the analysis brings and the result will come. You also need to always keep track of actual speed, plus spot improvements that are actually relevant to key metrics like conversion rates.
Remember, also, to use competitor performance data as a parameter to focus your efforts on issues that give your site a competitive advantage.
How to improve the score on PageSpeed Insights?
Below, check out some tips for implementing PSI recommendations accurately and correctly, improving page grade and, consequently, performance and user experience.
1. Optimization of HTML code
Improved HTML code can help the performance of the page, as duplicate codes or unintentional tags get in the way of server readability. Thus, it is important to organize the code with compression tools, for example, which help to optimize the HTML in a very practical way.
2. Image Optimization
Images should also be improved as they are often the main causes of page load delay. It is possible to optimize:
- The size of an image;
- The display size in relation to the image’s actual size in pixels.
In addition, it is important to delay loading images off-screen, use a content delivery network (CDN) when opting for state-of-the-art images.
AMP is a Google tool to facilitate loading on mobile devices, prioritizing the user experience through quick and simplified access, offering a more basic and functional mobile version, without unnecessary features that make the page heavy.
4. Content Delivery Network (CDN)
CDN delivers the server load to several different locations and uses the one closest to the user to fulfill requests. The closer the CDN and user data are, the faster the load time.
5. Defer loading images off-screen
Here, it is possible to postpone access to images only when the user uses the scroll bar. Avoiding that all are loaded at the same time, which contributes to the delay in delivering the content and slowness of the page.
6. Improving server response time
Improving server response time means ensuring your website is hosted on a great server. So, if PSI recommends these criteria, please contact your hosting provider or consider hosting solutions best suited to your site.
Minification excludes white space and comments in developers’ work to improve CSS and JS files, which optimizes load time.
8. Browser Cache
Here, Google PageSpeed Insights considers the number of resources the browser needs to assimilate from your page to display when it is requested again. This memory is defined by the cache. The better it is organized, the easier the browser can retrieve the page from the cache.
9. Clear redirects
Google PageSpeed Insights will also suggest that redirects be cleaned up, as their accumulation also slows down when browsers request additional HTTP.