Csscss: a CSS redundancy analyzer that analyzes redundancy (opens in new tab)

This could be an interesting companion to Helium. Helium-css can be used on live sites to find unused CSS. Combine with this project to remove duplicates too. https://github.com/geuis/helium-css

Personally I used Chrome dev tools - and it has a feature called 'CSS Selector Profiles' under the 'profile' tab.

You can 'record' yourself using a website - and Chrome records how many 'hits' each css rule gets.

This is better than Dust-me, and all the other CSS rule detectors - because it allows you to use your site in a 'dynamic' way - and test for all the edge CSS cases (like resizing your browser to small, or enabling an error message etc).

After using my SaaS for an hour - I found hundreds of rules that just never got used.

Also - it tells you how many times a rule got used. So I found a few number of rules that literally only got used once, and I could often re-write them into 1-2 bigger rules - further reducing my CSS overhead.

From the makers of the phenomenal Chosen jquery plugin.

http://harvesthq.github.io/chosen/

Hopefully this is indicative of the quality of this library! I'll definitely try it out this morning.

It's rare that I feel any particular emotion towards project names, but the name and description behind this one is inspired.

If you're a ruby developer I strongly encourage you to check out the source code and parsing in general. This is heavily using parslet [1] to build a css parser [2]. I'm sure there are edge cases I have missed, but still the LOC for this codebase is relatively small and fairly readable.

Stay away from the RedundancyAnalyzer though. There be dragons.

[1] http://kschiess.github.io/parslet/

[2] https://github.com/zmoazeni/csscss/tree/ae2f22f4416bca35f903...

CSSO [1] is a tool that removes duplicate declarations during minification instead of just warning about them. It also performs more advanced structural optimizations.

[1] http://bem.info/tools/csso/

I love the name and tag line.

Here is something I came across at PyCon. This technique uses genetic algorithm to minimize the CSS. The author claims 10% improvement over the standard CSS minimizer.

Links:

- https://us.pycon.org/2013/schedule/presentation/178/

- https://github.com/ryansb/genetic-css

This. This makes me smile. For the name, tagline and the application.

I bookmarked this for sure! I'm the WORST at having tons of duplicate declarations!

It seems like when run on SCSS mode, it expands mixins before running the redundancy check. For instance, two of my selectors both include three of the same mixins, which end up expanding into 23 rules, and CSSCSS reports 25 shared rules between them. (Further inspection confirms that exactly 2 normal rules are shared.)

I would think that using mixins should also count as having eliminated redundancy. A simple solution would be to ignore them, or more ideally the redundancy check could treat mixins just as a normal rule, so that it could detect using the same set of mixins in multiple places as redundancy.

Great!

But, one issue. It appears to not support @import of Compass extensions: "File to import not found or unreadable."

I'm upvoting this is for the cleverly redundant title that repeats itself and causes me to vote it up.

We really need this, our css has grown in to a monster over the years.

This may also be of interest:

Dust-Me Selectors is a firefox extension that scans HTML pages to find unused CSS selectors. http://www.brothercake.com/dustmeselectors/

Brilliant, I was just searching for a tool for this.

Noob question: how do I know the selectors and inheritance rules are applied in the same way as the target platform?

Should have run an analyser against the sub heading for that article.

Any support for scss/sass planned?