<?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: Effective Web Performance: The Wrong 80 Percent</title>
	<atom:link href="http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80-percent/feed/" rel="self" type="application/rss+xml" />
	<link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80-percent/</link>
	<description>Web Performance, Branding, and Social Media</description>
	<lastBuildDate>Wed, 17 Mar 2010 01:50:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: simonkenyonshepard</title>
		<link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80-percent/comment-page-1/#comment-1353</link>
		<dc:creator>simonkenyonshepard</dc:creator>
		<pubDate>Wed, 16 Dec 2009 22:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://newestindustry.org/?p=2691#comment-1353</guid>
		<description>I agree with what you are saying, in that bad design is a cause of poor performance, but in my opinion the two you pit against each other are as important as each other. &lt;br&gt;The key thing about performance optimization is that it&#039;s a practice of highly detailed painstaking analysis and refinement. What your actually complaining about is the lack of the same in the UX design process. Only if both are given the same level of detailed craftsmanship and forethought will you create a website that meets the standards you are talking about.&lt;br&gt;The best analogy to use here is cars, if you put spoilers and bonnet vents on articulated lorry, it doesn&#039;t make much of a difference to performance, however, if you put them on a Nascar in the right places, it can make the all important difference...</description>
		<content:encoded><![CDATA[<p>I agree with what you are saying, in that bad design is a cause of poor performance, but in my opinion the two you pit against each other are as important as each other. <br />The key thing about performance optimization is that it&#39;s a practice of highly detailed painstaking analysis and refinement. What your actually complaining about is the lack of the same in the UX design process. Only if both are given the same level of detailed craftsmanship and forethought will you create a website that meets the standards you are talking about.<br />The best analogy to use here is cars, if you put spoilers and bonnet vents on articulated lorry, it doesn&#39;t make much of a difference to performance, however, if you put them on a Nascar in the right places, it can make the all important difference&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Pierzchala</title>
		<link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80-percent/comment-page-1/#comment-1327</link>
		<dc:creator>Stephen Pierzchala</dc:creator>
		<pubDate>Thu, 17 Sep 2009 17:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://newestindustry.org/?p=2691#comment-1327</guid>
		<description>Having looked at the Aptimize Web site (I unfortunately was not able to attend Velocity this year), it seems to do many of the things in a single package that Steve Souders recommends sites do to improve measured performance.&lt;br&gt;&lt;br&gt;However, as the above post notes, Aptimize is simply another in a long line of tools designed to fix the technical problem of poor Web performance. &lt;br&gt;&lt;br&gt;If Web performance is being examined after a site has been released, the question of how the site got out the door in the first place becomes even more important.</description>
		<content:encoded><![CDATA[<p>Having looked at the Aptimize Web site (I unfortunately was not able to attend Velocity this year), it seems to do many of the things in a single package that Steve Souders recommends sites do to improve measured performance.</p>
<p>However, as the above post notes, Aptimize is simply another in a long line of tools designed to fix the technical problem of poor Web performance. </p>
<p>If Web performance is being examined after a site has been released, the question of how the site got out the door in the first place becomes even more important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JFraser</title>
		<link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80-percent/comment-page-1/#comment-1326</link>
		<dc:creator>JFraser</dc:creator>
		<pubDate>Thu, 17 Sep 2009 13:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://newestindustry.org/?p=2691#comment-1326</guid>
		<description>Got any feedback on Aptimize? When I was at Velocity there was a lot of buzz about it but would like to hear from someone using it.</description>
		<content:encoded><![CDATA[<p>Got any feedback on Aptimize? When I was at Velocity there was a lot of buzz about it but would like to hear from someone using it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
