←back to thread

Critical CSS

(critical-css-extractor.kigo.studio)
234 points stevenpotts | 2 comments | 06 May 25 03:13 UTC | HN request time: 0.419s | source
Show context
oneeyedpigeon ◴[06 May 25 09:05 UTC] No.43903048[source]▶
Feels like premature optimisation to me. Are there really cases where the CSS is so complex or the page loads so many resources that this effort is worthwhile? Maybe with the most complex web apps, I guess, but for almost all cases, I would have thought writing clean CSS, HTML, and JavaScript would render this unnecessary or even counterproductive.
replies(7): >>43903086 #>>43904549 #>>43906407 #>>43907541 #>>43908043 #>>43908178 #>>43928444 #
1. Gabrys1 ◴[06 May 25 09:13 UTC] No.43903086[source]▶
I would pay good money for this tool ~12 years ago. We had a site with enormous amounts of CSS that accumulated over the years and it was really unclear which rules are and which aren't critical
replies(1): >>43920470 #
2. korm ◴[07 May 25 20:54 UTC] No.43920470[source]▶
The mod_pagespeed filter "prioritize_critical_css" was released exactly 12 years ago in early May 2013. At least 3 more popular critical css tools were released the following year, integrating with Grunt, Gulp, and later Webpack.