Consumer News / Opinion on JetPack
I’m looking at my blog’s visitor statistics today (the day I wrote this) and noticed this big blue and green banner notice saying that all future updates to the WordPress.com stats package for your self-hosted blog will only be included in the JetPack add-on package.
I’m not reacting well to this enforced method of retaining my statistics package in my WordPress blog.
Finding yourself forced into a package that is overly redundant with processes that I already employ feels very much like I’m using a Microsoft product and being told it’s this or nothing. I have always preferred the power of choice myself.
Show me something that makes me want it, and I’ll be there. But not this way.
As if my day isn’t already busy enough, I now have to decide to either blow off my WordPress.com stats package or look into JetPack to see what plugins I have to dump to adopt this thing that I originally did not feel that I needed when it first came out.
The verbiage for JetPack is the same as the WordPress.com stats package… it will put “no additional load on your server.” Yet I’ve proven to myself, that my own interaction (loggin in and editing) with my site is slowed down considerably when the stats package is in place. When I disable it, my response time is easily 1/2 that. But then again, I don’t use a CDN right now. (That’s for another day… CDN’s.)
{ 0 comments }








