On Wed, Feb 24, 2010 at 2:14 PM, Corbin, James <[email protected]> wrote: >For example, we have editors that take upwards of 30 seconds to render >initially.
what is the processing time of the entire request on the serverside? is it 30 seconds??? -igor > Subsequent renders are obviously quicker. > > I guess what I am trying to say, are there any best practices for reducing > the initial load time of pages. > > > > -----Original Message----- > From: Igor Vaynberg [mailto:[email protected]] > Sent: Wednesday, February 24, 2010 2:58 PM > To: [email protected] > Subject: Re: Speeding Up HTML Parse??? > > On Wed, Feb 24, 2010 at 1:26 PM, Corbin, James <[email protected]> > wrote: >> I'm profiling our Wicket Application using Google's Speed Tracer Plugin >> (nice plugin). >> >> >> >> The profiling tool is showing most of the time spent in two areas, >> >> >> >> 1) Parsing HTMlL > > this measures the browser's speed not wickets.... > > besides, where does most of the time browserside should go? shouldnt > it be parsing html? thats what browsers do... > > -igor > > > >> >> 2) Javascript Valuation (mostly with YUI). >> >> >> >> What are some of the best practices around developing code that >> minimizes the impact of parsing HTML in Wicket? >> >> >> >> We haven't had a lot of time to optimize our code and now are starting >> to look at that aspect of our application. >> >> >> >> Thanks, >> >> >> >> J.D. >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
