On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
>
> We use
Just FYI - New Relic does a fantastic job of browser speed graphing - but
it is an expensive product.
On Fri, Jul 6, 2012 at 6:14 AM, Larry Martell wrote:
> On Thu, Jul 5, 2012 at 10:48 PM, Andy McKay wrote:
> >> I'm trying to use the Navigation Timing package to measure how long a
> >> page tak
On Thu, Jul 5, 2012 at 10:48 PM, Andy McKay wrote:
>> I'm trying to use the Navigation Timing package to measure how long a
>> page takes to be rendered.
>
> So you don't want to include all the lookups? Just the "rendering" part?
Not sure what you mean by "lookups." I want to include everything
> Thanks Andy. Super cool, and pretty much just what I was looking for.
> Seems to work fine in FF and Chrome, but in Safari I don't seem to
> have access to the performance.timing data. Should that be there or do
> I have do something to load or enable it?
Sadly, Safari does not support this :( Y
> I'm trying to use the Navigation Timing package to measure how long a
> page takes to be rendered.
So you don't want to include all the lookups? Just the "rendering" part?
> So that would be loadEventEnd-responseEnd,
> however I am finding that loadEventEnd is always 0 for me, even though
> I a
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
>
> We use
Look at Boomerang:
http://lognormal.github.com/boomerang/doc/
John
On 25/06/12 12:34, Larry Martell wrote:
> This is not strictly a django question, but I'm hoping someone here
> has solved this and can help me. I have a client that has a django app
> that collects a bunch of server side statist
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
>
> We use
I stumbled upon this while looking about this timing stuff:
http://www.html5rocks.com/en/tutorials/webperformance/basics/
Seemed slightly more verbose than W3C formal documentation.
On Tue, Jun 26, 2012 at 10:38 PM, Melvyn Sopacua wrote:
> On 26-6-2012 5:04, Andy McKay wrote:
> >> Now they want
On 26-6-2012 5:04, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
Wow, really nice. Can't
On Mon, Jun 25, 2012 at 9:04 PM, Andy McKay wrote:
>> Now they want me to add to that how long
>> the browser takes to render the page after it gets the data.
>
> You can use the navigation timing API:
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
>
> We use
On Mon, Jun 25, 2012 at 6:56 AM, Melvyn Sopacua wrote:
> On 25-6-2012 14:00, Larry Martell wrote:
>> On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
>> wrote:
>>> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
Now they want me to add to that how long
th
> Now they want me to add to that how long
> the browser takes to render the page after it gets the data.
You can use the navigation timing API:
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
We use this in conjuction with graphite and django-statsd to produce
g
On 25-6-2012 14:00, Larry Martell wrote:
> On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
> wrote:
>> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>>>
>>> Now they want me to add to that how long
>>> the browser takes to render the page
>>
>>
>> How would server cod
I am no django expert ... but I guess you can do following ...
Get the timestamp when request first reaches your server
It does some processing
returns output to browser
use javascript to check if DOM loaded and get the timestamp
calculate time diff and send to the server again to save it.
Don't
On Mon, Jun 25, 2012 at 5:56 AM, bruno desthuilliers
wrote:
> On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>>
>> Now they want me to add to that how long
>> the browser takes to render the page
>
>
> How would server code ever know this ?
My assumption is that it would b
On Monday, June 25, 2012 1:34:08 PM UTC+2, larry@gmail.com wrote:
>
> Now they want me to add to that how long
> the browser takes to render the page
>
How would server code ever know this ?
--
You received this message because you are subscribed to the Google Groups
"Django users" group
17 matches
Mail list logo