As you can see it took 2.14 seconds for browser to download and render page but out of that only 267 milliseconds are spent in getting the HTML for the page inside portal and rest of the time is spent in downloading and executing other 12 resources.
Problem with WebSphere Portal performance
Recently i was trying to find out why my portal pages are slow, so i used firebug to see where my browser is spending most of the time and it turned out that less than 30% of time is spent inside portal engine, for generating HTML markup of the page and major chunk of time is spent in downloading and executing resources such as images, css, JavaScript.
As you can see it took 2.14 seconds for browser to download and render page but out of that only 267 milliseconds are spent in getting the HTML for the page inside portal and rest of the time is spent in downloading and executing other 12 resources.
As you can see it took 2.14 seconds for browser to download and render page but out of that only 267 milliseconds are spent in getting the HTML for the page inside portal and rest of the time is spent in downloading and executing other 12 resources.
Subscribe to:
Post Comments (Atom)
1 comment:
Thanks for info....
SEO Company in Bangalore
Post a Comment