public marks

PUBLIC MARKS from dzc with tag performance

2016

High Performance Browser Networking (O'Reilly)

by 1 other
This book is required reading for anyone who cares about web performance; it's already established as the go-to reference on the topic. —Mark Nottingham (IETF HTTPBis Chair)

2014

2013

Speedup Symfony2 on Vagrant boxes (VirtualBox)

by 1 other
Some tips for making Symfony2 faster on Vagrant + VirtualBox

Browser Diet

by 3 others
How to lose weight (in the browser) And what if we got together a bunch of experts who work on large sites to create a definitive front-end performance guide?

Web Application Load Testing Tools For API Endpoints With loader.io

by 1 other
A load testing service that allows you to stress test your web-apps/apis with thousands of concurrent connections.

2011

2010

Indicateurs Clé de Performance des sites web

La Bible des Indicateurs Clé de Performance est un ouvrage original d'Eric T. Peterson sous le titre The Big Book of Key Performance Indicators.

High Performance Web Sites :: Browser Performance Wishlist

What are the most important changes browsers could make to improve performance? This document is my answer to that question. This is mainly for browser developers, although web developers will want to track the adoption of these improvements.

LABjs :: Loading And Blocking JavaScript

by 2 others
LABjs (Loading And Blocking JavaScript) is an open-source (MIT license) project. on-demand JavaScript loader, capable of loading any JavaScript resource, from any location, into any page, at any time. LABjs by default will load (and execute) all scripts in parallel as fast as the browser will allow. However, you can easily specify which scripts have execution order dependencies and LABjs will ensure proper execution order. This makes LABjs safe to use for virtually any JavaScript resource, whether you control/host it or not, and whether it is standalone or part of a larger dependency tree of resources. It uses an expressive, chaining API to specify which scripts to load, and when to wait ("block"), if necessary, for execution before proceeding with further execution.