<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Velocity: Top 5 Mistakes of Massive CSS</title>
	<atom:link href="http://www.stevesouders.com/blog/2010/07/03/velocity-top-5-mistakes-of-massive-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevesouders.com/blog/2010/07/03/velocity-top-5-mistakes-of-massive-css/</link>
	<description>Essential knowledge for making your web pages faster.</description>
	<lastBuildDate>Sat, 04 Feb 2012 09:46:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Steve Souders</title>
		<link>http://www.stevesouders.com/blog/2010/07/03/velocity-top-5-mistakes-of-massive-css/#comment-2151</link>
		<dc:creator>Steve Souders</dc:creator>
		<pubDate>Sun, 04 Jul 2010 20:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1356#comment-2151</guid>
		<description>@Jan: I fixed the &quot;slides&quot; link. Thanks!

@Stephanie: Stylesheets aren&#039;t as bad as external scripts. Scripts block other downloads (in many browsers) and also block rendering. Stylesheets only block rendering. Either way, it&#039;s probably a little faster to avoid the DNS lookup even if you pay the price of cookies, but it depends on how big the cookies are. I would reserve the same domain for scripts, and shard stylesheets on a separate domain. It&#039;s also more important to keep scripts on the same domain for XHR (so you don&#039;t bump into the cross-site security restrictions).</description>
		<content:encoded><![CDATA[<p>@Jan: I fixed the &#8220;slides&#8221; link. Thanks!</p>
<p>@Stephanie: Stylesheets aren&#8217;t as bad as external scripts. Scripts block other downloads (in many browsers) and also block rendering. Stylesheets only block rendering. Either way, it&#8217;s probably a little faster to avoid the DNS lookup even if you pay the price of cookies, but it depends on how big the cookies are. I would reserve the same domain for scripts, and shard stylesheets on a separate domain. It&#8217;s also more important to keep scripts on the same domain for XHR (so you don&#8217;t bump into the cross-site security restrictions).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephane</title>
		<link>http://www.stevesouders.com/blog/2010/07/03/velocity-top-5-mistakes-of-massive-css/#comment-2150</link>
		<dc:creator>Stephane</dc:creator>
		<pubDate>Sun, 04 Jul 2010 14:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1356#comment-2150</guid>
		<description>Isn&#039;t the CSS file is in the critical path for page loading? Putting it on a cookieless server forces another DNS lookup. Shouldn&#039;t we treat it like an early loaded javascript and put it on the same server, even if that implies serving it with a cookie?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t the CSS file is in the critical path for page loading? Putting it on a cookieless server forces another DNS lookup. Shouldn&#8217;t we treat it like an early loaded javascript and put it on the same server, even if that implies serving it with a cookie?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Lehnardt</title>
		<link>http://www.stevesouders.com/blog/2010/07/03/velocity-top-5-mistakes-of-massive-css/#comment-2148</link>
		<dc:creator>Jan Lehnardt</dc:creator>
		<pubDate>Sun, 04 Jul 2010 11:14:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1356#comment-2148</guid>
		<description>The “Slides” link links the video. :)</description>
		<content:encoded><![CDATA[<p>The “Slides” link links the video. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

