<?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: 54 out of the US top 100 websites fail Yahoo’s performance test</title>
	<atom:link href="http://royal.pingdom.com/2008/05/29/54-out-of-the-us-top-100-websites-fail-yahoo%e2%80%99s-performance-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://royal.pingdom.com/2008/05/29/54-out-of-the-us-top-100-websites-fail-yahoo%e2%80%99s-performance-test/</link>
	<description>Ramblings and tech news from the Pingdom team</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:34:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Michael Lee</title>
		<link>http://royal.pingdom.com/2008/05/29/54-out-of-the-us-top-100-websites-fail-yahoo%e2%80%99s-performance-test/comment-page-1/#comment-206821</link>
		<dc:creator>Michael Lee</dc:creator>
		<pubDate>Sun, 22 Jun 2008 06:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://royal.pingdom.com/?p=301#comment-206821</guid>
		<description>Surprising indeed!

It&#039;d be interesting to:

- See these results combined with actual broadband usage figures.
- Use YSlow to test different connection speeds.

If YSlow could emulate slow connections (i.e. EDGE, dial-up) it would help to pinpoint response bottlenecks that could be optimized for an overall improved experience across all connection types...

I wonder though how important this really is? Once upon a time software size was a major concern, today not so much since space is so readily available. Maybe the same can/will be said about web content sizes since even mobile platforms are seeing improvements in both their networking speeds (3G) and storage capacity (2GB+ microSD). Besides, even with startup optimization and caching some media content may remain large and so require a minimum connection speed for an acceptable experience...</description>
		<content:encoded><![CDATA[<p>Surprising indeed!</p>
<p>It&#8217;d be interesting to:</p>
<p>- See these results combined with actual broadband usage figures.<br />
- Use YSlow to test different connection speeds.</p>
<p>If YSlow could emulate slow connections (i.e. EDGE, dial-up) it would help to pinpoint response bottlenecks that could be optimized for an overall improved experience across all connection types&#8230;</p>
<p>I wonder though how important this really is? Once upon a time software size was a major concern, today not so much since space is so readily available. Maybe the same can/will be said about web content sizes since even mobile platforms are seeing improvements in both their networking speeds (3G) and storage capacity (2GB+ microSD). Besides, even with startup optimization and caching some media content may remain large and so require a minimum connection speed for an acceptable experience&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StorefrontBacktalk - Techniques, Tools, and Tirades about Retail Technology and E-Commerce</title>
		<link>http://royal.pingdom.com/2008/05/29/54-out-of-the-us-top-100-websites-fail-yahoo%e2%80%99s-performance-test/comment-page-1/#comment-188200</link>
		<dc:creator>StorefrontBacktalk - Techniques, Tools, and Tirades about Retail Technology and E-Commerce</dc:creator>
		<pubDate>Fri, 06 Jun 2008 15:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://royal.pingdom.com/?p=301#comment-188200</guid>
		<description>[...] surprising considering their minimalistic style.&#8221;But the more interesting part of the Pingdom stats is the analysis that looks at the sites&#8217; size, HTTP requests and caching. It&#8217;s worth a [...]</description>
		<content:encoded><![CDATA[<p>[...] surprising considering their minimalistic style.&#8221;But the more interesting part of the Pingdom stats is the analysis that looks at the sites&#8217; size, HTTP requests and caching. It&#8217;s worth a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

