Start of main content
As a rule, web performance in the minds of engineers is associated with the initial stage of the page life cycle: before the load event. The fact that only one of the five Web Vitals metrics is interested in a page after it is loaded contributes to this.
It turns out that the majority of benchmarks have blind spots and find far from all the retarded areas of the code (and, it turns out, the interface). As a result, we have to look for performance problems with a poorly developed toolkit and not with the most sophisticated algorithms.
In this talk we will analyze how Chrome DevTools can help in this situation and learn how to identify resource-intensive code sections.