Yes Igor, I understand that, but some of our display pages initially take a very long time to initially render. For example, we have editors that take upwards of 30 seconds to render initially. 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:igor.vaynb...@gmail.com] Sent: Wednesday, February 24, 2010 2:58 PM To: users@wicket.apache.org Subject: Re: Speeding Up HTML Parse??? On Wed, Feb 24, 2010 at 1:26 PM, Corbin, James <jcor...@iqnavigator.com> 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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
