Validating HTML Killed a Plugin

Long ago sold on using valid HTML, I made the choice that I would rather not have a WordPress plugin on this site if it meant I could not have valid HTML. I have several reasons why: Reasons Why Validating HTML is Important.

Well, I have another reason. Making sure your site is still valid after installing a plugin, can prove you may not need the plugin at all!

Delete the TweetMeme WordPress Plugin

Example of TweetMeme button

I’m sure TweetMeme would not like you to delete their plugin, but it’s really a waste. It also doesn’t validate. WordPress plugins slow things down. They often work by filtering content, and inserting things in the right space. To do that, it means processor power, and that equals to increased load time. Add too many plugins, and you could bring your site speed down to a slow crawl.

So here is a simple question. Why use a plugin where you can easily insert one line of code into the template? To make their TweetMeme button work as a plugin it needs to be stuck in an iframe, and has all sorts of messy code. Part WordPress plugin issue, part TweetMeme, but no matter.

Here is the fix in this particular case. TweetMeme supplies the one line of code right from their site. Just insert this code where you want the TweetMeme button on your blog:

<div><script type=”text/javascript” src=”http://tweetmeme.com/i/scripts/button.js”></script></div>

You don’t have to use the DIV tags, but they do make for easier styling. My TweetMeme button is now back on my site, and my HTML? It’s now VALID.

8 Comments

Add a Comment

Your email address will not be published. Required fields are marked *