# Css cowpaths / success / :empty

**URL:** <https://discuss.httparchive.org/t/css-cowpaths-success-empty/1903>\
**Category:** Analysis\
**Created:** [March 31, 2020, 4:34pm UTC](https://discuss.httparchive.org/t/css-cowpaths-success-empty/1903 "2020-03-31T16:34:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rviscomi](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.httparchive.org/rviscomi/32/835_2.png) [@rviscomi](https://discuss.httparchive.org/u/rviscomi)\
**Post date:** [July 3, 2020, 11:43pm UTC](https://discuss.httparchive.org/t/css-cowpaths-success-empty/1903/2 "2020-07-03T23:43:34Z")

</div>

Hey @briankardell, late reply but yes it should be possible to analyze CSS in this way. We have the raw CSS response bodies and we can also query the parsed stylesheet, similar to how we analyzed the CSS chapter of the Almanac last year. See [Analyzing stylesheets with a JS-based parser](https://discuss.httparchive.org/t/analyzing-stylesheets-with-a-js-based-parser/1683) for background on how we did that.

---

_[View the full topic](https://discuss.httparchive.org/t/css-cowpaths-success-empty/1903)._
