<?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: Image Size and Uploading</title>
	<atom:link href="http://blog.ukfast.co.uk/2006/03/27/image-size-and-uploading/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ukfast.co.uk/2006/03/27/image-size-and-uploading/</link>
	<description>News and views from the UK&#039;s best hosting provider</description>
	<lastBuildDate>Thu, 19 Jan 2012 19:17:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert Brainstorm</title>
		<link>http://blog.ukfast.co.uk/2006/03/27/image-size-and-uploading/comment-page-1/#comment-9</link>
		<dc:creator>Robert Brainstorm</dc:creator>
		<pubDate>Mon, 27 Mar 2006 16:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://ukfastblog.dev.text.co.uk/?p=15#comment-9</guid>
		<description>A third way would be to use a progressive format, which will show a blurred version of the image, which will sharpen as the image downloads. 

If you have graphics large enough to start worrying about download speeds then maybe you should consider different ways of portraying the information. An image shouldn&#039;t really be used if the information can be conveyed to the user just as effectively using plain text (&lt;a href=&#039;http://www.useit.com/alertbox/9703a.html&#039; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;)

The download time of the entire page will probably be the same if the image is cut up or in one piece, but you mentioned that it appears to be faster, this is simply because you will see several small images all downloading at the same time, but they will be downloading slower. Also cutting up images will lead to accessibility problems, not every web user is an average user and there are other specialist browsers (apart from IE and Firefox; text-readers for blind users, small screen users using smartphones and pda&#039;s will definately be affected, or people who simply prefer to have their images turned off when they browse)</description>
		<content:encoded><![CDATA[<p>A third way would be to use a progressive format, which will show a blurred version of the image, which will sharpen as the image downloads. </p>
<p>If you have graphics large enough to start worrying about download speeds then maybe you should consider different ways of portraying the information. An image shouldn&#8217;t really be used if the information can be conveyed to the user just as effectively using plain text (<a href='http://www.useit.com/alertbox/9703a.html' rel="nofollow">here</a>)</p>
<p>The download time of the entire page will probably be the same if the image is cut up or in one piece, but you mentioned that it appears to be faster, this is simply because you will see several small images all downloading at the same time, but they will be downloading slower. Also cutting up images will lead to accessibility problems, not every web user is an average user and there are other specialist browsers (apart from IE and Firefox; text-readers for blind users, small screen users using smartphones and pda&#8217;s will definately be affected, or people who simply prefer to have their images turned off when they browse)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

