A few months ago, I signed up for CloudFlare and added this blog to their service. At first, I was terrified. I hate messing with DNS settings. Then I was jubilant — my bandwidth was down about 40%. Next I was worried, because traffic dropped dramatically. Finally, I was upset — Google had cut me off. It’s been about two months since the last post. Here’s what’s happening now.
Traffic is back
I don’t think I can honestly blame CloudFlare for this one. Yeah, it happened after I turned them on, but it didn’t happen immediately after. Google seems to have recalculated my blog’s value a little after I switched over, and I wasn’t ranking as highly for some of my higher-traffic terms (increasing AdSense revenue, updating your 2WIRE router to use WPA2, and pre-paid Android phones). Honestly, I hadn’t touched on those topics for a few weeks, and that probably hurt me.
Performance is good
As measured by Pingdom, response times are still under a second for most requests. They’re not as low as before CloudFlare, but they’re plenty good. And bandwidth usage is still way down, which is phenomenal.
Conclusions
I’m happy with CloudFlare. They have a great product and have seen impressive results. I’m using them on other blogs, but I’m still a little hesitant about switching over Dappered. We’ll see what the future brings. If Dappered’s traffic keeps growing like it has been, we’ll have to do something.
Update: Here’s a chart showing my drop in search traffic and its recovery. This is Traffic Sources > Search Engines in Google Analytics. Good question, Debbie.
Update: I added the [don't] in the headline. I’ve turned CloudFlare off on this site. And check the comments — Anurag is having the same problem as Debbie and me. That makes the traffic drop a pretty serious, pretty consistent issue.















What I said was: Give me all the bacon and eggs you have.
Ron Swanson (Parks and Recreation):
This has been cracking me up since last week. Parks and Recreation is worth a look if you haven’t checked it out.