Sebastian Helzle

I'm currently working on dropping the script tags for content nodes completely in https://github.com/neos/neos-ui/pull/3770

I'm making good progress after I realised that I use a similar system in flowpack/neos-debug: 

I'm not sure how breaking this could be right now, therefore draft for now ;) @grebaldi I remember you started working on a replacement for the script tag, so your...

Some test results with 82 nodes (haven't found a good way to measure time to interactive with the iframe): ## With Script Tag + with full Properties Document size: 245KB...

I tested a variant of this change in my customers project and the document size was reduced from 1.8mb to 1.2mb. Without any nodedata it's 700kb. So I think we...

OK optimised a bit more and completely removed nodedata from the guest frame: ## Without NodeData in augmenter Document size: 108KB / 7.5KB (~44%) Document rendering time: ~123ms (~55%) Finish:...

Yes of course. At the end we need the same amount of nodedata. But we kill the overhead of the function calls and document parsing. Even if the combined loading...

@bwaidelich I tested the loading performance a while yesterday with "Fast 3G" connection + Caching in my local Dev Context. Result: The page loads much faster, but if you try...

Realised today this will also fix the issue https://github.com/neos/neos-development-collection/issues/2988 with the Fusion Augmenter when augmenting a single content element. Previously it added another tag as it counted the element itself...

The two main performance hogs which makes the async request for the nodedata slow is in `\Neos\Neos\Ui\Fusion\Helper\NodeInfoHelper::renderChildrenInformation` which queries each nodes children twice. In my tests this takes at least...