I just checked the site out using YSlow and it scored pretty well. However, it very quickly pointed out the problems:
* Add expires headers (this is why your images are not being cached) * Compress components using GZip * Configure Entity Tags (ETags) Check your IIS settings for expires headers and gzipping of text/js, text/css and text/html. Scoring well on the ETags test is a little esoteric though; basically, in IIS, you need to add a custom header value named 'ETag' with a blank value, scrapping the ETag - basically they're more effort than they're worth for the client, so Yahoo advise they be turned off. Once you've fixed those problems, your YSlow score will be excellent and the site will be performing very well from a front end point of view (depending on your server, of course) and you can stop using CF to serve images (a really horrid idea). As for the huge background image - I quickly knocked it down to 85% quality in The GIMP and it shrunk the image size by 75%. The difference in the image was barely noticeable. After you've done that (or perhaps a little less lossy if the designer can't bear it), you can then use YSlow once again to compress it as far as it will go without losing any image quality - just go to the Components tab, find the background image and then click the smush.itlink. I'll repeat: install and use YSlow and Firebug add-ons for firefox, they are revelatory! Dominic 2009/12/7 Jessica Kennedy <[email protected]> > > Oh! Sorry, I'm testing on IE 7. Sry if this was ot-- I was thinking I > would probably need to implement a <cfheader> somehow to get the browser to > cache images, i was just stuck on how to change the http header for the > images that are loades... so not really an issue with CF, just one I thought > it could fix... but apparently not =( > > appreciate the help regardless, though! > > >>> nothing... really? > > > >Yes really. Not to be a jerk or anything but this is OT. You might be > better > >of hitting up a UI list as this is not a cf issue but a browser issue or > >even worse a (shudder) IE issue. You have not told us what version of IE > you > >are using so we can check it. That is a critical piace of info. There are > 3 > >versions of IE in common use these days 7, 8 and the dreaded 6. > > > >I know, cross browser UI can be a total pain... wait strike that... a > LIVING > >NIGHTMARE when it comes to IE. So I feel your pain. > > > >It literally could be anything. I would start commenting out parts of the > >page until you find the offending piece of code. I have had hidden form > >fields and JS blocks throw off page elements before. I would also try > using > >other roll over techniques (There are dozens) and see if that fixes the > >problem. > > > >HTH and Godspeed. > > > >G! > > > > > >On Sat, Dec 5, 2009 at 1:14 PM, Jessica Kennedy < > >[email protected]> wrote: > > > >> > >> nothing... really? > >> > >> > >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:328932 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
