# Installed purgecss but I still see on Coverage a lot of unused CSS

**URL:** https://discourse.roots.io/t/installed-purgecss-but-i-still-see-on-coverage-a-lot-of-unused-css/22180
**Category:** sage
**Created:** 2022-01-25T19:57:20Z
**Posts:** 16
**Showing post:** 4 of 16

## Post 4 by @pko — 2022-01-25T20:02:33Z

Sure, sorry about that. Basically all I did is the instructions that I saw here for Purge CSS

> [@Removing unused CSS with Purgecss/UnCSS](https://discourse.roots.io/t/removing-unused-css-with-purgecss-uncss/11586):
>
> This seems to be [a common request here](https://discourse.roots.io/search?q=unused%20css) so I thought I would demonstrate two very simple methods which require very little modification to Sage. Recently, I’ve been looking for a quicker alternative to [UnCSS](https://github.com/giakki/uncss), since it is slow and often flaky. I thought [PurifyCSS](https://github.com/purifycss/purifycss) would be the answer since it has [a nice webpack plugin](https://github.com/webpack-contrib/purifycss-webpack), however, [it doesn’t remove similar named selectors](https://github.com/purifycss/purifycss/issues/189), which — if you use something like [Tachyons](http://tachyons.io/) — can be [a lot](http://tachyons.io/docs/table-of-properties/). As of writing this, the main repo seems to be unmaintained as well. [P…](https://github.com/FullHuman/purgecss)

I ran the command and added those lines on webpack.config.optimize.js then ran a yarn build:production.

Here are the contents from my webpack.config.optimize.js

 ![image](https://discourse.roots.io/uploads/default/original/2X/e/e68939db134970dc59451c377d1f80d80c653088.png)

---

_[View the full topic](https://discourse.roots.io/t/installed-purgecss-but-i-still-see-on-coverage-a-lot-of-unused-css/22180)._