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.
- Speeding Up HTML Parse??? Corbin, James
- Re: Speeding Up HTML Parse??? Igor Vaynberg
- RE: Speeding Up HTML Parse??? Corbin, James
- Re: Speeding Up HTML Parse??? Igor Vaynberg
- Re: Speeding Up HTML Parse??? Igor Vaynberg
- Re: Speeding Up HTML Parse??? Jochen Mader
- RE: Speeding Up HTML Parse??? Russell Morrisey
- RE: Speeding Up HTML Parse??? Corbin, James
