Ross Harmes at code.flickr.com, Pre-generating Justified Views; re: how they achieved a 7x speed increase in page render times:

The first time you come to any Flickr page, we store the width of your browser window in a cookie. We can then read that cookie on the server on subsequent page loads.

Gotta love a simple solution.

Ross Harmes at code.flickr.com, Pre-generating Justified Views; re: how they achieved a 7x speed increase in page render times:

The first time you come to any Flickr page, we store the width of your browser window in a cookie. We can then read that cookie on the server on subsequent page loads.

Gotta love a simple solution.

A front-end operations engineer would own external performance. […] They own everything past the functionality. They are the bridge between an application’s intent and an application’s reality.
— Alex Sexton, Front-End Ops
What happens if I scroll and I happen to move the mouse at the same time? It’s perfectly possible for me to inadvertently “interact” with an element as I scroll past it, triggering an expensive paint. That, in turn, could push me through my frame budget of ~16.7ms (the time we need to stay under that to hit 60 frames per second). I’ve created a demo to show you exactly what I mean. Hopefully as you scroll and move your mouse you’ll see the hover effects kicking in, but let’s see what Chrome’s DevTools makes of it…
— Paul Lewis writing for HTML5 Rocks, Avoiding Unnecessary Paints