"Another interesting finding is likely to annoy some developers. When asked “What is the most common problem you’ve encountered accessing websites or applications on your mobile phone?”, respondants answered “Slow to load” (38%), “Crashed/froze received an error” (18%), “Formatting made it difficult to read and use” (15%).

This tells us that speed is more important than aesthetics. So perhaps some of the time and effort put into media queries, viewports, avoiding scrolling, line length would actually be better employed reducing HTTP requests and optimising so that websites are perceived to render faster.

Certainly, if you’re using gigantic libraries and frameworks to speed up your development, you might pause to wonder whether trading off faster development for slower loading is a trade-off you want to make, given that most users find speed to be the main problem – and problems drive consumers away and potentially into the arms of competitors."

"Developers want to build a great user experience on mobile. They want the experience to be fast, easy, and rewarding for the user. However, because of a mix of performance issues, broken features, or worse—missing features, this is quite difficult with the current state of the mobile web.

The best way to fix this is by focusing on those features that will actually help developers build high-quality apps.

And since the web is constantly evolving, we're taking a versioned approach to this effort, starting from the basics and building up, as illustrated by “Rings”."

"The implication: high performance equals high tolerances, which means your entire system must be designed to exacting standards."

Great explanations of Apache's prefork and working modules and how they apply to mod_php and mod_python.

"Even though these resources have a future Expires date, clicking the Reload button tells the "browser to double-check that the cached components are up-to-date, hence the conditional GET request.