I think this approach can become unhelpful in cases where there are a couple of bigger images. Say, 5 images of 20kb each would already add some 100 kb to the CSS and thus might slow down the initial CSS rendering.

My idead is, instead of only ignoring images above the 32kB threshold (or not), it would be useful if there was an option to set this limit to some manual value, so the user (or even better: the theme author) could decide for the most beneficial value.

Comments

jcarnett’s picture

jcarnett commented
Priority: Normal » Minor

2.x solves this problem by aggregating the image data in a file separate from the rest of the CSS so your other styles will load first and be available for rendering while the image data is still loading.

I'm not opposed to adding options to set the maximum file size, but I don't think it's something I'm going to focus on immediately.