PUBLIC MARKS with tags browser & performance

This brand new specification defines an interface for web applications to access timing information related to navigation and elements. When implemented, this will help track web pages frontend performance.

Some rules for rendering efficiently CSS : ID, class and then universal, plus other tips

Browserscope is a community-driven project for profiling web browsers. The goals are to foster innovation by tracking browser functionality and to be a resource for web developers.

A complete focus on web browser performance-related questions, from a lot of point of views : javascript, network, painting, caching, client-side database, etc.

Internet Explorer 7 scores an abysmal 90522ms. (...) IE8-beta2 scored at 9542ms. But, for reference, in the same virtual environment Firefox "Minefield" was still able to pull off 1873ms. So, as while still no where near as fast as the other guys, IE8 is lightyears ahead of IE7 in its javascript performance.

The universal, high-speed-everywhere web isn't quite a reality yet, as anyone who's used a relative's dial-up or a seriously weak airport connection can testify to. Web page re-formatting tool Finch gives you just the text, ma'am, from any site you plug into its address box, stripping Flash, JavaScript, stylesheets, and even images from the layout. Tools like this often crop up for mobile phones, such as Google's Mobilizer, but Finch is made for the desktop browser. Some sites will work better with their graphical navigators removed than others, of course, but for anyone stuck with a fist-poundingly slow connection, or paying for every megabyte, Finch is a great bookmarket to keep handy.

A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses — like HTML pages, images and files (collectively known as representations) — for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again.

Caching is a great example of the ubiquitous time-space tradeoff in programming. You can save time by using space to store results. In the case of websites, the browser can save a copy of images, stylesheets, javascript or the entire page. The next time the user needs that resource (such as a script or logo that appears on every page), the browser doesn’t have to download it again. Fewer downloads means a faster, happier site.

Vey useful links for cache control and browser behaviors * Explain of cache control in detail (very nice article! ) http://betterexplained.com/articles/how-to-optimize-your-site-with-http-caching/ * The State of Browser Caching: http://www.mnot.net/blog/2006/05/11/browser_caching * XMLHttpRequest caching: http://www.mnot.net/javascript/xmlhttprequest/cache.html

Caching is a great example of the ubiquitous time-space tradeoff in programming. You can save time by using space to store results. Fewer downloads means a faster, happier site.

If you're a frequent visitor to code.google.com for product updates and reference materials for Google APIs you're working with, you might have noticed that the page loading time (or page rendering time depending on how you see it) has reduced in varying

This is the second in a series of articles describing experiments conducted to learn more about optimizing web page performance. You may be wondering why you’re reading a performance article on the YUI Blog. It turns out that most of web page performance is affected by front-end engineering, that is, the user interface design and development.

# Prefetch Links : Dynamic speed increases can be obtained # Tweak Network Fasterfox allows you to tweak many network and rendering settings