We always want to get both speed and functionality at the same time, but such a requirement contains an internal contradiction. If you want a race car, we remove everything we can to make it as light as possible. There is only room for one pilot and the most necessary structural details. If you need a roomy truck, then you need a large body and a powerful engine. However, the speed of such a car will be an order of magnitude lower than that of a racing car.
Let's see what happens when management demands to combine speed and functionality, using the optimization of the vprok.ru site as an example.
To analyze the effectiveness of optimization, the generally accepted Google PageSpeed (GPS) parameter was used; A score of at least 50 points is considered satisfactory.
First, it was necessary to determine which elements on the page are the heaviest. They turned out to be pictures of goods, and it was decided to make them loadable via AJAX requests. But as a result, the size of the JS scripts that provide these postloaders has grown.
A detailed study of Google's algorithms for determining site speed showed that there are two fundamental metrics: First Contentful Paint (FCP; rendering time for the first content-significant element) and Largest Contentful Paint (LCP; rendering time for the largest content element).
No comments:
Post a Comment