<?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: Performance and Beauty</title>
	<atom:link href="http://timkadlec.com/2010/04/performance-and-beauty/feed/" rel="self" type="application/rss+xml" />
	<link>http://timkadlec.com/2010/04/performance-and-beauty/</link>
	<description>A Wisconsin based web developer writing about the web.</description>
	<lastBuildDate>Wed, 16 May 2012 20:42:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Tim Kadlec</title>
		<link>http://timkadlec.com/2010/04/performance-and-beauty/comment-page-1/#comment-13953</link>
		<dc:creator>Tim Kadlec</dc:creator>
		<pubDate>Thu, 15 Apr 2010 02:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://timkadlec.com/?p=345#comment-13953</guid>
		<description>I agree - right now, for most people, optimization is certainly not the first consideration (and often, barely a consideration at all). I think that&#039;s going to change though. The more data we find that demonstrates just how greatly a users perspective of a site is influenced by performance, the more and more apparent it becomes that basic optimization needs to be something we &quot;just do&quot;.

I also think that the proliferation of mobile devices will factor in. People want their content no matter where they are, no matter the connection, and they don&#039;t want to wait. When they don&#039;t have the luxury of Wi-Fi and unlimited data, performance will play a very big role in determining what sites they choose to get their content from.

While clearly I cannot speak for Google, I&#039;d imagine your site wouldn&#039;t be greatly penalized. For one, the quality of your content would almost certainly outweigh whatever emphasis they&#039;ve placed on performance. Secondly, while there is certainly room for improvement performance wise (all those javascript files hurt, particularly those in the head) you do manage to rank a C in YSlow.

I&#039;m not saying I think Google&#039;s simply looking at YSlow scores, but I think they serve as a decent gauge, and I&#039;d imagine that they&#039;re only penalizing sites that do such a poor job of optimization that they would garner a D or F. (Again...just my hypothesis)</description>
		<content:encoded><![CDATA[<p>I agree &#8211; right now, for most people, optimization is certainly not the first consideration (and often, barely a consideration at all). I think that&#8217;s going to change though. The more data we find that demonstrates just how greatly a users perspective of a site is influenced by performance, the more and more apparent it becomes that basic optimization needs to be something we &#8220;just do&#8221;.</p>
<p>I also think that the proliferation of mobile devices will factor in. People want their content no matter where they are, no matter the connection, and they don&#8217;t want to wait. When they don&#8217;t have the luxury of Wi-Fi and unlimited data, performance will play a very big role in determining what sites they choose to get their content from.</p>
<p>While clearly I cannot speak for Google, I&#8217;d imagine your site wouldn&#8217;t be greatly penalized. For one, the quality of your content would almost certainly outweigh whatever emphasis they&#8217;ve placed on performance. Secondly, while there is certainly room for improvement performance wise (all those javascript files hurt, particularly those in the head) you do manage to rank a C in YSlow.</p>
<p>I&#8217;m not saying I think Google&#8217;s simply looking at YSlow scores, but I think they serve as a decent gauge, and I&#8217;d imagine that they&#8217;re only penalizing sites that do such a poor job of optimization that they would garner a D or F. (Again&#8230;just my hypothesis)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Coyier</title>
		<link>http://timkadlec.com/2010/04/performance-and-beauty/comment-page-1/#comment-13940</link>
		<dc:creator>Chris Coyier</dc:creator>
		<pubDate>Thu, 15 Apr 2010 01:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://timkadlec.com/?p=345#comment-13940</guid>
		<description>Nice analysis of Visit Philly. I think it goes to show that most of us at design agencies are designers first and optimizers second. When building a new site for a client, we think of ways to make the site look great and accomplish the obvious goals of the site. We don&#039;t think &quot;oooh, this site will really be a good opportunity to combine and minify some javascript.&quot; If a technique is awesome and will impress people, and we think we can pull it off, we&#039;ll do it. 

I&#039;m not sure I have any strong opinions on Google&#039;s move. My main blog&#039;s home page weights in at 663k with a 1.76s load time. It&#039;s not great, but I think it&#039;s pretty much fine, especially since I serve a lot of it through a CDN. If that were to be in the totally-unacceptable/major-penalty range for Google, I wouldn&#039;t be too happy about it.</description>
		<content:encoded><![CDATA[<p>Nice analysis of Visit Philly. I think it goes to show that most of us at design agencies are designers first and optimizers second. When building a new site for a client, we think of ways to make the site look great and accomplish the obvious goals of the site. We don&#8217;t think &#8220;oooh, this site will really be a good opportunity to combine and minify some javascript.&#8221; If a technique is awesome and will impress people, and we think we can pull it off, we&#8217;ll do it. </p>
<p>I&#8217;m not sure I have any strong opinions on Google&#8217;s move. My main blog&#8217;s home page weights in at 663k with a 1.76s load time. It&#8217;s not great, but I think it&#8217;s pretty much fine, especially since I serve a lot of it through a CDN. If that were to be in the totally-unacceptable/major-penalty range for Google, I wouldn&#8217;t be too happy about it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

