Comments on: Speed Tracer – visibility into the browser

By: Paul Vincent

Paul Vincent — Tue, 16 Nov 2010 09:09:41 +0000

Hi,

After I clicked the button to install Speed Tracer, where do i save the extension_0_18.crx to make it run with Chrome?

thanks,

By: Miller

Miller — Fri, 15 Jan 2010 02:46:33 +0000

Hi, I tried Speed Tracer this morning,but it seems work not well. Firstly,when switch to Network(resources), there is nothing there, but i did opened a website(map.google.com). Secondly,Sluggishness(events) seems include incompelte information, for example there is no Script Evaluation and DOMContentLoaded.

I have read the Gettting Started document many times but found nothing helpfull, could you tell me what’s the reason?
Thanks a lot!

By the way, my chrome version is “4.0.295.0 dev”,download from your suggest site and i do add the flag “–enable-extension-timeline-api”.

By: Elijah Lynn

Elijah Lynn — Sat, 19 Dec 2009 18:43:33 +0000

Yeah, Google is on FIRE!!!

And I am loving it!

Go Google!

By: Kyle Simpson

Kyle Simpson — Fri, 11 Dec 2009 10:21:29 +0000

When I run this on a test page (which loads just a sentence of text and 2 images (+ some invisible scripts in the background), I see the log include like 30 or 40 “paint”s, even though the page renders right away and basically doesn’t change. Any idea why that would be?

By: Steve Souders

Steve Souders — Thu, 10 Dec 2009 20:49:22 +0000

@Stoyan: The SPDY announcement was a few weeks ago, but certainly has the potential to be the most impactful performance announcement from Google.

By: Stoyan

Stoyan — Thu, 10 Dec 2009 20:13:16 +0000

That’s great stuff!

I think you forgot to mention SPDY in the list of cool performance stuff from Google lately :)

By: HB

HB — Thu, 10 Dec 2009 19:16:44 +0000

I was already excited about this when I saw it on Google’s blog yesterday – thanks for the more detailed look! Agreed that an overall page pie chart would come in handy for quickly spotting possible problem areas.

Normally I use Firebug with YSlow for analyzing performance, component size and caching, tracking headers, etc. I have Page Speed for Firebug installed but haven’t found it as overall useful as YSlow. This, however, will definitely get me opening Chrome during optimization.

By: Wim Leers

Wim Leers — Thu, 10 Dec 2009 18:03:16 +0000

I don’t have the time to read the entire post at the moment, but: 1) WOW, 2) Google has indeed been kicking web performance ass as of lately!

By: Scott Schiller

Scott Schiller — Thu, 10 Dec 2009 18:00:48 +0000

Yep, this is good stuff; nice to see parse, reflow and JS timing all included in detail. Digging into the data and optimizing will take a bit of detective work, but the more people care about making efficient code, so much the better.