This isn't a Free Hosting support issue, but...
After the ridirects (a consequence of bouncing off of several nameservers), you have 126 HTTP requests on your home page, and most of them go to outside domains (Twitter and Google's +1 being the largest request targets). Your "home" resources are loading relatively quickly (some are deferred in preference to outside resources); it's the sheer number of requests and the load times of external resources that are killing you. My browser actually froze a coule of times trying to load and render your home page. You could have an impossibly fast hosting server and infinite bandwidth on that server (or upgrade to the biggest Infinity+ hosting package) and your page would still be snail-slow because so much of your page has nothing to do with the server you're on or the network pipe it uses.
Get the request numbers down to a minimum, and make each request as small as it can be. Take a look at your site using things like the Developer Tools (network tab) in Chrome and Yahoo's YSlow. You can use WhySlow.com to get your own local network and browser out of the picture. Reconsider all of the social widgets you're using, and cut them down to what your traffic actually supports and requires. (For instance, if you have no real user presence on Google Plus, then it might not make sense to add the dozen or so requests that deal with G-plussness.) Unoptimized WordPress is a slow and resource-hungry bit of software, and there are a lot of plugins that are rather less than paragons of screaming high performance. Using a good cache plugin will help a lot with the local resource cost, as will making anything static that can be static (it's much better to hard-code permanent stuff into the template than to look it up in a database or config file for every single page render). Move JavaScript to the bottom of the page where possible (widget scripts need to live inline so that they can be rendered without reflow) and make sure the page is usable without the script if it fails to load. You might want to spend some time on the WordPress section of SmashingMagazine.com for good, professionally-tested, real-world performance pointers.
But as long as those uncached outside requests are there (they can't be cached because they use site and user identifiers, and CDNs can only get you so far with dynamic data), you're not going to have a whole lot of speed going on.
