- From: Philippe Le Hegaret <plh@w3.org>
- Date: Thu, 25 Jun 2015 07:57:47 -0400
- To: Patrick Meenan <pmeenan@webpagetest.org>
- CC: Eli Perelman <eperelman@mozilla.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On 06/24/2015 07:28 PM, Patrick Meenan wrote: > At least for what I was planning to do with it it wouldn't alter any > behavior. We (and I expect most browsers) track aggregate field metrics > for a bunch of technical metrics to track our performance and guide our > optimization work. None of the standard technical measurements really > mean anything for the user experience (onload, DOM Content Loaded, > etc). A lot of sites have their own custom metrics that they track that > does better tie to the user experience and most that do have a core > "this is the user experience time for this operation". The time to > first tweet and time to first pin were concrete examples that I know of > but just about every major web property has their own. > > What I'd like to do is to be able to collect that in a standard way so > that when we make optimization trade-offs we take the applications > actual experience metrics into account. That does mean that it will > impact decisions that we make about how the browser works but not in the > context of that specific page or page load. With performance observers, this would give you an easier to track those marks, correct? Philippe
Received on Thursday, 25 June 2015 11:57:51 UTC