3 ms·

Hey, article author here :) > A lot of great information here. Thanks! > …unless you've produced some kind of CSS monstrosity, your CSS isn't the bottleneck

Hey, article author here :) > A lot of great information here. Thanks! > …unless you've produced some kind of CSS monstrosity, your CSS isn't the bottleneck in your website performance. You’re definitely right insofar as selector efficiency should be last on your list of things-to-make-my-site-faster. CSS as a whole, however, is a pretty significant performance concern; I wrote a little more about that here: http://csswizardry.com/2013/01/front-end-performance-for-web-designers-and-front-end-developers/#section:css-and-performance http://csswizardry.com/2013/01/front-end-performance-for-web... </plug> Cheers! H

ufukbay 14y ago
Is there a performance difference between using "div#container" and "#container"? When reading the css, I find it easier to be reminded that the element with the id container is a div element, but I guess its an additional check for the browser right?
- csswizardry 14y ago
  Qualifying selectors like that is always a bad idea because: 1) What if you ever need to use the selector on a different element? 2) A performance hit (though so slight it might as well not matter) 3) Increased specificity I have written a lot about CSS selectors: http://csswizardry.com/2012/05/keep-your-css-selectors-short/ http://csswizardry.com/2012/05/keep-your-css-selectors-short... http://csswizardry.com/2012/07/quasi-qualified-css-selectors/ http://csswizardry.com/2012/07/quasi-qualified-css-selectors... http://csswizardry.com/2012/07/shoot-to-kill-css-selector-intent/ http://csswizardry.com/2012/07/shoot-to-kill-css-selector-in... H
  - ufukbay 14y ago
    Thanks for the reply and the links, I will check them out. :)
bung 14y ago
Maybe a dumb question, but if you are making one of these larger sites, and you add classes to everything because there are "100s of <a> tags" ... does all the added bytes to the HTML matter less than the time it takes to parse CSS? or does it not make any difference, I guess we're talking about milliseconds here? Would some people choose to push it onto the client and reduce their bandwidth?

ufukbay 14y ago

Is there a performance difference between using "div#container" and "#container"? When reading the css, I find it easier to be reminded that the element with the id container is a div element, but I guess its an additional check for the browser right?

csswizardry 14y ago
Qualifying selectors like that is always a bad idea because: 1) What if you ever need to use the selector on a different element? 2) A performance hit (though so slight it might as well not matter) 3) Increased specificity I have written a lot about CSS selectors: http://csswizardry.com/2012/05/keep-your-css-selectors-short/ http://csswizardry.com/2012/05/keep-your-css-selectors-short... http://csswizardry.com/2012/07/quasi-qualified-css-selectors/ http://csswizardry.com/2012/07/quasi-qualified-css-selectors... http://csswizardry.com/2012/07/shoot-to-kill-css-selector-intent/ http://csswizardry.com/2012/07/shoot-to-kill-css-selector-in... H
- ufukbay 14y ago
  Thanks for the reply and the links, I will check them out. :)

bung 14y ago

Maybe a dumb question, but if you are making one of these larger sites, and you add classes to everything because there are "100s of <a> tags" ... does all the added bytes to the HTML matter less than the time it takes to parse CSS? or does it not make any difference, I guess we're talking about milliseconds here? Would some people choose to push it onto the client and reduce their bandwidth?