<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>
<channel>
	<title>Tall Drink of Water</title>
	<atom:link href="http://blog.jink.us/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jink.us</link>
	<description>Text about Development, Photography and Life.</description>
	<lastBuildDate>Wed, 22 Jul 2009 03:39:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Pressing The Optimizations&#8230;</title>
		<link>http://blog.jink.us/blog/2009/07/21/pressing-the-optimizations/</link>
		<comments>http://blog.jink.us/blog/2009/07/21/pressing-the-optimizations/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 02:41:21 +0000</pubDate>
		<dc:creator>Derek Gates</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[Web]]></category>
		<guid isPermaLink="false">http://blog.jink.us/?p=6</guid>
		<description><![CDATA[Installing WordPress is incredibly easy.  Optimizing it just as easy. Being a pursuer of optimized pages, I started checking for ways to optimize the output of WordPress.  By following Yahoo! Best Practices guide I surmise that the biggest factors in (&#8230;)</p><p><a href="http://blog.jink.us/blog/2009/07/21/pressing-the-optimizations/">Read the rest of this entry &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>Installing WordPress is incredibly easy.  Optimizing it just as easy.</p>
<p>Being a pursuer of optimized pages, I started checking for ways to optimize the output of WordPress.  By following <a href="http://developer.yahoo.com/performance/rules.html">Yahoo! Best Practices</a> guide I surmise that the biggest factors in page load are:</p>
<ul>
<li>Reduce HTML elements.</li>
<li>Join, Minify Javascript and CSS files.</li>
<li>Cache files if server side calls are expensive.</li>
<li>Use GZIP compression on files.</li>
</ul>
<h2>Reduce HTML Elements</h2>
<blockquote><p>A complex page means more bytes to download and it also means slower DOM access in JavaScript. It makes a difference if you loop through 500 or 5000 DOM elements on the page when you want to add an event handler for example. </p></blockquote>
<p>This step is quite easy.  This is dependent on the theme chosen, which controls all of the output for the blog.  I am currently using the <a href="http://cordobo.com/free-wordpress-templates/green-park-2/">Green-Park 2</a> theme designed by <a href="http://cordobo.com/">Andreas Jacob</a>.  Andreas is incredibly talented and has designed this theme to be lightweight from the ground up.</p>
<p>I am designing a theme which includes many of the tricks Andreas used in Green-Park 2, such as the addition of CSS3 effects that degrade down to CSS2. </p>
<h2>Join, Minify Javascript and CSS files.</h2>
<p>For themes or plugins that use large CSS or even multiple Javascript files this is a life saver.  Joining these these smaller files into one larger file speeds up the page load.  Reducing the amount of requests the browser has to perform is key to speeding up the page, creating connections and requesting files takes time. To add more insult to injury, most browsers limit concurrent Javascript file downloading when they are from the same domain.</p>
<p>Both Javascript and CSS can be reduced in size, a process called Minifying.  Javascript and CSS can have comments removed, white space removed and other tricks to reduce file size.  The resulting small file functions the same but is downloaded quicker due to less characters in the files.</p>
<p>Joining and minifying is usually a manual affair, performed by the owner of a blog.  This becomes a pain when CSS needs updating or Javascript has to be changed or updated.  My weapon of choice for manual minifying is the <a href="http://developer.yahoo.com/yui/compressor/">YUI Compressor</a> codebase, which is a Java program to handle minifying a file at a time.  To do this online, check out the <a href="http://www.refresh-sf.com/yui/">Online YUI Compressor</a> (not run by Yahoo!).</p>
<p>For automatic joining and minifying on WordPress I use the plugin <a href="http://omninoggin.com/wordpress-plugins/wp-minify-wordpress-plugin/">WP Minify Plugin</a>.  This plugin uses the <a href="http://code.google.com/p/minify/">Minify</a> codebase which uses <a href="http://www.crockford.com/javascript/jsmin.html">JSMin</a> for it&#8217;s Javascript minification.  Minify supports swapping out JSmin for YUI, which I have yet to do.  Another option for minification is the <a href="http://aciddrop.com/php-speedy/">PHP Speedy</a> system, which a <a href="http://aciddrop.com/category/php/">WordPress plugin</a> has been started, but not available for WordPress newer than 2.7.</p>
<h2>Cache files if server side calls are expensive.</h2>
<p>WordPress is incredibly powerful, but can be bogged down by PHP calls on every page load.  This is usually insignificant to worry about, but when lots of visitors visit the blog those PHP calls can increase page load by a significant amount.  A way to fight this slowdown is to cache the generated files and serve those generated files.  On this blog I use <a href="http://ocaoimh.ie/wp-super-cache/">WP Super Cache</a>, which performs the caching automatically.</p>
<h2>Use GZIP compression on files.</h2>
<blockquote><p>Gzipping generally reduces the response size by about 70%. Approximately 90% of today&#8217;s Internet traffic travels through browsers that claim to support gzip.</p></blockquote>
<p>GZIP is an easy way to reduce page load size.  The <a href="http://omninoggin.com/wordpress-plugins/wp-minify-wordpress-plugin/">WP Minify Plugin</a> enables this when joining and minifying Javascript and CSS.  The caching by <a href="http://ocaoimh.ie/wp-super-cache/">WP Super Cache</a> GZIPs all of the page content, enabling compression where the Minify plugin can&#8217;t.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jink.us/blog/2009/07/21/pressing-the-optimizations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting Started</title>
		<link>http://blog.jink.us/blog/2009/07/08/getting-started/</link>
		<comments>http://blog.jink.us/blog/2009/07/08/getting-started/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 04:49:20 +0000</pubDate>
		<dc:creator>Derek Gates</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://blog.jink.us/?p=1</guid>
		<description><![CDATA[I&#8217;ve been taken in by the WordPress camp.  For too long I&#8217;ve avoided this blogging system, afraid that a badly crafted back-end would be a cause of headaches.  With the install completed, my initial fears were for naught.  WordPress is (&#8230;)</p><p><a href="http://blog.jink.us/blog/2009/07/08/getting-started/">Read the rest of this entry &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been taken in by the WordPress camp.  For too long I&#8217;ve avoided this blogging system, afraid that a badly crafted back-end would be a cause of headaches.  With the install completed, my initial fears were for naught.  WordPress is an incredibly easy to install and configure blog system.  Within 15 minutes of configuration and FTP uploading, this blog was alive.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jink.us/blog/2009/07/08/getting-started/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
