The answer is yes, but although following PageSpeed 's guidelines is usually a good idea , up to a certain point, you should be aware that the analysis variables of this tool are very strict and are not always in line with what a truly optimized website is.
Therefore, you should not obsess over its indicators, as this will result in great frustration and, ironically, over-optimization of your resources that ultimately ends up harming your website.
An example of this is when PageSpeed Insights suggests you optimize CSS delivery . In an ideal world, your CSS would be minified and compressed to the max, and separated to display the essential styles (the critical assets) in the header and the rest in the footer. However, in the real world this is not possible, since you are probably using WordPress .
What's wrong with using WordPress?
There is nothing wrong with it. On the contrary, it is excellent! But achieving 100 PageSpeed points in WordPress when performing the Google web speed test can be quite a difficult task considering that, when installing plugins, you will have everything: CSS files on your page that cannot be minified or styles that are inefficient, among others, which will have a negative impact on the core web vitals of your website and consequently on its score.
There are other times when, even if our page is “perfect” and can reach a job seekers database score of 100, it is not possible to do so due to external factors. For example, if we have a low-budget server, it may give errors that cannot be solved, such as, for example, slow server response time or time to first byte (TTFB) . In that case, we can always contact our server provider to see if it is possible to improve the TTFB or consider hiring another service that is a little better.
At the end of the day, what really matters to us is the performance perceived by the user and not the Google Page Speed. Those who visit our website really care about how quickly they can see the content of our page and this is where we should focus our efforts. Use the Google tool to identify possible errors so that we can solve them and improve the actual loading time. Still, in the next section we will explain what are the most common errors that Google Page Speed detects on our website and how we can solve them.
Main problems and how to solve them
In this section we will present the 5 most common errors that usually offer us the greatest capacity to save loading time on web pages and we will explain in detail how to solve them.
1. Remove render-blocking resources
As Google explains in this article, render-blocking resources are those scripts and styles that block the first rendering of the page.
The goal of addressing these opportunities that Google points out to us is to reduce the impact that these files have on loading speed . To do this, we have 3 possible options:
- Board index
- All times are UTC
- Delete cookies
- Contact us