<?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: Browser Performance Issues with Charsets</title> <atom:link href="http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets/feed" rel="self" type="application/rss+xml" /><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets</link> <description>Next Generation Web Performance</description> <lastBuildDate>Wed, 16 May 2012 13:49:16 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.2</generator> <item><title>By: Gestion de crise</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-5112</link> <dc:creator>Gestion de crise</dc:creator> <pubDate>Thu, 04 Aug 2011 14:25:52 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-5112</guid> <description>Hi, does it work with Google Chrome too ?</description> <content:encoded><![CDATA[<p>Hi, does it work with Google Chrome too ?</p> ]]></content:encoded> </item> <item><title>By: Private Jet Hire</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-4948</link> <dc:creator>Private Jet Hire</dc:creator> <pubDate>Wed, 25 May 2011 11:03:02 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-4948</guid> <description>is this solution applicable on every browser? nice find though</description> <content:encoded><![CDATA[<p>is this solution applicable on every browser? nice find though</p> ]]></content:encoded> </item> <item><title>By: 对《优化浏览器渲染》的补充【译】 &#124; 所谓技术 - 裁纸刀下</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-2849</link> <dc:creator>对《优化浏览器渲染》的补充【译】 &#124; 所谓技术 - 裁纸刀下</dc:creator> <pubDate>Mon, 14 Mar 2011 08:07:10 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-2849</guid> <description>[...] Browser Performance Issues with Charsets [...]</description> <content:encoded><![CDATA[<p>[...] Browser Performance Issues with Charsets [...]</p> ]]></content:encoded> </item> <item><title>By: Billy Hoffman</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-10</link> <dc:creator>Billy Hoffman</dc:creator> <pubDate>Fri, 11 Jun 2010 14:06:18 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-10</guid> <description>The performance detriment is needless bloat. If a charset is specified a Content-Type HTTP header, that takes precedence over anything in the body of the HTML document, including a META tag with an http-equiv for the Content-Type header. So make a decision to either specify the charset in each document or in the HTTP header, but not both. Of course, we are talking a few dozen bytes here ;-)</description> <content:encoded><![CDATA[<p>The performance detriment is needless bloat. If a charset is specified a Content-Type HTTP header, that takes precedence over anything in the body of the HTML document, including a META tag with an http-equiv for the Content-Type header. So make a decision to either specify the charset in each document or in the HTTP header, but not both. Of course, we are talking a few dozen bytes here <img
src='http://zoompf.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Artz</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-9</link> <dc:creator>Artz</dc:creator> <pubDate>Thu, 10 Jun 2010 15:41:28 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-9</guid> <description>Is there any performance benefit/detriment of having both a charset defined in the response header AND the meta tag?</description> <content:encoded><![CDATA[<p>Is there any performance benefit/detriment of having both a charset defined in the response header AND the meta tag?</p> ]]></content:encoded> </item> <item><title>By: IE 8 Charset Bug - ravelrumba</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-8</link> <dc:creator>IE 8 Charset Bug - ravelrumba</dc:creator> <pubDate>Fri, 14 May 2010 21:12:43 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-8</guid> <description>[...] Hoffman has a great post about charset and performance issues, in which he mentions that Firefox will re-request a URL if it detects a new charset after the [...]</description> <content:encoded><![CDATA[<p>[...] Hoffman has a great post about charset and performance issues, in which he mentions that Firefox will re-request a URL if it detects a new charset after the [...]</p> ]]></content:encoded> </item> <item><title>By: High Performance Web Sites :: Page Speed 1.6 Beta - new rules, native library</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-7</link> <dc:creator>High Performance Web Sites :: Page Speed 1.6 Beta - new rules, native library</dc:creator> <pubDate>Tue, 02 Feb 2010 05:48:48 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-7</guid> <description>[...] Returning charset in the Content-Type header will ensure the browser sees it early. (See this Zoompf post for more [...]</description> <content:encoded><![CDATA[<p>[...] Returning charset in the Content-Type header will ensure the browser sees it early. (See this Zoompf post for more [...]</p> ]]></content:encoded> </item> <item><title>By: Billy Hoffman</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-6</link> <dc:creator>Billy Hoffman</dc:creator> <pubDate>Wed, 06 Jan 2010 16:20:52 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-6</guid> <description>I haven&#039;t tried with other browsers yet. I suppose all thats needed is incrementally adding whitespace and testing in the browser until you see different characters in the alert box.</description> <content:encoded><![CDATA[<p>I haven&#8217;t tried with other browsers yet. I suppose all thats needed is incrementally adding whitespace and testing in the browser until you see different characters in the alert box.</p> ]]></content:encoded> </item> <item><title>By: Kyle</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-5</link> <dc:creator>Kyle</dc:creator> <pubDate>Wed, 06 Jan 2010 08:26:01 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-5</guid> <description>Wow! Were you able to repeat this result in other browsers? I noticed I was getting an inconsistent result from your demo, so I to a peek at the cache entry and saw it was stored with the charset from the meta tag. Interesting.</description> <content:encoded><![CDATA[<p>Wow! Were you able to repeat this result in other browsers? I noticed I was getting an inconsistent result from your demo, so I to a peek at the cache entry and saw it was stored with the charset from the meta tag. Interesting.</p> ]]></content:encoded> </item> <item><title>By: uberVU - social comments</title><link>http://zoompf.com/blog/2009/12/browser-performance-issues-with-charsets#comment-4</link> <dc:creator>uberVU - social comments</dc:creator> <pubDate>Fri, 04 Dec 2009 18:20:27 +0000</pubDate> <guid
isPermaLink="false">http://zoompf.com/blog/?p=150#comment-4</guid> <description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;
This post was mentioned on Twitter by zoompf: HTML Charsets are boring But not using Charsets correctly caused web performance problems. Learn more now: http://bit.ly/5q8mee...</description> <content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p><p>This post was mentioned on Twitter by zoompf: HTML Charsets are boring But not using Charsets correctly caused web performance problems. Learn more now: <a
href="http://bit.ly/5q8mee" rel="nofollow">http://bit.ly/5q8mee</a>&#8230;</p> ]]></content:encoded> </item> </channel> </rss>
