<?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>DQuinn.net &#187; firebug</title>
	<atom:link href="http://www.dquinn.net/tags/firebug/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dquinn.net</link>
	<description>Daniel J. Quinn&#039;s journal of WordPress, electronic publishing, and general geek culture.</description>
	<lastBuildDate>Thu, 22 Jul 2010 23:46:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Speed Up Your WordPress: Mastering Yahoo!&#8217;s Thirteen Performance Rules</title>
		<link>http://www.dquinn.net/mastering-yahoos-13-performance-rules/</link>
		<comments>http://www.dquinn.net/mastering-yahoos-13-performance-rules/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 12:39:53 +0000</pubDate>
		<dc:creator>Daniel Quinn</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[.htaccess]]></category>
		<category><![CDATA[blogs]]></category>
		<category><![CDATA[cache-control headers]]></category>
		<category><![CDATA[content delivery network]]></category>
		<category><![CDATA[dns lookups]]></category>
		<category><![CDATA[etags]]></category>
		<category><![CDATA[expires header]]></category>
		<category><![CDATA[facelift plugin]]></category>
		<category><![CDATA[firebug]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[gzip components]]></category>
		<category><![CDATA[http requests]]></category>
		<category><![CDATA[mediatemple]]></category>
		<category><![CDATA[minify]]></category>
		<category><![CDATA[wp super cache]]></category>
		<category><![CDATA[yslow]]></category>

		<guid isPermaLink="false">http://www.dquinn.net/?p=1439</guid>
		<description><![CDATA[The problem is that while the info is definitely out there, it's not all in one place (at least as far as I've browsed). Moreover, there are a couple of specific applications of the speed tricks that haven't been clearly laid out before (particularly, applying Cache-Control headers to dynamic images generated by the WordPress Facelift plugin, or the ideal .htaccess settings if your host is MediaTemple). In the interest of time (and laziness, our one true virtue), I've compiled an easy-to-apply series on YSlow that will get your WordPress sped up in no time.]]></description>
			<content:encoded><![CDATA[<p>All right guys, I know there are already countless articles about speeding up WordPress all over the Google. We've all vied for speed when it comes to preventing our fatass blogs from choking our readers' browsers. The problem is that while the info is definitely out there, it's not all in one place (at least as far as I've browsed). Moreover, there are a couple of specific applications of the speed tricks that haven't been clearly laid out before (particularly, applying cache-control headers to dynamic images generated by the WordPress Facelift plugin, or the ideal .htaccess settings if your host is MediaTemple). In the interest of time (and laziness, our one true virtue), I've compiled an easy-to-apply series on YSlow that will get your WordPress sped up in no time.</p>
<p>First thing's first:</p>
<p>Download <a href="https://addons.mozilla.org/en-US/firefox/addon/5369">YSlow for Firebug</a> if you haven't already, then skim over <a href="http://developer.yahoo.com/performance/rules.html">Yahoo!'s article</a> about the thirteen best practices for speeding up your website:</p>
<ol>
<li><strong>Minimize HTTP Requests</strong> - (<em>Don't make me download a lot of crap</em>.)</li>
<li><strong>Use a Content Delivery Network</strong> (<em>Have someone else serve your shit</em>.)</li>
<li><strong>Add an Expires or Cache-Control Header</strong> (<em>Stale bread is best for french toast. Really</em>.)</li>
<li><strong>GZip Components </strong>(<em>Zip it up!</em>)</li>
<li><strong>Put Stylesheets at the Top </strong>(<em>I need to see your site before I click on stuff, dumbass</em>.)</li>
<li><strong>Put Scripts at the Bottom </strong>(<em>See above</em>.)</li>
<li><del>Avoid CSS Expressions</del> (<em>Who uses them anyway?</em>)</li>
<li><del>Make Javascript and CSS External</del> (<em>Duh.</em>)</li>
<li><strong>Reduce DNS Lookups</strong> (<em>Don't be a social media slut</em>.)</li>
<li><strong>Minify Javascript and CSS </strong>(<em>Nobody wants to see your whitespace</em>.)</li>
<li><del>Avoid Redirects</del> (<em>I came to your site, not theirs.</em>)</li>
<li><del>Remove Duplicate Scripts</del> (<em>Duh</em>.)</li>
<li><strong>Configure ETags</strong> (<em>Yeah, I didn't know what these were either.</em>)</li>
</ol>
<p>I also recommend setting up WP Super Cache after all is said and done. So here we go:</p>
<ul>
<li><a href="http://www.dquinn.net/dont-make-me-download-a-lot-of-crap-yslow">The Unavoidables: Don't Make Me Download a Lot of Crap; or, Sometimes You Just Deserve an F From YSlow, You Shameless Self-Promoter</a></li>
<li><a href="http://www.dquinn.net/htaccess-adding-etags-gzip-expires-headers">Three Sexy Performance Rules for .htaccess on WordPress: Configure ETags, Gzip Compression, and Expires Headers</a></li>
<li><a href="minify-css-javascript-yui-compressor">Nobody Wants to See Your Whitespace: Minify CSS and Javascript using Yahoo!’s UI Compressor</a></li>
</ul>
<p>*<em> Full disclosure</em>: Where do I stand? My front page gets a big fat B (88%) for making you download a lot of crap:</p>
<div id="attachment_1441" class="wp-caption aligncenter" style="width: 404px"><img class="size-full wp-image-1441" title="YSlow Score: DQuinn.net" src="http://www.dquinn.net/images/yslow-rating.gif" alt="YSlow Score: DQuinn.net Home Page" width="394" height="396" /><p class="wp-caption-text">YSlow Score: DQuinn.net Home Page</p></div>
<p>YSlow gleefully reports that 32 CSS background images is downright <em>sinful</em>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dquinn.net/mastering-yahoos-13-performance-rules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Nifty Plugins for Firefox, from Your Friendly Neighborhood Lithuanian</title>
		<link>http://www.dquinn.net/nifty-firefox-plugins/</link>
		<comments>http://www.dquinn.net/nifty-firefox-plugins/#comments</comments>
		<pubDate>Thu, 21 Feb 2008 04:18:57 +0000</pubDate>
		<dc:creator>Daniel Quinn</dc:creator>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[css viewer]]></category>
		<category><![CDATA[doctype]]></category>
		<category><![CDATA[firebug]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[fireftp]]></category>
		<category><![CDATA[genuine interactive]]></category>
		<category><![CDATA[html validator]]></category>
		<category><![CDATA[lithuanian]]></category>
		<category><![CDATA[papeboston]]></category>
		<category><![CDATA[web developer toolbar]]></category>

		<guid isPermaLink="false">http://www.dquinn.net/journal/tutorial/nifty-firefox-plugins/</guid>
		<description><![CDATA[When I first starting working at Genuine Interactive, I asked a random question of Genuine's many web-gurus, who know infinitely more about web development than I do. The particular guru I queried was a Lithuanian MySQL database programmer named Jimbo, who in addition to having a penchant for quoting from the movie The Hunt for Red October, often relates to me, in his thick Russian accent, stories of what life was like in Lithuania.]]></description>
			<content:encoded><![CDATA[<p>When I first starting working at <a title="Genuine Interactive" href="http://www,genuineinteractive.com">Genuine Interactive</a>, I asked a random question of Genuine's many web-gurus, who know infinitely more about web development than I do. The particular guru I queried was a Lithuanian MySQL database programmer named Jimbo, who in addition to having a penchant for quoting from the movie <em>The Hunt for Red October</em>, often relates to me, in his thick Russian accent, stories of what life was like in Lithuania.</p>
<p>Before Jimbo attempted to address my question, he pointed out that I lacked all of the great tools I could be using that would enable me to easily answer my question myself. So I pass on Jimbo's wise recommendations to you!</p>
<p><img class="size-full wp-image-857 alignright" title="HTML Validator for Firefox" src="http://www.dquinn.net/images/htmlvalidator.gif" alt="HTML Validator for Firefox" width="200" height="75" /></p>
<p><a href="http://users.skynet.be/mgueury/mozilla/">HTML Validator</a>. The validator installs a small, unobtrusive icon at the bottom of your Firefox status bar, indicating whether the site you're looking at is valid or not, how many errors have caused it to fail validation, and where in the source code the errors are located. Be sure to select the "SGML Parser" when you install the plugin. The validator checks markup against whatever DOCTYPE you specify, so it works for any flavor DOCTYPE—transitional or strict.</p>
<p><img class="size-full wp-image-860 alignright" title="Web Developer Toolbar" src="http://www.dquinn.net/images/web-developer-toolbar.gif" alt="Web Developer Toolbar" width="200" height="150" /></p>
<p><a href="https://addons.mozilla.org/en-US/firefox/addon/60">Web Developer Toolbar</a>. After using this plugin, I find it hard to imagine what development was like without it. The Web Developer Toolbar provides a plethora of tools that allow you to test various aspects of your website before it goes live, right in Firefox. Here's a list of some of the things it can do:</p>
<ul>
<li>Allow you to see how your website performs
<ul>
<li>if javascript is disabled</li>
<li>if CSS is disabled</li>
<li>if images are disabled</li>
<li>when viewed at different resolutions</li>
</ul>
</li>
<li>Disable your cache, so you can preview your pages without having to worry about old edits popping up</li>
<li>Outline or display various elements of a page (like headings, tables, links, depreciated elements, etc) that are not immediately (or normally) visible, so you can easily make sense of a site's structure upon first glance</li>
<li>Analyze forms</li>
</ul>
<p>On top of these features, the Web Developer Toolbar also has the ability to push your site to the w3c validator (for both HTML, CSS, and XML feeds), as well as push your site to accessibility validators to test compliance with Section 508 and WAI.</p>
<p><img class="size-full wp-image-862 alignright" title="Firebug" src="http://www.dquinn.net/images/firebug.gif" alt="Firebug" width="160" height="120" /></p>
<p><a href="https://addons.mozilla.org/en-US/firefox/addon/1843">Firebug</a>. Think of Firebug as the web developer's magnifying glass. Like the Firefox CSS Viewer, Firebug enables you to visually locate elements of your HTML code by mousing over those elements on the page. In a property window, Firebug lays out your page's hierarchy and shows you all the properties associated with each element in your page. What's more, Firebug <em>allows you to actively edit a page that's on the web</em> so you can preview what your changes would look like before you even implement those changes in your markup. Definite wow-factor for any web developer! But don't forget to implement the changes, of course, when they do pan out as you wanted.</p>
<p><img class="size-full wp-image-863 alignright" title="FireFTP" src="http://www.dquinn.net/images/fireftp.gif" alt="FireFTP" width="159" height="120" /></p>
<p><a href="http://fireftp.mozdev.org/">FireFTP</a>. Stop using a third-party client to upload your pages to the web! FireFTP, which integrates directly into Firefox, can do all the things your everyday FTP client can do without forcing you to leave your browser.</p>
<p>Sekmes! Geros kloties! And happy coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dquinn.net/nifty-firefox-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
