3 ms·
Surely the first bit of advice in any post about analysing website performance should be: USE WEBPAGETEST It gives you access to everything Chrome dev tools do
by philbo 11y ago
Surely the first bit of advice in any post about analysing website performance should be: USE WEBPAGETEST
It gives you access to everything Chrome dev tools do, plus so much more:
* speed index as a metric for the visual perception of performance
* easy comparison of cached vs uncached results
* operating on median metrics to ignore outliers
* side-by-side video playback of compared results
* different user agents
* traffic-shaping
* SPOF analysis
* a scriptable API
* custom metrics
I could go on. There's a lot of excellent performance tooling out there but WebPageTest is easily the most useful from my experience.
- _mtr 11y ago> It gives you access to everything Chrome dev tools do, plus so much more: Can WebPageTest (I've never heard of this tool) reach pages that require authentication? http://www.webpagetest.org/ http://www.webpagetest.org/
- jakub_g 11y agoIt's open source, you can build your own http://www.webpagetest.org/about http://www.webpagetest.org/about
- philbo 11y agoIt can, using either basic auth or by scripting submission of login forms. Probably obvious, but you should avoid doing it from one of the public instances. Building your own private instance is as easy as spinning up a prepared EC2 image, or if you have a couple of hours to fiddle about you can do it from scratch on any Windows machine. Details here: https://sites.google.com/a/webpagetest.org/docs/private-instances https://sites.google.com/a/webpagetest.org/docs/private-inst...