First metrics are in! 21,000+ websites analyzed. The `max` column is absolutely bonkers. Plaintext table of attached screenshot here: gist.github.com/bartveneman/...

The dust of decades settles on your keyboard as you push aside lines of vendor prefixes Your fedora casts shadows over cryptic CSS hacks from another era. "This belongs in a museum" you mutter ReliCSS: The front-end archaeologist's tool for navigating legacy CSS www.alwaystwisted.com/relicss/ 🙏🖤

Do you ever use or look at the browserhacks analysis that we provide? Old IE hacks like `*zoom: 1`, or others like old Webkit stuff `.selector:not(*:root) {}`, etc. etc. Considering removing it from our analysis to speed it up and reduce bundle size.

How to calculate CSS code coverage with @playwright/test 🎭 www.projectwallace.com/blog/how-to-...

BIG shoutout to @netlify.com to allow projectwallace.com to run on an Open Source sponsered plan. This allows me to keep shipping many updates for free to everyone to use 🫶

How to calculate CSS code coverage with @playwright.dev www.projectwallace.com/blog/how-to-...

It looks like the folks at cssstats.com did a massive overhaul. Lots more stats, comparing websites and saving snapshots, for free! 😱 It looks like it's still early days because I've encountered many issues but they've taken a giant leap.

If you really hate looking at unused custom properties, maybe clean them up? 😇 I know looking at unused custom properties not applied in devtools is not the same as potentially flawed static analysis on a large chunk of CSS, but hey...

Open sourcing css-code-coverage github.com/projectwalla... It is *very* early stages, it needs a ton more tests, docs, cli tool etc. but is for the folks who want an early look.

We're experiencing some DNS issues while we're moving away from Vercel. Please hang on tight. Fingers crossed that analyzing your CSS isn't the most important thing you were going to do today 🤞

Thinking of cooking up something to compare sets of CSS. Most likely for before/after sort of stuff, but perhaps other use cases too. Visualisation of that will be tough, I guess. Rendering stats for a single site easily ends up with thousands of DOM nodes. Would you use it?

Gave the ol' CMD+K menu a fresh lick of paint and added a search bar. Much more useful this way 😍

Doing a very similar trick on the CSS Coverage inspector: create an array of start/stop elements to render an entire range instead of a single DOM node per line. ❌ DOM size before: 3145 nodes ✅ DOM size after: 686 nodes (But gains depend on CSS size & patchiness of coverage of the selected file)

I appreciate all 18 of you! +1 rank gained is still a plus in my book. 2025.stateofcss.com/en-US/other-...

How to create a Naked CSS theme without removing CSS www.projectwallace.com/blog/how-to-...

🥵

enjoying all the recent (or not so recent) updates to @projectwallace.com's (free) CSS analyser page, including a dedicated 'design tokens' section, like this – www.projectwallace.com/design-token... lovely stuff @veneman.dev 🙏 🖤

🧛 Anyone up for counting the depth of your CSS nesting? Could be interesting to spot deeply nested and hard to debug rulesets, declarations, etc.

🆕 Spacing reset analysis Sparked by @ohhelloana.blog's enthusiasm, this turned out to be a relatively simple feature! 🥳 A few gotchas: - a gazillion ways to write 0 (scientific notation, floats, signed numbers) - many spacing-related properties, potentially vendor prefixed (although unlikely)

#CSSDay was a blast and the first act of applying quick wins was improving scrollbar styling after watching @nerdy.dev's talk. Still recovering from the energy.

At #cssday where @miriam.codes is speaking truths

🌟 Release notes April & May www.projectwallace.com/blog/april-m... ☀️ NEW Light theme 🍑 NEW CSS Naked theme ⚖️ NEW Website Analytics 🛠️ Added new devtools to several pages

🆕 Container names. Because we all sometimes forget to name a thing, or forget that we named it and never used it 😇

🆕 See which Media Features are used. Useful if you have many media queries and want a quick view of which features are queried. Idea taken from @httparchive.org's CSS chapter.

🌟 Release notes April & May www.projectwallace.com/blog/april-m... ☀️ NEW Light theme 🍑 NEW CSS Naked theme ⚖️ NEW Website Analytics 🛠️ Added new devtools to several pages

Published [email protected] and [email protected] to reduce their install size with ~50%. css-analyzer shipped 2 versions of css-tree which is the only dependency but at a 'costly' ~2.03MB. It also ships CommonJS so we *could* even further get the number down.

The @httparchive.org 's Web Almanac is looking for contributors for this year's edition. github.com/HTTPArchive/...

🔆 last night I shipped a light theme There may be bits and bobs still not converted yet so please let me know if anything looks broken. Also, grab some sunglasses 😎

All packages updated to ship ESM only: 🌱 github.com/projectwalla... 🌱 github.com/projectwalla... 🌱 github.com/projectwalla... 🌱 github.com/projectwalla... 🌱 github.com/projectwalla... 🌱 github.com/projectwalla... Published a new major for each of them with ESM being the only change.

✌️ TWO new features released Well, actually 3. Oh who cares anyway. ✅ Copy your CSS @​layers as JSON ✅ Show devtools on the custom property page ✅ Copy all/unused/undefined/undefined-with-fallback properties as JSON

March 2025 release notes 📝 www.projectwallace.com/blog/march-2...

Just in time for the March release notes

🚢 39 releases 🦄 1 new _years-long_ awaited feature 🏳️‍🌈 Moar syntax highlighting Release notes (Feb 2025) www.projectwallace.com/blog/februar...

The item usage panel now also highlights syntax.

✨ feature alert: pseudo class analysis www.projectwallace.com/analyze-css

MASSIVE performance improvement released tonight when you open the inspector or networkpane (or any of our devtools panels). Feels really noticable when inspecting larger sites. Yes I tried it on a 5MB CSS file.

Pretty massive new feature: when navigating between pages the site now remembers your URL and CSS so you don't have to submit+download the same CSS every time 🥳

You can now sort the CSS Coverage table by URL, coverage or filesize! www.projectwallace.com/css-coverage

that's twice this week I've found a possible use for my little 'can I use combiner' CSS support tool. I think I should tidy it up a bit and put it somewhere

📢 CSS Coverage viewer A new page recently arrived and it helps you inspect your CSS coverage generated from Chrome/Edge devtools, or more importantly: coverage reports generated from Playwright/Puppeteer (because they can span multiple page navigations)!! www.projectwallace.com/css-coverage

📝 January release notes *Massive* release notes. www.projectwallace.com/blog/january...

📝 January release notes *Massive* release notes. www.projectwallace.com/blog/january...

😅 our format-css package was so opinionated that it skipped rendering `!important` Anyway, fixed in 1.5.1 github.com/projectwalla...

@projectwallace.com I enjoyed your article about CSS @import and wrote something similar fullystacked.net/css-import/

Custom Property analyzer now also tells you which custom properties are: - never declared 🙄 - but still used in a var() 😵‍💫 - but with a fallback value ☺️ This is a little better than just checking for the propery never being declared, because the fallback acts as a safe-guard.

🔎 search custom properties 🔍 When reviewing large codebases you often want to check for certain names or prefixes. The new search lets you do that, even with negated patterns like `!my-prefix`.

☠️ Reverting this because it seems there's a pretty massive performance that I can't wrap my head around just yet. Sorry! Will figure our a way to get it back though. 😔

🗣️💬 Preserving comments Our CSS formatter is updated to keep most of your CSS comments intact instead of stripping them. This can be helpful sometimes when auditing or prettifying your CSS. github.com/projectwalla...

So stoked about the layer tree visualisation that it's now part of the analyzer result page, instead of only listing out which layers were found 🥰

💫 Line numbers! 💫 Because Wallace is starting to look more and more like an actual editor and line numbers can be super helpful.