Slow when HTML + CSS is large

When I run:

▶ time node bin/minimalcss.js https://www.peterbe.com/plog-original.html -o /dev/null

It steadily takes about 6-7 seconds. That’s way too slow. Let’s see what we can do.

[leeoniya]

That’s soo cool. I’d love to experiment with making minimalcss depend on DropCSS. I love the idea of how minimalcss can get you the rendered DOM as a HTML string, including any DOM mutations (first) by things like window.onload but once it has the HTML strings (per URL) and the CSS hrefs, technically it could replace csstree+cheerio if it works out.

what would be the value-add of --use-dropcss over the DropCSS/Puppeteer demo i posted above and the same advice in its docs? if you’d like to add this option to minimalcss, then certainly feel free to do so.

Hint hint @leeoniya ^ 😃

i’m not sure i got this one 😃 did you want me to compare the diff between dropcss and minimalcss outputs of your site?

[peterbe]

what would be the value-add

What I’m saying is that minimalcss current bundles two distinct pieces of functionality. A) getting the HTML B) analyzing the HTML. It’s kinda nuts that it’s all baked into 1 thing but here we are. I like all the work and effort that’s gone into (A) but I wish (B) was something you can optionally swap in and out for other solutions.

In other words, today minimalcss is puppeteer + csstree+cheerio. What --use-dropcss would do is change that to puppeteer + dropcss.

if you’d like to add this option to minimalcss, then certainly feel free to do so.

I do. But struggling to find the time. It’s easier to think and comment about it rather than writing a patch. It was my optimistic hope that you’d have the inclination but I totally understand if you don’t.