On 8/27/07, Ben Bangert <[EMAIL PROTECTED]> wrote: > > That shouldn't actually be a problem as they use ETag's instead. The > Yahoo tool is not perfect, and does have a few inconsistencies on > some things.
It seems to be not functioning optimally: I tested reloading my front page and looking at the traffic with Live HTTP Headers. It always wanted to reload the images and javascripts. Also the Proxy I use seemed to produce misses for all the files every time. That will definitely make an impact on speed to an extent. I'd > suggest having your front-end app handle gzipping. I use Apache in > front of Paster, which gzip's the images when I add the following > (Apache 2): I don't use a front-end app at the moment. The paste.gzipper is not supported by the Pylons at the moment? > The most substantial speed boost I got on the PylonsHQ site, was from > reducing the CSS from 3 stylesheets to 1 because each CSS load goes > one at a time, blocking parallel downloads and anything else until > the CSS is done. Moving the JS to the bottom also resulted in > noticeable improvement since it loaded just once at the end instead > of blocking parallel page component loading. My problem are the large JS libs I use, from which I need only some simple function for each page. Too bad they are not modularized so I could just pick the functions I really need easily. They could really benefit from gzipping. -- --PJ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
