Giveaway: 2 Free Tickets to Velocity Conference in NY

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!
![Page Visibility API]()
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
![CSS Gradients]()
With CSS border-radius, I showed you how CSS can bridge the gap between design and development by adding rounded corners to elements. CSS gradients are another step in that direction. Now that CSS gradients are supported in Internet Explorer 8+, Firefox, Safari, and Chrome...
![WebKit Marquee CSS: Bringin’ Sexy Back]()
We all joke about the days of Web yesteryear. You remember them: stupid animated GIFs (flames and "coming soon" images, most notably), lame counters, guestbooks, applets, etc. Another "feature" we thought we had gotten rid of was the marquee. The marquee was a rudimentary, javascript-like...
![Redacted Font]()
Back when I created client websites, one of the many things that frustrated me was the initial design handoff. It would always go like this:
Work hard to incorporate client's ideas, dream up awesome design.
Create said design, using Lorem Ipsum text
Send initial design concept to the client...
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