Re:Front-end performance heatmap bookmarklet
by smcnally on Saturday October 11, 2014 @03:36PM
(#8443217)
Agreed that Chrome dev tools are awesome for devs. A heatmap like this is much more approachable to a significant portion of the dev-related population. It will be useful and time-saving when you're explaining to a product person, e.g., what including that giant image element mid-page will do to UX; when explaining to biz dev what your concerns are re including "just two lines of js" for a partner widget in the right rail; when explaining to rev ops why the new programmatic partner is sucking the wind out of things.
these data are available in dev tools; this can help tell a story without you or me having to write that story every time.
Re:Front-end performance heatmap bookmarklet
by chrisbalt on Saturday October 11, 2014 @02:27PM
(#8442967)
Kiro, you can view this information and more in the "Network" tab of the Developer Tools in Chrome. Make sure the red "Record Network Log" circle is enabled, refresh the page (suggest you also check the "Disable cache" checkbox) and you should see a stream of everything loading on the page in great detail, including the timing data, which is painted on the page with this tool.
Re:Front-end performance heatmap bookmarklet
by givehimagun on Saturday October 11, 2014 @09:10PM
(#8443953)
Looks like Firefox 32 does not have the Resource Timing API on by default. They have a note in the readme to check caniuse.com and then caniuse.com mentions you have to turn on the API in 32 in about:config.
these data are available in dev tools; this can help tell a story without you or me having to write that story every time.
Hope this helps.