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
To: users@wicket.apache.org
Subject: RE: Speeding Up HTML Parse???
Before spending a lot of time trying to debug client-side performance,
be sure that the problem is on the client side, and not the server. A
lot of performance problems I see on my project arise from user code on
the server side
-
From: Jochen Mader [mailto:pflanzenmoer...@gmail.com]
Sent: Thursday, February 25, 2010 4:48 AM
To: users@wicket.apache.org
Subject: Re: Speeding Up HTML Parse???
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
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
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
[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
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
