TYPO3 Core

I would say the number of DOM elements is simply owed to the necessary markup for Bootstrap for responsivness.

The number of requests is indeed interesting even though only 75% of data is transferred.

Markus Klein wrote:

I would say the number of DOM elements is simply owed to the necessary markup for Bootstrap for responsivness.

Yes, I posted that data cause the more the DOM elements are the more the UI is laggy. Something to take into consideration designing a ui.
Developers usually have powerful computers while editors usually have entry level ones or worst. The experience of them is different also because of this.

I just hope this bug report can help a little to improve the responsiveness of the BE in future versions or at least to not make the thing worst.

Well, seems you have some knowledge in that area.
Maybe wanna help with those issues?

Sure, I guess that I'm already helping with this bug report and I want to help more.
How can I help further?

If you can fix stuff with specific patches, just push them to our review system.
Also consider getting a Slack account for direct interaction in the typo3-coredev channel. Maybe also raise your findings there, since only a few people will actually stumble over this report here, but Slack has >2000 members.

Hey,
thank you for the tests and numbers.
can you please provide some more information, especially:

- Operating System and version
- Browser(s) and Versions (can you test with some more browsers?)
- Internet connection, Provider, band width?
- hardware of your client: RAM? HDD/SSD? CPU?

It is interesting, because I had some performance tests yesterday in the office of a customer.
Same system, same WLAN, one chrome on windows, the other chrome on Mac OSX. The chrome on the mac was two times faster when reload the complete backend.

OS: Windows 10 (1511 10586.218)
Browser: Chrome 49.0.2623.112 m
Connection: ADSL (Low latency mode), NGI Italia, 7 Mb/s DL - 512 Kb/s
Hardware: 4GB RAM, 128GB SSD, Intel Core M 5Y10

Btw, this is a bug report related more to the responsiveness of the backend than the load time of the BE pages.
I think that we should focus on the resources (CPU/RAM) used to handle all that DOM+Javascript considering that editors usually have pretty outdated and slow machine.