Removed display blocking resources
Posted: Wed Dec 18, 2024 4:28 am
We found unnecessary CSS and JavaScript resources. It turned out that they were delaying the loading of images. The browser did not display the page until the unnecessary code was processed. It should be noted that this is a very common problem. We perform this task every time we need to improve performance.
We explicitly set the width and height attributes
Some images on the Customer's website "jumped", changing their location during the loading process of the web resource. This was due to the fact that the system needs to calculate the parameters of the place required to display the image. This is why the width and height attributes should be used - they allow you to avoid this. In fact, not everyone pays attention to this. But we are ardent supporters of maximum web performance and consider this important. After all, "jumping" images and formatting that is corrected during the loading process are unacceptable from the point of view of usability.
Configured to show all text while loading web fonts
Many users skim content very quickly. It is important that texts are shown to the visitor immediately. And on the Customer's website, some texts were not shown until the fonts were loaded.
Reduced the impact of third-party code
Third-party code is something that is not directly related to the site structure. This includes social media buttons, transitions, trackers, advertising, analytics, etc. As it turned out during the audit, the developers treated this issue rather frivolously.
In general, such a problem often arises when the administrator whatsapp number uk independently tries to make the web resource more efficient and adds the necessary codes without knowing how to do it correctly.
Set rules for efficient use of cache for static objects
We carefully configured the .htaccess file so that static elements are saved in the cache on the user's device. This way, some of the site data will not be downloaded from our service on subsequent visits, but will be loaded directly from the device. Of course, this provides additional acceleration.
Prevented excessive network load
To do this, we carried out a complex set of works, including deep optimization of images, styles, scripts. It should be noted that the factor of excessive network load retains its significance even in the era of super-fast and ubiquitous Internet. At least, search engines still take it into account.
Reduced the load on the main thread
The main thread involves loading and displaying the page, as well as interacting with the user. This means that until the page loads, the user will not be able to fully interact with it. In order to reduce the load on the main thread, we also optimized CSS and JavaScript. They are usually the main consumers that create the load. Without their optimization, noticeable acceleration is often impossible.
Attention was paid to a number of other works
We set up efficient image encoding, making image processing faster, and started using passive event listeners to improve scrolling performance, making user interaction with the site faster via mouse.
We explicitly set the width and height attributes
Some images on the Customer's website "jumped", changing their location during the loading process of the web resource. This was due to the fact that the system needs to calculate the parameters of the place required to display the image. This is why the width and height attributes should be used - they allow you to avoid this. In fact, not everyone pays attention to this. But we are ardent supporters of maximum web performance and consider this important. After all, "jumping" images and formatting that is corrected during the loading process are unacceptable from the point of view of usability.
Configured to show all text while loading web fonts
Many users skim content very quickly. It is important that texts are shown to the visitor immediately. And on the Customer's website, some texts were not shown until the fonts were loaded.
Reduced the impact of third-party code
Third-party code is something that is not directly related to the site structure. This includes social media buttons, transitions, trackers, advertising, analytics, etc. As it turned out during the audit, the developers treated this issue rather frivolously.
In general, such a problem often arises when the administrator whatsapp number uk independently tries to make the web resource more efficient and adds the necessary codes without knowing how to do it correctly.
Set rules for efficient use of cache for static objects
We carefully configured the .htaccess file so that static elements are saved in the cache on the user's device. This way, some of the site data will not be downloaded from our service on subsequent visits, but will be loaded directly from the device. Of course, this provides additional acceleration.
Prevented excessive network load
To do this, we carried out a complex set of works, including deep optimization of images, styles, scripts. It should be noted that the factor of excessive network load retains its significance even in the era of super-fast and ubiquitous Internet. At least, search engines still take it into account.
Reduced the load on the main thread
The main thread involves loading and displaying the page, as well as interacting with the user. This means that until the page loads, the user will not be able to fully interact with it. In order to reduce the load on the main thread, we also optimized CSS and JavaScript. They are usually the main consumers that create the load. Without their optimization, noticeable acceleration is often impossible.
Attention was paid to a number of other works
We set up efficient image encoding, making image processing faster, and started using passive event listeners to improve scrolling performance, making user interaction with the site faster via mouse.