unfortunately no..
when the anime is on TV, There is more interest in my site, and i've 10/12.000 unique visitors.
But I think that I'm NOT the only one that having these visitors on wordpress site.
nobody else has had my problem?

As donncha says, also consider moving your site from a shared hosting account to a VPS. Otherwise you will continue having your site blocked or you may have you account canceled.
Installing cache plugins isn't enough when you start having 10k+ visitors.

thanks for the advice but a small dedicated is too expensive form me..
wich host do you have? Hostgator?
Now.. i've the site in down : http://www.onepieceworld.net/
And I have now installed :
WP Super Cache
DB Cache Reloaded
SQL Monitor

I use Hostgator for a lot of my clients. Their shared servers are pretty beefy. They don't disable your site for visitors but maybe CPU? In which case what you should be doing is SSH into your server and run top. You may find a specific process causing your problem and not your site in general.
But I do agree that you probably belong on a dedicated server.

W3 Total Cache supports all of the popular hosting account types, but there are lots of plugins, themes, widgets and hosts out there. So if you want some tips you can contact me through my site or if you install W3TC use the bug submission form.

I noticed that you use WP Super Cache and DB Cache Reloaded together. I have seen a number of sites state that they are compatible. I was about to create a new thread to ask this, but I thought I try here first.

Have you found these two plugins to be compatible? Do they create speed gains when used together?

Hi cfisher
I don't have knowledge with wordpress but notice something in your site
You use i lot pictures as background in your home page you lose about 300 KB for this backgrounds.
If you fix that with small size pictures i think you well save about 30% of bandwidth
Sorry for my bad English

@donncha - thanks for the clarification. BTW, I eagerly await your integration of that Minifiy plugin designed for SuperCache (I saw this discussed on the author's website). I have problems with the other main WP-Minify plugin, and I hope this one works for me!

@manhal99 - thanks for the advice. I've been working hard to increase my website speed with only marginal returns. I'l like to implement WP Smush.it plugin to address your concerns over image size, but I am uncertain if this plugin plays nicely SuperCache with the CDN enabled.

By the way, I think both WP Super Cache and W3 Total Cache are incredible and excellent, so I have no bias whatsoever against either - it's just that presently, again: for shared hosting situations, WP Super Cache together with the self-hosted CDN option (make sure you also use extra subdomains in the "Additional CNAMES" field, like cdn1.example.com, cdn2.example.com, cdn3.example.com) is a solution that can stretch your traffic a long ways and is slightly easier to get and keep working.

In addition to the earlier great suggestion to also use the WP Minify plugin (i.e. together with WP Super Cache) also look into the oft overlooked WP Widget Cache plugin: as the name suggests, it is very helpful if you have widgets in your sidebars, and you can activate and tweak caching duration on a per-widget basis, and best of all, it works like a charm with WP Super Cache.

Finally, a tip which steps outside the realm of caching and instead looks at the volume of traffic itself, i.e. a wholly different approach: look into the (free) CloudFlare service. That is a reverse proxy type filter based bad bot blocking service, which essentially cleans up the traffic by eliminating most of the bad stuff. Oddly enough, that service works better with W3 Total Cache! If you go with the free service mode, the CDN issue becomes practically moot, as CloudFlare already does a lot of caching transparently for you. Again, that's a different approach, but it may be just right for you.

It'd be neat of WP Super Cache also supports CloudFlare, then again: it's tried and tested to work very well with W3 Total Cache already.

Thanks nv1962 for this write up. I reviewed the CloudFlare service. That appears to be a very interesting approach to speeding up a website.

@donncha - any idea if/how CloudFlare might work with SuperCache? I also use a 3rd party CDN and set up it up directly into SuperCache. In addition to filtered DNS, CloudFlare says that they also cache images, CSS, javascript, etc. too so they sound like a CDN in some respects... All this caching by various parties (SuperCache, CDN, Cloudflare) makes my head hurt trying to wrap my mind around the caching of a cache of a cache.

Yeah it can get complicated very quickly! Just to be sure: don't mix the use of self-hosted CDNs in WP Super Cache together with CloudFlare if you're going with their generous Free service. Their paid Pro service can handle CDNs with more flexibility, but I suppose most will want to look into their Free service first. BTW: CloudFlare picks up static files (images, JS, CSS) automatically, to serve those from its farm, so that amply compensates the "lack" of self-hosted CDNs. Also: when minifying javascript and CSS files (either with a separate plugin or inside W3 Total Cache) be careful to not minify already minified files (if the JS or CSS code already looks like a solid block of text, it's minified already - some plugin developers do that to speed up performance.) And finally, some JS simply doesn't like being minified and/or concatenated. In my experience, it's best to do things step by step: get the cache working first, then add minify, then work with CDNs to see if that works, too.

It's important to understand that CloudFlare is *not* a CDN, nor is it their intension to be. Furthermore nothing replaces properly tuning your web site before adding other services as next or final steps.

After all, CloudFlare has a security focus. The approximate CDN functionality is a nice extra thrown in, arguably (perhaps) to offset the tiny extra time for originating IP lookups. But their focus is on internet hygiene, not performance optimization per se.

Nonetheless... It's still an interesting article, as it shows that picking the appropriate distributed content delivery method and provider does benefit from selecting one that is within geographic proximity. I.e. as Ivan Malijkh already notes, he has sites served from the Netherlands, and when the users (visitors) are also in the Netherlands, the obvious CDN choice would be in that same country, too. That explains why his setup with CloudFlare fared not so well; it's not so much about CoudFlare's service but the Netherlands not being in Kansas anymore, Toto.

Again, Frederick Townes' reminder is important to keep in mind (if you forgive me the department of redundancy department)