Wednesday, March 23, 2022

Frontend Performance Optimization

The biggest piece of content was the heavy product image, and after the first round of optimization, its load time increased because we load all the images after the page wireframe has loaded. It was decided to separate the first image and send it along with the HTML code generated on the server. And after the browser sees the big picture, the rest of the product gallery is drawn to it. Laravel is used as the backend of the site on the server. The result of this optimization pleased: 55 GPS points.


It would seem that the problem is solved: we managed to do the impossible and combine the impressive functionality of the site with the high speed of its loading. But this result in practice cannot be evaluated anywhere except for good GPS indicators: the visitor of the resource still sees the same staged loading. So maybe it was worth not chasing abstract points, but paying attention to the real needs of users?

In addition, now the marketing department has removed a large banner from the site, and the script for accepting cookies turned out to be the heaviest element. This means that the goal has not yet been achieved and further optimization measures need to be taken.

No comments:

Post a Comment

Frontend Performance Optimization

The biggest piece of content was the heavy product image, and after the first round of optimization, its load time increased because we load...