Since I started self-hosting this blog again on August 6 2008, I have been trying to find more ways to pull traffic toward the content that I put up. Like all bloggers, I feel that I have important things to say (at least in the area of Web performance), and ideas that should be read by as many people as possible.

As well, I have realized that if I invest some time and effort into this blog, it can be a small revenue source that could get me that much closer to my dream of a MacBook Pro.

The Analysis

In a post yesterday morning, Darren Rowse had some advice on when the best time to release new post is. Using his ideas as the framework, I pulled the data out of my own tracking database and came up with the chart below. This shows the page view data between September 1 2007 and September 15 2008 based on the day of the week vistors came to the site.

Using this data and the general framework that Darren subscribes to, I should be releasing my best and newest thoughts in a week on Monday and Tuesday (GMT).

After Wednesday, I should release only less in-depth articles, with a focus on commentary on news and events. And I must learn to breathe, as I suffer from an ailment all to common in bipolars: a lack of patience.

A new post doesn’t immediately find its target audience unless you have hundreds or thousands (Tens? Ones?) of readers who are influential. If you are luckyin this regard, then these folks will leave useful comments, and through their own attention, help gently show people that a new post is something they should devote their valuable attention towards.

It takes a while for any post to percolate through the intertubes. So patience you must have.

Front-loaded v Long-tailed

Unless, of course, your traffic model is completely different than a popular blogger.

The one issue that I had with Darren’s guidance is that it applies only to blogs that are front-loaded. A front-loaded blog is one that is incredibly popular, or has a devoted, active audience who help push page views toward the most recent 3-5 posts. Once the wave has crested, or the blogger has posted something new, the volume of traffic to older posts falls off exponentially, except in the few cases of profound or controversial topics.

When I analyzed my own traffic, I found that the most of my traffic volume was aimed toward posts from 2005 and 2006. In fact, more recent posts are nowhere near as popular as these older posts. In contrast to the front-loaded blog, mine is long-tailed.

There are a number of influential items in my blog which have proven staying power, which draw people from around the world. They have had deep penetration into search engines, and are relvant to some aspect of peoples’ lives that keeps pulling them back.

Summary

I would highly recommend analyzing your traffic to see it is front-loaded or long-tailed. I know that I wish that this blog  was more front-loaded, with an active community of readers and commentators. However, I am also happy to see that I have created a few sparks of content that keep people returning again and again. If your blog is  long-tailed, then when you post becomes far less relevant than ensuring the freshness and validity of those few popular posts. Ensure that these are maintained and current so that they remain relevant to as many people as possible.

Tags: analysis, analytics, blog posts, Blogging, content creation, content release, current, Darren Rowse, freshness, front-loaded, hits, long tail, maintain, page views, posting, search engines, statistics, traffic, update, Web Performance

This morning, Tiger Direct effectively imploded.

Bad day.

UPDATE: Looks like they found the solution to their problem.

Technorati Tags:
Grabperf, Web performance, Tiger Direct, Cyber Monday

Tags: GrabPERF, HTTP, IE, IM, it, LAN, Om, performance, pr, Technorati, update, web, Web Performance, Web+performance

Today’s biggest victim of Black Friday appears to be Sears

Sears measurement data for the last 8 hours can be found here.

UPDATE: It gets worse for Sears.

Technorati Tags:
Grabperf, Sears, Black Friday, Web Performance

Tags: app, data, GrabPERF, GrabPERF.org, HTTP, IE, IM, it, LAN, measurement, Om, performance, PHP, Technorati, update, web, Web Performance, Web+performance

We got Samantha a new T-Mobile cell a few weeks back. But it came with an unwanted and expensive feature: every morning at 11:00, she receives a weather update from Windows Live Alerts.

Apparently the previous owner of the number had these alerts programmed. And of course, there is no way to shut them off because we have no clue who this person is/was.

If anyone out there from the Windows Live team or the T-Mobile support team can try and help us, it would be very much appreciated.

Technorati Tags: Windows Live, T-Mobile, TMobile, Windows Live Alerts, help, sms

Tags: app, HTTP, it, live, Om, One, pr, T-Mobile, Technorati, TMobile, update, window, Windows

It has been at least a year since I last updated everyone on the state of GrabPERF. That’s because for most of the last year, the system has been rolling along without a hitch or a major systemic change. The last major change to the agent code was alomost exactly a year ago, when I added the ability to capture text matches.

It wasn’t until last week, however, that I allowed folks to be able to see the results of these text match failures. Let’s just say that motivation has been low and my real job has been keeping me busy.

I did want to share the growth, and mellowing of the system as it progresses into year three.

Total Measurements Per Day

Unique Tests Measured Per Day

Back in July 2005 when I started this grand experiment, I was gathering 10,000 measurements a day from less than forty tests. The system spiked at 390,000 measurements per day (April 2006) and 147 tests (June 2006).

Starting just after that, I started reducing the number of tests to improve system efficiency, and began developing the text match capability.

There have been some changes to the number of measurements, but on the whole, the system has been completely stable for the last 12 months.

As some of you may have noted, I have add some new features in the last 10 days, and re-organized the structure of the system to allow for better tracking of usage. Over the next few months, I will be attacking the code to make it process things more efficiently, but not substantially change the appearance or functionality of GrabPERF.

It has been noted by some commentators that the design doesn’t pop and sizzle. No AJAX, DHTML, or other flashy gizmos. Guess what? The system is designed to deliver data efficiently and effectively. And as someone who has seen the performance fall-out from badly delivered Web 2.0 implementations, I will stick with clunky and effective, as, in the end, you gotta put all those bytes on the wire.

For those that have stuck with the system over the last year, thanks. I enjoy delivering the best measurement data money can’t buy, and hope you stick around for the ride.

Tags: ajax, app, ARIN, cbc, content, data, design, GrabPERF, HTML, HTTP, IE, IM, ISP, it, live, measurement, Om, One, performance, pr, Technorati, tracking, update, web, web 2.0, Web Performance

If you use GrabPERF on a regular basis, the somewhat flaky navigation method has become second nature to you. In fact, to circumvent some of the idiosyncrasies, you have probably bookmarked your favourite pages.

Yesterday, I broke your links.

When I redesigned GrabPERF in February 2006, I had just discover the require function in PHP, and decided to build the entire the structure using a single container page as the framework, and individual functions called using URL parameters.

As time went on, my own “brilliance” started to get in the way of maintaining and updating the code. It took me 10-15 minutes to figure out how I constructed pages, and then find the right code to fix or update.

Yesterday, I got completely fed up with this structure.

Now, all functions have their own unique pages, making maintenance a snap. And as an added benefit, I can now effectively track the usage of individual pages, so I know where to through development efforts.

Some of the changes.

http://grabperf.org/homepage.php?page=compare&test=2&tests%5B%5D=276&tests%5B%5D=277&tests%5B%5D=279&tests%5B%5D=280

becomes

http://grabperf.org/compare.php?test=2&tests%5B%5D=276&tests%5B%5D=277&tests%5B%5D=279&tests%5B%5D=280

http://grabperf.org/homepage.php?page=scatter&test=277&hours=2

becomes

http://grabperf.org/scatter.php?test=277&hours=2

I apologize for the confusion that this may cause, but in the long run, this will help me make the code better, and more robust.

Tags: book, content, design, GrabPERF, GrabPERF.org, HTTP, IE, IM, improvement, ISP, it, maintain, maintenance, Om, optimize, Pages, performance, PHP, pr, run, Technorati, update, web, Web Performance

Last night, I spent over an hour on the phone with three very friendly and helpful T-Mobile tech support representatives, and guess what? The troublesome Samsung T619 I slammed a couple of weeks ago is now able to send and receive text messages.

I was impressed with the efficiency of the T-Mobile team, and the Tier 2 team I ended up with was thorough. It took two Over-the-air updates to fix the phone, but it’s done and I’m happy.

Can’t take back the bad comment, but hope I can counter it with some good words.

Tags: T-Mobile, TMobile, Samsung T619, SGH-T619, Samsung

Tags: app, HTTP, IE, IM, it, Om, One, pr, T-Mobile, Technorati, TMobile, update

Today, I want to talk about what happens when you aggressively adopt an online strategy, but leave your print subscribers behind.

I subscribe to a great architecture and design magazine, whose name I will exclude from this discussion, with a fantastic and informative online presence. The archive and articles available to subscribers are a fantastic resource for people just beginning to explore this field.

In February, I noticed that they had updated their site with the most recent issue’s content and cover. I was somewhat miffed, as my print copy had not yet arrived in the mail. Immediate assumption: print copy lost; request re-transmission.

Today, I checked the site, and all of the content for the March 2007 issue is online. And I don’t have my copy of this issue yet.

Based on the response to the e-mail that I sent to the circulation and publishing team, I may be the first person to bring this to their attention.

When you are in the dead-tree print industry, the Web (1.0 and 2.0) are crucial extensions to your existing business model. But the aggressive use of the Web channel to deliver your content to the rest of the world before the print subscribers receive their copies is doing damage to your business.

Subscribers pay extra in order to gain access to your magazine before the rest of the world can get it. This must extend to the Web channel. As a subscriber, knowing that someone can read the contents of the magazine online before I get my chance to look at the print copy is unsatisfactory.

Subscription content infers a level of exclusivity to those who buy the gold ticket. If you give everyone the gold ticket at the same time, then a subscription loses it sense of exclusivity. Then the magazine loses guaranteed revenue. Then the magazine is gone.

Information should be free. I chafe against the subscription gateways as much as the next person. But if you base your entire business on a subscription model, you better not undermine your own subscription business by giving the subscription content away for free.

Tags: magazine, content, subscription, print, Web

Tags: app, attention, business, content, design, EAD, extension, HTTP, IE, IM, information, IP, it, leave, live, media, Om, One, online, online presence, pr, strategy, Technorati, update, web

Just found that Dwell magazine has a blog.

Ooops! A pseudo-blog. No feed.

Dwell: Get with the program.

UPDATE: Apparently it does! There is an RSS graphic at the bottom. But that’s not the feed link. Oh no!

You have to click the image to go to a page that has the page that has the RSS feed in it.

No. The feed is part of the blog. It MUST appear on the same page as the blog. Making it hard to find defeats the point of the process.

Tags: app, ARIN, blog, content, feeds, HTTP, IE, IM, ISP, it, LAN, Om, pr, RSS, Technorati, update

I hear the February 2007 issue is great.

I’m a subscriber.

Where’s my copy?

UPDATE:  They are sending out a replacement copy. Yay!

Technorati tags: Metropolis, magazines, subscriber

Tags: content, HTTP, ISP, it, Om, Technorati, update