Guymon

CSS Performance

Juriy Zaytsev hat einen sehr ausführlichen Post über CSS Profiling und Performance geschrieben.

The fastest rule is the one that doesn’t exist. There’s a common strategy to combine stylesheet “modules” into one file for production. This makes for one big collection of rules, where some (lots) of them are likely not used by particular part of the site/application. Getting rid of unused rules is one of the best things your can do to optimize CSS performance, as there’s less matching to be done in the first place. There are certain benefits of having one big file, of course, such as the reduced number of requests. But it should be possible to optimize at least critical parts of the app, by including only relevant styles.
This isn’t a new discovery by any means. Page Speed has always been warning against this. However, I was really surprised to see just how much this could really affect the rendering time. In my case, I shaved ~200-300ms of selector matching — according to Opera profiler — just by getting rid of unused CSS rules. Layout and paint times went down as well.

Die meisten Tips beziehen sich zwar auf große, komplexe One-Page-Apps, aber spannend ist das trotzdem.

jQuery Performance

Scott Kosman hat einige leicht umzusetzende Performance Tips für jQuery zusammengesucht.

Thankfully, there are a few very simple things anyone can add into their jQuery workflow that can clear up a lot of basic problems. When undertaking code reviews, three of the areas where I consistently see the biggest problems are: inefficient selectors; poor event delegation; and clunky DOM manipulation. We’ll tackle all three of these and hopefully you’ll walk away with some new jQuery batarangs to toss around in your next project.

Defense against external resources failing

Rich Thornett erklärt wie man externe Ressourcen so einbindet, dass sie nicht die eigene Seite beeinträchtigen wenn sie nicht geladen werden können.

The Deck network, which delivers advertising to some of the most popular web design and culture destinations, was down for about thirty minutes. During this period, most partner sites running ads from The Deck could not be viewed as result.

I’ll discuss outages like this and how to defend against them. (…) the issues in play are applicable to any web widget you might add to your site to display third-party content.

Performance: Delayed Content

Paul Hammond zeigt wie man die Performance einer Webseite mit “Delayed Content” deutlich verbessern kann.

Jeremy Keith hat diesen Gedanken aufgegriffen und wendet ihn auf den mobile first Ansatz an.

This technique has consequences for content strategy and information architecture. Instead of thinking about possible page content in a binary way as either ‘on the page’ or ‘not on the page’, conditional loading introduces a third ‘it’s complicated’ option.

This was just a simple example but I hope it illustrates that conditional loading could become an important part of the content-first responsive design approach.

SEO: Page Speed

Bei Alex Graves bin ich auf ein Video von Matt Cutts gestoßen in dem er die Bedeutung der Webseiten Performance deutlich heruntergespielt.

Although there seems to have been a huge push towards looking to reduce the page speed, Cutts revealed that there are only really “one in a thousand” sites that have any issues in relation to their page speed that could be big enough to affect their position within the search engine results, taking away some of the need to have the most efficient site on the internet.

Die Schlussfolgerung des Posts – Google Page Speed Optimisation is a Waste of Time – teile ich zwar nicht, denn eine gute Performance macht Benutzer zufriedener, aber es ist zumindest interessant, um nicht zuviel Energie, aus den falschen Gründen, in einzelne Aspekte der Entwicklung zustecken.