<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Newest Industry - Latest Comments in Effective Web Performance: The Wrong 80%</title><link>http://newestindustry.disqus.com/</link><description>Chronicles of a Crazy Canuck</description><atom:link href="https://newestindustry.disqus.com/effective_web_performance_the_wrong_80/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 16 Dec 2009 12:06:09 -0000</lastBuildDate><item><title>Re: Effective Web Performance: The Wrong 80%</title><link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80/#comment-25954680</link><description>&lt;p&gt; 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;/p&gt;&lt;p&gt;The key thing about performance optimization is that it'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.&lt;/p&gt;&lt;p&gt;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;/p&gt;&lt;p&gt;The best analogy to use here is cars, if you put spoilers and bonnet vents on articulated lorry, it doesn'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... &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">simonkenyonshepard</dc:creator><pubDate>Wed, 16 Dec 2009 12:06:09 -0000</pubDate></item><item><title>Re: Effective Web Performance: The Wrong 80%</title><link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80/#comment-16806781</link><description>&lt;p&gt;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;/p&gt;&lt;p&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;/p&gt;&lt;p&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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stephen Pierzchala</dc:creator><pubDate>Thu, 17 Sep 2009 08:16:43 -0000</pubDate></item><item><title>Re: Effective Web Performance: The Wrong 80%</title><link>http://newestindustry.org/2009/09/10/effective-web-performance-the-wrong-80/#comment-16803304</link><description>&lt;p&gt;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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JFraser</dc:creator><pubDate>Thu, 17 Sep 2009 04:56:08 -0000</pubDate></item></channel></rss>