I took a quick look via Firebug/Networking on your site:

31 sub requests, of which 5 form a chain so they can't load in parallel. The server at www.facecash.com waits 2.5 seconds before it sends back the content (this is not DNS waiting time!). On s.facecash.com which you use for the other page components, those are just 0.2 seconds.

The page has 409 KB in total, of which 97 KB are JavaScript code and 135 KB are the main picture (home1.jpg). This big picture changes on each request, smashing the browser caching and ensuring subsequent page reloads will be slow, too.

WTF?!

You should really overcome your ego and to make use of the offer given to you.

> I think any delay may be DNS-related

Here in Germany, your domain resolves within a few milliseconds. However, your whole site takes 12-13 seconds to load. (FWIW, I have a 16 MBit internet connection)

You'll have to learn a lot about basic things like: how to compress images properly, how to decrease web server latency, how to get JS code out of the critical path, how to ensure proper cache use on client side, etc.

Don't get me wrong: It is perfectly okay if a young company's system isn't fully optimized. That's fine, nobody expects this. But if you claim to be "quick like a fox" and to be "fairly optimized at this point", you're saying that you think you are fast enough, so customers can't hope you'll be willing to improve your speed much in the future. And that is a problem, unless you were really optimized, which you aren't.