css and images break when enabling compression

2015-03-22 Thread Mark Spence
I am on a windows shared server and I am trying to enable compression. I am trying this, which I found online, in my web.config: httpCompression directory=%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files scheme name=gzip dll=%Windir%\system32\inetsrv\gzip.dll

Re: css and images

2005-03-15 Thread Larry C. Lyons
I haven't noticed any on my personal site (http://www.lyonsmorris.com/). Right now its mix of css and older traditional tables based layouts. Both layouts share the same style sheets, and from what I've seen unused styles with images do not slow down page loading any more than unused styles

Re: css and images

2005-03-15 Thread Phill B
Thats what I thought but the site websiteoptimization.com counts it against you when you do a speed report. :-\ Phillip B. On Tue, 15 Mar 2005 08:57:53 -0500, Larry C. Lyons [EMAIL PROTECTED] wrote: I haven't noticed any on my personal site (http://www.lyonsmorris.com/). Right now its mix of

Re: css and images

2005-03-15 Thread Larry C. Lyons
It must be because of the size of the css file perhaps? Have you tried the speed report with unused css styles both with and without image references? It would be interesting to find out. larry On Tue, 15 Mar 2005 11:38:38 -0500, Phill B [EMAIL PROTECTED] wrote: Thats what I thought but the

Re: css and images

2005-03-15 Thread Phill B
The site seams to take into account every image that is listed in the style sheet regardless of it being used on the page or not. Makes it hard to get a good idea of what is going on. On Tue, 15 Mar 2005 11:54:00 -0500, Larry C. Lyons [EMAIL PROTECTED] wrote: It must be because of the size of

css and images

2005-03-14 Thread Phill B
If you have a style sheet that lists several images, will it load those images even if the style is not called to? I need to know if it will cause any performance issues. This is what the style sheet would look like. #style { background-image: url('/images/a.jpg'); background-repeat: no-repeat;