0 
0 It is not always easy to troubleshoot ADF performance problems – it is often complicated. Many parts needs to be measured, analyzed and considered. While looking for performance problems at the usual suspects (ADF application, database, network), the real problem can also be found in the often overlooked browser load time. The browser load time is just an important part of the HTTP request and response handling as is the time spent in the applicationserver, database and network. The browser load time can take a few seconds extra time on top of the server and network process time before the end-user receives the HTTP response and can continue with his work. Especially if the browser needs to build a very very ‘rich’ ADF page – the browser needs to build and process the very large DOM-tree. The end-user needs to wait then for seconds, even in modern browsers as Google Chrome, Firefox and Microsoft Edge. Often this is caused by a ‘bad’ page design where too much ADF components are rendered and displayed at the same time; too many table columns and rows, but also too many other components can cause a slow browser load time. This blog shows an example, analyses the browser load time in the ADF Performance Monitor, and suggest simple page design considerations to prevent a large browser load time.
Read more on adfpm.com – our new website on the ADF Performance Monitor.
Related posts:
ADF Performance Monitor: Measuring Network Time to Browser and Browser Load Time 
ADF Performance Monitor – Major New Version 7.0 
Troubleshooting ADF ViewObject Range Paging Issues 
ADF Performance Monitor: Support for EJB/JPA (EclipseLink) 
ADF Performance Monitor brings performance improvements and Insight at Intris
