a) Read the speed tracer output, if the time is spent with the redirect or
loading the actual markup it will tell you.
b) HTML rendering in the browser is influenced by the markup and ajax. Read
the speed tracer output and it will tell you where the time is spent. It's
most likely not wicket that costs the initial 30 second delay but some
resource taking long to load, an AJAX component doing its magic ...
But that's all client(browser)-side stuff.

Reply via email to