O'Reilly's Velocity Conference is quickly approaching -- it's September 15-17 in beautiful New York. As a follow up to last month's post, I wanted to make sure people knew I had 2 more tickets left to give away to this epic front-end performance conference!
If you're hoping to win a free ticket to Velocity NY, please post a comment below citing your favorite client-side performance testing tool. Winner will be selected tomorrow!
I spent a few months experimenting with different approaches for writing simple, elegant and maintainable media queries with Sass. Each solution had something that I really liked, but I couldn't find one that covered everything I needed to do, so I ventured into creating my...
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
MooTools 1.3 was just released and one of the big additions is the Browser object. The Browser object is very helpful in that not only do you get information about browser type and browser versions, you can gain information about the user's OS, browser plugins, and...
"Copy to clipboard" functionality is something we all use dozens of times daily but the client side API around it has always been lacking; some older APIs and browser implementations required a scary "are you sure?"-style dialog before the content would be copied to clipboard -- not great for...
My favourite client side performance testing tool is GTMetrix a web based performance tester. Link: http://gtmetrix.com/
webpagetest.org
I use mocha, I especially started using mocha with co and –harmony: https://github.com/visionmedia/co/blob/master/test/arrays.js
Oops I read that as testing tool. I use jsperf for quick tests and devtools for anything heavier
Profiling in the Google Chrome Console mixed with PageSpeed Insights are really useful for performance testing.
For testing I use the Chrome Dev Tools and a gulp task PageSpeedTest
I live in NYC area and I really want to go to this event… And I would be happy to share a blog post talking about the event…
People. You can’t beat the frustration of a potential user in the testing phase to motivate you to make things faster.
Chrome Dev Tools and New Relic
Chrome’s Dev Tools primarily.
Hey David,
My favourite client side performance testing tools are
1- Chrome Dev Tools
2- Gtmetrix
3- Pingdom (to some extent)
4- & sometimes New Relic helps a lot.
Chrome Developer Tools is the best without any doubts
I do not have a favorite tool as I am new to the testing and DevOps world. I would greatly benefit from the tickets by jump starting my learning as I am already passionate about learning these skills. Please help a developer discover the way! I will return the favor!
I use Chrome dev tools