Group items tagged

"At Artsy we've been building Node.js applications that share code and rendering between the server and browser. We've seen many benefits from this - pages load faster, we can optimize SEO, developers are more productive, and JavaScript coding is just an overall better experience."

"WebPagetest will now expose any User Timing marks that a page records so you can use the same custom events for your synthetic test measurement as well as your Real User Measurement"

I shouldn't need to explain the importance of front-end performance at this point; after two previous posts, 9 Ways to Optimize Your Front End Performance and...

"Here are some common mistakes we see on smartphone-optimized websites and how to avoid them."

pngquant 2 applies vector quantization algorithm to optimise image colour palette with the least amount of loss as possible.

"Google mobile search is getting faster - to be exact, 200-400 milliseconds faster! We are gradually rolling out this improvement to all browsers that support the attribute (currently, mobile Chrome and Safari)."

"while 75% of the top 100 retail websites employ a Content Delivery Network (CDN), the median home page takes a full second longer to become interactive than the median page that does not use a CDN"

When we look back over the history of web performance we see a heavy focus on reducing the number of requests and getting files to the browser quickly. Our platform has changed a lot, and while optimizing for network performance remains a crucial part of our jobs, we now have to broaden our performance horizons. Our users also expect smooth scrolling, animations and interactions, even on mobile devices. In short we need to deal with not just how quickly our sites and apps load, but also how quickly they run. [video] In this session Paul takes a lightning tour of how Chrome converts the DOM into pixels, see how our code affects its workload, and arrive at a modern workflow for finding (and eliminating) rendering bottlenecks.

Le fameux "+500ms -> -20%" de Google search

A "webfont" is a set of resources, not just a single download. A single resource that includes all stylistic variants, which we may not need, plus all the characters, which may go unused, would simply be too large - tens of megabytes for a font with good unicode and stylistic coverage!

"Tracked by redirections from a simple tweet"

Or why it is better to use the `script[async]` attribute to fasten page load time.

RWDPerf - Performance testing tool for Responsive web designs.

"A bookmarklet to create a front-end performance heatmap of resources loaded in the browser using the Resource Timing API."

Support de présentation de Gonzalo Ruiz de Villa à l'occasion de #spainjs 2013