Did you actually read all the output from that link? It did tell you all of the problems!
I'd do the following:
setup a nameserver with a .info extension and use that instead of your current nameservers at both the registrar and in your own NS records for the domain. This will get rid of 371ms which is worthwhile!
fix your delegated nameservers (dns8.yarantoos.com dns7.yarantoos.com) to be the same as your NS records (ns16.mkoh.com ns15.mkoh.com)
fix the timeout at dns8.yarantoos.com or delete it as a nameserver
To explain in a little more detail -
When you registered the domain tarahan.info, you set up nameservers of dns8.yarantoos.com * dns7.yarantoos.com. When you actually setup hosting for the domain, you set up DIFFERENT nameservers of ns15/16.mkoh.com. This won't be helping and some old versions of Bind (ok ancient versions) may not be able to resolve your domain.
The biggest problem is the timeout at dns8.yarantoos.com - it's set up as a nameserver at the registrar but doesn't know about tarahan.info, so there's a potentially *long* timeout happening when users access that nameserver.
When your domain's nameservers have the same TLD (ie .info in this case) as the domain being resolved, the TLD nameservers (ie the nameservers for .info in this case) return the actual IP address of the nameservers for tarahan.info. This is called "glue". If the nameservers have different TLDs (in this case, dns7/8.yarantoos.com and ns15/16.mkoh.com both have .com endings) this glue will not be returned which means several other lookups have to be done.
Try www.dnsreport.com - it does tell you a lot more, most of which I agree with. Click here for a full check. The first two red entries are the ones to worry about - dns8.yarantoos.com and the fact that the nameservers differ.