Having a few extra DIV is not going to slow your website to that extent if you had some JavaScript, or wrote malformed markup or used nested TABLE layout then yes, you might get a slowdown in rendering, etc.
If you want a benefit of Strict over Transitional; the Strict hasn’t the same amount of (deprecated presentational values) thus you could ‘theoretically’ save some markup weight by placing your presentation within CSS where it is supposed to go, etc.
The w3schools is noted for having outdated or incorrect advice Chris, so take a lot of their material with a big pinch of salt – don’t confused that site with the W3C.
I’ll try using div. If it slows my site (and I’ve seen it do it for years), I’ll go back to <p>. As far as semantics go, strict validation is strict enought for me.
You’ve “seen” it. How about some proof. Some logic. Some technical reason.
And you can forget about validation. Semantics counts more. You can’t build until you know what you’re building. If you don’t know what you’re building, but you start building, you need to learn more before going further.
You’re flying blind around the validation. You need to read the specs, or some tech docs that explain them. Hiding inline inside block level is not the answer, it’s a fake. You say: all water is good. I say: salt water will kill you.
Noonnope,
I’ve measured it many times. I admit that there are plenty of divs in my code already, from wordpress. While writing this, I looked for the divs on my site to make sure none of them were mine and found that I forgot that I do have a div that I put in about a year ago - and the site doesn’t have the stop and go problem. I guess that problem got resolved when fixing something else. But I really did have the problem - for at least 3 years. I’ll put the div in tomorrow and see what happens.
You won’t get perfection (semantics) with div either, because if you don’t put in an   along with the image, you’ll get an empty div error. So there really is no way to center an image without tricking the compliler.
