guest2013-1
guest
- Joined
- Aug 22, 2003
- Messages
- 19,800
Thanks again for the help guys I have passed your comments onto the web guys.
You should maybe think of getting different web guys...
Thanks again for the help guys I have passed your comments onto the web guys.
ANYWAY. My ass is sore from this stupid ****ing chair I'm sitting on and I have ton of work to do today. At least it's not 42 like yesterday. Cloudy with a chance of cool wind = nice![]()
Thanks for the contribution zagame!
You looking for something like this:Yea it's awesome, I usually save a lot just by minifying my JS and my CSS. Sometimes the designer also uses styles and includes unused ones while he designed the stuff reducing that file size considerably. Just wish there was a way to get Page Speed to show you a file without the styles, would make editing one to exclude them much easier
Dust-Me Selectors is a Firefox extension (for v1.5 or later) that finds unused CSS selectors.
It extracts all the selectors from all the stylesheets on the page you're viewing, then analyzes that page to see which of those selectors are not used. The data is then stored so that when testing subsequent pages, selectors can be crossed off the list as they're encountered.
You can test pages individually, or spider an entire site, and you'll end up with a profile of which selectors are not used anywhere.
Yes, but it's still a manual job removing those unused css selectors, especially if the designer included thousands of them in one css file.
If Dust-Me had a "this is a revised file of all the css you use" like PageSpeed gives on minified js/css or images, I'd be one happy chappy.
There anyway you know of that you can change it for IIS?
Step by step Setting up Gzip on IIS 6 (compressing servers output stream)
1. Allow the compression ISAPI to run IIS 6’s new security system prohibits ISAPI DLLs from running by default, so you need to tell IIS 6 that it’s okay to let the compression ISAPI DLL run.
01. Open the IIS admin tool (inetmgr); drill into your server, and right-click on “Web Service Extensions”.
02. Choose “Add a new web service extension”. For the extension name, use whatever you want to identify it in the list (I used “HTTP Compression Extension”).
03. You need to add a single required file, which is \Windows\System32\inetsrv\gzip.dll, the ISAPI responsible for doing gzip and deflate compression.
04. Check the “Set extension status to allowed”, then click OK.
05. You should have a new web service extension in your list called “HTTP Compression” (or whatever you named it), and it should have a status of “Allowed”.
2. Select compressible content
IIS 6’s compression system only compresses a very limited set of content. You need to enable compression for the appropriate file extensions (specifically, .aspx files for your ASP.NET pages, and perhaps any static content you want compressed as well).
01. You’re going to edit the Metabase. To do this, you first need to shut down IIS.
02. In the IIS admin tool, right click on your server name in the left panel, and choose All Tasks -> Restart IIS.
03. On the restart dialog, choose “Stop internet services” and click OK. When IIS is shut down, you’ll need to edit \Windows\System32\inetsrv\MetaBase.xml (make a backup first!).
04. Search for “IIsCompressionScheme”. There will be two XML elements, one for deflate and one for gzip. Both elements have properties called HcFileExtensions and HcScriptFileExtensions. These contain a space-delimited list of file extension for compressible content.
05. At a bare minimum, you’ll need to add aspx, ascx to the HcScriptFileExtensions list. Note that if the properties are left blank, then all content, regardless of file extension, will be compressed.
the word online ?