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

tweetmeme3

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.

  7 Responses to “Validating HTML Killed a Plugin”

  1. Hi Robert,

    I deleted that plug-in long ago but not for the same reason you mentioned in your post. I had technical issues with the count not updating and they couldn’t get it resolved.

    After reading your article, I’m wondering how many other plug-ins could be eliminated. I currently use about 20 different plug-ins on my blog. I’m not sure how they affect the HTML but they don’t appear to slow the load time.

  2. Thanks for the tip, Robert.

    So what’s the difference between a plugin using processor power and javascript using processor power? Is it that for a plugin the server is doing the work whereas for javascript the the visitor’s computer is doing the work?

    How does that affect load time for the visitor?

    Guy.

  3. Hey Guy,

    Javascript is running on the users browser, so that means their CPU needs to work. A WordPress plugin will make your website server CPU work harder, and that could be bad news if you get a lot of traffic.

  4. Yaa its right that Validated HTML Killed a Plugin,want to solve that one.

  5. hey how i set a plugin of my facebook on my site..i just want that without facebook open he like it.

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>