More detailed CloudFlare analysis

Following my last post about CloudFlare, I ran some further benchmarks in response to the feedback from their team. Here’s the summary:

  • CloudFlare only combines our Javascript, not our CSS files, despite what it said on the tin (the site has been updated, when we signed it said JS & CSS)
  • This only happens on some user agents on some operating systems, CloudFlare will not give me a list of user agents.
  • On browsers where this is enabled, we see a marked improvement, where it’s not, we see no gain or a small loss.

Graphs

I ran two sets of tests (using only browsers where RocketLoader is enabled).

Graph showing marked improvement with cloudflare on

Second graph showing marked improvement with cloudflare on

Conclusion

We probably won’t implement CloudFlare across all our sites. I might still experiment on one of our higher traffic sites now that we’re running boomerang and gathering real user data to compare. However, the black box nature of CloudFlare fundamentally leaves me feeling uneasy.

The product appears to be in beta, which wasn’t clear when we signed up. I thought it was a polished product ready for production use. But much of the support chat is about RocketLoader being in beta, no list of user agents at this time, etc.

Bottom line, CloudFlare hasn’t done what I expected. I’ll test mod_pagespeed and we’ll probably go with that, pending any major roadblocks.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s