For those of you who are familiar with html and css and who have used the PB only for speed reasons, I recommend that you take a different path. For each page exists in the database the corresponding html. And always for each page there is a css file that you can identify with the browser debug. If you copy that css in custom.css and the content of the page taken from the database in an article you will not see any difference in aesthetics or loading. In my case I had three PB "templates" and therefore three css files to copy in custom.css. I was worried about the slowness that might ensue. Actually doing tests with the core web vitals I have better results in this way than the pages with page builder. Also because in this way I was able to eliminate PB and upgrade to J4. If you want to make a better job with an editor you can clean custom.css deleting the doubled code.
When I discovered that what I have in the pages depends on the servers of another entity I had no doubts, I am happy with the choice made. To those who are able to edit in html then I recommend this way.
Only the animations don't work, but adding the AOS library you can get the same results and better, indeed there are more options. In one morning I rebuilt a site where there were 24 pages made with PB including animations, it's a pretty fast procedure.
