The advantage with WebSockets (over AJAX) is basically that there's less HTTP overhead. Once the connection has been established, all future message passing is over a socket rather than new HTTP request/response calls. So, you'd assume that WebSockets can send and receive much more messages per unit time.

Itw by M. Hendrickson Current state of the Performance and Operations market. Terms, semantics and DevOps, are we splitting hairs? What do performance people do on a daily basis? Do you need to tradeoff anything to get better performance? Are most websites acceptable when it comes to speed? Measuring slowness -- clarified and demystified Where do you find performance monitoring tools? How do you know if you have a fast enough web site? Does Mobile disrupt your quest for high performance? Does HTML5 add any more complexity challenges to high performance web sites? Wrap up and discussion of Velocity Conference

A month ago, we wrote about how the Home Depot improved their web performance through a major "Perflift". Today, we want to congratulate "l'equipe" at Le Monde for improving their website. While The New York Times is the number one newspaper in US, Le Monde is the number one news source in France and for French speakers around the world.

The 7 Deadly Mistakes That Make Websites Slow [Infographic] There are several common mistakes people make that slow down their website. Are you making any of them? See the mistakes below (and how you can fix them if you are making them!)

We've come quite a long way since introducing RUM about a year ago. Being the first app performance company to build real user monitoring as a core, native feature of application performance management, we are currently monitoring about 750 million page views a day, 5 billion a week and 20 billion a month for 20,000 active accounts.

When I was at DrupalCon Denver I suggested that all production JavaScript should be minified. This seemed like something simple that I wouldn't get any push back on. After all, the major JavaScript packages do it and the performance recommendation tools all recommend it. I was wrong.

This week begins face to face meetings at the IETF on how to approach HTTP 2.0 and improve the Internet. How the industry moves forward together on the next version of HTTP - how every application and service on the web communicates today - can positively impact user experience, operational and environmental costs, and even the battery life of the devices you carry around.

My previous blog post, Cache them if you can, suggests that current cache sizes are too small - especially on mobile. Given this concern about cache size a relevant question is: If a response is compressed, does the browser save it compressed or uncompressed? Compression typically reduces responses by 70%.

A recent article by John Naughton has sparked a debate inside the web design and web development community. Are designers, with their image heavy designs, ruining the web? The answer is yes, but its not why you think. It's not because designers use big images or even that they use a lot of images.