As part of the work done to improve the product editor's performance, we should analyze key metrics for the product editor and find a way to measure them with Playwright.

This is an example.

It’s just a regular playwright E2E test, with the only difference that at the end of the job, we attach the results property to the test info util. The results are just a simple JS object whose keys represent the metric keys and the values, the actual result. You can track as many metrics per file and organize these specs as needed.

More context here: p6q8Tx-3Z2-p2

This issue aims to create some E2E tests to observe the impact that the PRs we make during the regular cycle have on the product editor's performance. With that information, for instance, we will be able to know about a performance drop after merging a problematic PR.